Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
2.2.11, 3.0.15, 3.11.1, 4.0-alpha1, 4.0
-
Normal
Description
I have a script that calls "nodetool bootstrap resume" after a failed join (in my environment some streams sometimes fail due to mis-tuning of stream bandwidth settings). However, if the streams fail again, nodetool won't exit.
Last lines before it just hangs forever :
[2017-02-26 07:02:42,287] received file /var/lib/cassandra/data/keyspace/table-63d5d42009fa11e5879ebd9463bffdac/mc-12670-big-Data.db (progress: 1112%) [2017-02-26 07:02:42,287] received file /var/lib/cassandra/data/keyspace/table-63d5d42009fa11e5879ebd9463bffdac/mc-12670-big-Data.db (progress: 1112%) [2017-02-26 07:02:59,843] received file /var/lib/cassandra/data/keyspace/table-63d5d42009fa11e5879ebd9463bffdac/mc-12671-big-Data.db (progress: 1112%) [2017-02-26 09:25:51,000] session with /10.x.y.z complete (progress: 1112%) [2017-02-26 09:33:45,017] session with /10.x.y.z complete (progress: 1112%) [2017-02-26 09:39:27,216] session with /10.x.y.z complete (progress: 1112%) [2017-02-26 09:53:33,084] session with /10.x.y.z complete (progress: 1112%) [2017-02-26 09:55:07,115] session with /10.x.y.z complete (progress: 1112%) [2017-02-26 10:06:49,557] session with /10.x.y.z complete (progress: 1112%) [2017-02-26 10:40:55,880] session with /10.x.y.z complete (progress: 1112%) [2017-02-26 11:09:21,025] session with /10.x.y.z complete (progress: 1112%) [2017-02-26 12:44:35,755] session with /10.x.y.z complete (progress: 1112%) [2017-02-26 12:49:18,867] session with /10.x.y.z complete (progress: 1112%) [2017-02-26 13:23:50,611] session with /10.x.y.z complete (progress: 1112%) [2017-02-26 13:23:50,612] Stream failed
At that point ("Stream failed") I would expect nodetool to exit with a non-zero exit code. Instead, it just wants me to ^C it.