[
https://issues.apache.org/jira/browse/CASSANDRA-8838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364788#comment-14364788
]
Sylvain Lebresne commented on CASSANDRA-8838:
---------------------------------------------
bq. The first issue is that starting a node with {{no_wait=True}} fails to
detect the process pid and the test stops there, this applies to all four tests.
I've noticed that too and this is not specific to this issue: there is quite a
few dtests that uses this and are currently failing on trunk on my box for the
reason you mention. It appears that on current trunk, on my box, the Cassandra
process takes > 10 seconds to even get created (which is definitively something
relatively new). I haven't investigated what made that happen so it could be
nice to bisect it so we at least know, but as you said, removing the
{{no_wait}} flag at least fixes the tests.
> Resumable bootstrap streaming
> -----------------------------
>
> Key: CASSANDRA-8838
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8838
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Yuki Morishita
> Assignee: Yuki Morishita
> Priority: Minor
> Labels: dense-storage
> Fix For: 3.0
>
>
> This allows the bootstrapping node not to be streamed already received data.
> The bootstrapping node records received keyspace/ranges as one stream session
> completes. When some sessions with other nodes fail, bootstrapping fails
> also, though next time it re-bootstraps, already received keyspace/ranges are
> skipped to be streamed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
