[
https://issues.apache.org/jira/browse/CASSANDRA-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14528754#comment-14528754
]
Philip Thompson edited comment on CASSANDRA-5839 at 5/5/15 10:30 PM:
---------------------------------------------------------------------
communicate() immediately after create is definitely not the correct solution,
I have tested this. You're saying logback is being deadlocked, not anything in
Python? So we need to clear the buffers faster in Python?
was (Author: philipthompson):
communicate() seems to be the correct solution based on the python
documentation. If you're sure the dtest issue is exclusively in ccm and not in
C*, there's no need to keep this re-opened. Just file an issue on the CCM repo.
> 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)
