Skip to content

Commit 3f70da5

Browse files
committed
Merge pull request #82 from GoogleCloudPlatform/lesv-rm-003
Mention the problem at exit time
2 parents 8b5fd1c + 882c7c8 commit 3f70da5

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

java/dataflow-pardo-helloworld/README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,14 @@ pipeline that writes the words "Hello" and "World" into Cloud Bigtable.
3232

3333
`$ mvn compile exec:java -Dexec.mainClass="com.example.bigtable.dataflow.pardo.HelloWorldBigtablePardo" -Dexec.args="--runner=BlockingDataflowPipelineRunner --project=<PROJECTID> --bigtableProjectId=<PROJECTID> --bigtableClusterId=<CLUSTERID> --bigtableZoneId=<ZONE> --bigtableTableId=Dataflow_test --stagingLocation=gs://<STORAGE_BUCKET>/staging"`
3434

35+
Note: Occasionally, you may see log messages similar to the following. It is safe to ignore these warnings, which will be fixed in a future release:
36+
37+
INFO: Job finished with status DONE
38+
[WARNING] thread Thread[pool-1-thread-1,5,com.example.bigtable.dataflow.pardo.HelloWorldBigtablePardo] was interrupted but is still alive after waiting at least 15000msecs
39+
[WARNING] thread Thread[pool-1-thread-1,5,com.example.bigtable.dataflow.pardo.HelloWorldBigtablePardo] will linger despite being asked to die via interruption
40+
[WARNING] NOTE: 1 thread(s) did not finish despite being asked to via interruption. This is not a problem with exec:java, it is a problem with the running code. Although not serious, it should be remedied.
41+
[WARNING] Couldn't destroy threadgroup org.codehaus.mojo.exec.ExecJavaMojo$IsolatedThreadGroup[name=com.example.bigtable.dataflow.pardo.HelloWorldBigtablePardo,maxpri=10]
42+
java.lang.IllegalThreadStateException
3543

3644
### Verify
3745

0 commit comments

Comments
 (0)