[jira] [Commented] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286184#comment-15286184 ] stone commented on CASSANDRA-11569: --- Have made test on this patch? Actually I have

[jira] [Commented] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288502#comment-15288502 ] stone commented on CASSANDRA-11569: --- set RF=3 > Track message latency across DCs

[jira] [Commented] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288506#comment-15288506 ] stone commented on CASSANDRA-11569: --- use ipfw tool to set datacenter latency. I al

[jira] [Commented] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15290370#comment-15290370 ] stone commented on CASSANDRA-11569: --- thx,what I mean is the value of crossNodeLaten

[jira] [Updated] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stone updated CASSANDRA-11569: -- Attachment: nodeLatency.PNG > Track message latency across DCs > >

[jira] [Commented] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15290374#comment-15290374 ] stone commented on CASSANDRA-11569: --- see nodeLatency.PNG,I change latency from 90ms

[jira] [Comment Edited] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15290374#comment-15290374 ] stone edited comment on CASSANDRA-11569 at 5/19/16 6:12 AM: ---

[jira] [Commented] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293227#comment-15293227 ] stone commented on CASSANDRA-11569: --- I understand the latency calculate method now.

[jira] [Comment Edited] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293227#comment-15293227 ] stone edited comment on CASSANDRA-11569 at 5/20/16 11:58 AM: --

[jira] [Commented] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297707#comment-15297707 ] stone commented on CASSANDRA-11569: --- a new question about cross datacenter latency.

[jira] [Commented] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299277#comment-15299277 ] stone commented on CASSANDRA-11569: --- I konw that,what I confuse about is how to dea

[jira] [Comment Edited] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299277#comment-15299277 ] stone edited comment on CASSANDRA-11569 at 5/25/16 2:08 AM: ---

[jira] [Commented] (CASSANDRA-9555) Don't let offline tools run while cassandra is running

