[
https://issues.apache.org/jira/browse/CASSANDRA-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14528742#comment-14528742
]
Marcus Eriksson commented on CASSANDRA-5839:
--------------------------------------------
turns out this is a ccm issue - we fill up the subprocess.Popen stdout buffer
too quickly when creating the second keyspace. This in turn seems to
dead(?)-lock logback and the node does not start.
Adding a process.communicate() immediately after creating the process 'fixes'
the issue, but I need a bit more time checking if it is the correct solution
(unless you have an idea how to solve this [~philipthompson] ?)
> Save repair data to system table
> --------------------------------
>
> Key: CASSANDRA-5839
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5839
> Project: Cassandra
> Issue Type: New Feature
> Components: Core, Tools
> Reporter: Jonathan Ellis
> Assignee: Marcus Eriksson
> Priority: Minor
> Fix For: 3.0
>
> Attachments: 0001-5839.patch, 2.0.4-5839-draft.patch,
> 2.0.6-5839-v2.patch
>
>
> As noted in CASSANDRA-2405, it would be useful to store repair results,
> particularly with sub-range repair available (CASSANDRA-5280).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
