[
https://issues.apache.org/jira/browse/CASSANDRA-12846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15611143#comment-15611143
]
Romain Hardouin commented on CASSANDRA-12846:
---------------------------------------------
Hi,
It seems the cassandra user mailing list is more appropriate to ask this kind
of questions.
|Writing to the list|[email protected]|
|Subscription address|[email protected]|
|Unsubscription addresses|[email protected]|
|Archives|http://mail-archives.apache.org/mod_mbox/cassandra-user/|
Also, be sure to provide as many details as possible:
* Cassandra version
* What kind of repair (full, incremental)? You can paste the nodetool repair
command you are using or mention the tool e.g. cassandra-reaper.
* Number of vnodes or single token
* Number of nodes per datacenter, are datacenter in different regions (EU, US,
Asia, ...)?
* Is your data model prone to wide rows?
* Physical server or VM specs (CPU, RAM)
* JVM details (version, GC: CMS or G1?, Heap size)
* etc.
> Repair is taking too much time
> -------------------------------
>
> Key: CASSANDRA-12846
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12846
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Nanda Kishore Tokala
>
> we are having are only 300 MB data on each node but repair is taking nearly 3
> hours. Can you please suggest me what needs me checked and improved
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