[ https://issues.apache.org/jira/browse/CASSANDRA-9555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15309331#comment-15309331 ] stone commented on CASSANDRA-9555: -- so any patch are available to get? > Don't let o

[jira] [Commented] (CASSANDRA-9555) Don't let offline tools run while cassandra is running

[ https://issues.apache.org/jira/browse/CASSANDRA-9555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15309437#comment-15309437 ] stone commented on CASSANDRA-9555: -- I run sstableexpiredblocker tools in standalone c

[jira] [Comment Edited] (CASSANDRA-9555) Don't let offline tools run while cassandra is running

[ https://issues.apache.org/jira/browse/CASSANDRA-9555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15309437#comment-15309437 ] stone edited comment on CASSANDRA-9555 at 6/1/16 7:03 AM: -- I

[jira] [Comment Edited] (CASSANDRA-9555) Don't let offline tools run while cassandra is running

[ https://issues.apache.org/jira/browse/CASSANDRA-9555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15309437#comment-15309437 ] stone edited comment on CASSANDRA-9555 at 6/1/16 7:12 AM: -- I

[jira] [Created] (CASSANDRA-12404) ColumnFamilyStore.getIfExists

stone created CASSANDRA-12404: - Summary: ColumnFamilyStore.getIfExists Key: CASSANDRA-12404 URL: https://issues.apache.org/jira/browse/CASSANDRA-12404 Project: Cassandra Issue Type: Bug

[jira] [Updated] (CASSANDRA-12404) ColumnFamilyStore.getIfExists

[ https://issues.apache.org/jira/browse/CASSANDRA-12404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stone updated CASSANDRA-12404: -- Description: ColumnFamilyStore.getIfExists("ks","cf") when it does not exist ks.cf,it should return

[jira] [Commented] (CASSANDRA-12257) data consistency of multi datacenter

[ https://issues.apache.org/jira/browse/CASSANDRA-12257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426141#comment-15426141 ] stone commented on CASSANDRA-12257: --- dont think this is same thing. Cassandra-11752

[jira] [Commented] (CASSANDRA-8460) Make it possible to move non-compacting sstables to slow/big storage in DTCS

[ https://issues.apache.org/jira/browse/CASSANDRA-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354399#comment-15354399 ] stone commented on CASSANDRA-8460: -- there are several questions about this issue 1.fr

[jira] [Created] (CASSANDRA-12132) two cassandra nodes have common records,we need to calculate it

stone created CASSANDRA-12132: - Summary: two cassandra nodes have common records,we need to calculate it Key: CASSANDRA-12132 URL: https://issues.apache.org/jira/browse/CASSANDRA-12132 Project: Cassandra

[jira] [Commented] (CASSANDRA-12132) two cassandra nodes have common records,we need to calculate it

[ https://issues.apache.org/jira/browse/CASSANDRA-12132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362133#comment-15362133 ] stone commented on CASSANDRA-12132: --- CF=Each_quorum,RF=3. whenever two nodes down a

[jira] [Commented] (CASSANDRA-8460) Make it possible to move non-compacting sstables to slow/big storage in DTCS

[ https://issues.apache.org/jira/browse/CASSANDRA-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15362257#comment-15362257 ] stone commented on CASSANDRA-8460: -- a simple implement https://github.com/FS136047217

[jira] [Commented] (CASSANDRA-12132) two cassandra nodes have common records,we need to calculate it

[ https://issues.apache.org/jira/browse/CASSANDRA-12132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363833#comment-15363833 ] stone commented on CASSANDRA-12132: --- [~philipthompson] I am not saying this is an i

[jira] [Commented] (CASSANDRA-12132) two cassandra nodes have common records,we need to calculate it

[ https://issues.apache.org/jira/browse/CASSANDRA-12132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365435#comment-15365435 ] stone commented on CASSANDRA-12132: --- yes,this is what i want > two cassandra nodes

[jira] [Created] (CASSANDRA-12257) data consistency of multi datacenter

stone created CASSANDRA-12257: - Summary: data consistency of multi datacenter Key: CASSANDRA-12257 URL: https://issues.apache.org/jira/browse/CASSANDRA-12257 Project: Cassandra Issue Type: Impro

[jira] [Commented] (CASSANDRA-12257) data consistency of multi datacenter

[ https://issues.apache.org/jira/browse/CASSANDRA-12257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388694#comment-15388694 ] stone commented on CASSANDRA-12257: --- need measure the latency between DC real time

[jira] [Comment Edited] (CASSANDRA-12257) data consistency of multi datacenter

[ https://issues.apache.org/jira/browse/CASSANDRA-12257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388694#comment-15388694 ] stone edited comment on CASSANDRA-12257 at 7/22/16 1:15 AM: ---

[jira] [Created] (CASSANDRA-11460) memory leak

stone created CASSANDRA-11460: - Summary: memory leak Key: CASSANDRA-11460 URL: https://issues.apache.org/jira/browse/CASSANDRA-11460 Project: Cassandra Issue Type: Bug Reporter: stone

[jira] [Updated] (CASSANDRA-11460) memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-11460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stone updated CASSANDRA-11460: -- Description: env: cassandra3.3 jdk8 met same problem about this: https://issues.apache.org/jira/br

[jira] [Updated] (CASSANDRA-11460) memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-11460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stone updated CASSANDRA-11460: -- Attachment: aaa.jpg > memory leak > --- > > Key: CASSANDRA-11460 >

[jira] [Updated] (CASSANDRA-11460) memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-11460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stone updated CASSANDRA-11460: -- Description: env: cassandra3.3 jdk8 8G Ram so set MAX_HEAP_SIZE="2G" HEAP_NEWSIZE="400M" 1.met sam

[jira] [Commented] (CASSANDRA-11460) memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-11460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220927#comment-15220927 ] stone commented on CASSANDRA-11460: --- anyone have idea on this? > memory leak > ---

[jira] [Commented] (CASSANDRA-11460) memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-11460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227516#comment-15227516 ] stone commented on CASSANDRA-11460: --- anyone hava idea about this? > memory leak >

[jira] [Commented] (CASSANDRA-9549) Memory leak in Ref.GlobalState due to pathological ConcurrentLinkedQueue.remove behaviour

[ https://issues.apache.org/jira/browse/CASSANDRA-9549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233823#comment-15233823 ] stone commented on CASSANDRA-9549: -- could you take a summary after resolving the issu

[jira] [Commented] (CASSANDRA-11460) memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-11460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234049#comment-15234049 ] stone commented on CASSANDRA-11460: --- this issue is not related to bugCASSANDRA-9549

[jira] [Commented] (CASSANDRA-9549) Memory leak in Ref.GlobalState due to pathological ConcurrentLinkedQueue.remove behaviour

[ https://issues.apache.org/jira/browse/CASSANDRA-9549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15238615#comment-15238615 ] stone commented on CASSANDRA-9549: -- @Benedict Thanks for your answer. I got it. open

[jira] [Updated] (CASSANDRA-11460) memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-11460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stone updated CASSANDRA-11460: -- Tester: Benedict Status: Awaiting Feedback (was: In Progress) > memory leak > --- > >