cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Lamballais (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13272) "nodetool bootstrap resume" does not exit
Date Mon, 10 Jul 2017 10:31:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080131#comment-16080131
] 

Tim Lamballais commented on CASSANDRA-13272:
--------------------------------------------

[~blerer], I'll update it to retrieve the cause in case of ExecutionException. It'll then
pass that message back to the client, but I'll use the original throwable in the call to log.error,
so we don't lose the original stacktrace in the logs.

Cheerio,

Tim

> "nodetool bootstrap resume" does not exit
> -----------------------------------------
>
>                 Key: CASSANDRA-13272
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13272
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Lifecycle, Streaming and Messaging
>            Reporter: Tom van der Woerdt
>            Assignee: Tim Lamballais
>              Labels: lhf
>
> 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 :
> {noformat}
> [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
> {noformat}
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message