[jira] [Commented] (CASSANDRA-9142) DC Local repair or -hosts should only be allowed with -full repair

[ https://issues.apache.org/jira/browse/CASSANDRA-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579831#comment-14579831 ] sankalp kohli commented on CASSANDRA-9142: -- I think we should also mark the s

[jira] [Commented] (CASSANDRA-7203) Flush (and Compact) High Traffic Partitions Separately

[ https://issues.apache.org/jira/browse/CASSANDRA-7203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231795#comment-14231795 ] sankalp kohli commented on CASSANDRA-7203: -- " and I think we have bigger fish

[jira] [Commented] (CASSANDRA-8346) Paxos operation can use stale data during multiple range movements

[ https://issues.apache.org/jira/browse/CASSANDRA-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234140#comment-14234140 ] sankalp kohli commented on CASSANDRA-8346: -- Let me review it. > Paxos opera

[jira] [Commented] (CASSANDRA-8346) Paxos operation can use stale data during multiple range movements

[ https://issues.apache.org/jira/browse/CASSANDRA-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234375#comment-14234375 ] sankalp kohli commented on CASSANDRA-8346: -- You want to pass the msg like thi

[jira] [Commented] (CASSANDRA-8346) Paxos operation can use stale data during multiple range movements

[ https://issues.apache.org/jira/browse/CASSANDRA-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14239355#comment-14239355 ] sankalp kohli commented on CASSANDRA-8346: -- I don't think it is related as th

[jira] [Commented] (CASSANDRA-8457) nio MessagingService

[ https://issues.apache.org/jira/browse/CASSANDRA-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249854#comment-14249854 ] sankalp kohli commented on CASSANDRA-8457: -- I agree with [~iamaleksey]. We sh

[jira] [Commented] (CASSANDRA-7979) Acceptable time skew for C*

[ https://issues.apache.org/jira/browse/CASSANDRA-7979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253089#comment-14253089 ] sankalp kohli commented on CASSANDRA-7979: -- This does not detect clock skew.

[jira] [Commented] (CASSANDRA-7979) Acceptable time skew for C*

[ https://issues.apache.org/jira/browse/CASSANDRA-7979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253565#comment-14253565 ] sankalp kohli commented on CASSANDRA-7979: -- "Now I'm using this extreme use c

[jira] [Commented] (CASSANDRA-7979) Acceptable time skew for C*

[ https://issues.apache.org/jira/browse/CASSANDRA-7979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253566#comment-14253566 ] sankalp kohli commented on CASSANDRA-7979: -- [~sebastian.este...@datastax.com]

[jira] [Commented] (CASSANDRA-6246) EPaxos

[ https://issues.apache.org/jira/browse/CASSANDRA-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265909#comment-14265909 ] sankalp kohli commented on CASSANDRA-6246: -- I am a little confused as in how

[jira] [Updated] (CASSANDRA-8194) Reading from Auth table should not be in the request path

[ https://issues.apache.org/jira/browse/CASSANDRA-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-8194: - Assignee: Vishy Kasar > Reading from Auth table should not be in the request path > --

[jira] [Commented] (CASSANDRA-6246) EPaxos

[ https://issues.apache.org/jira/browse/CASSANDRA-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267389#comment-14267389 ] sankalp kohli commented on CASSANDRA-6246: -- Sure. Make sense > EPaxos >

[jira] [Commented] (CASSANDRA-7019) Improve tombstone compactions

[ https://issues.apache.org/jira/browse/CASSANDRA-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269142#comment-14269142 ] sankalp kohli commented on CASSANDRA-7019: -- "7019 is adding major compaction

[jira] [Created] (CASSANDRA-8595) Emit timeouts per endpoint

sankalp kohli created CASSANDRA-8595: Summary: Emit timeouts per endpoint Key: CASSANDRA-8595 URL: https://issues.apache.org/jira/browse/CASSANDRA-8595 Project: Cassandra Issue Type: Impr

[jira] [Resolved] (CASSANDRA-7384) Collect metrics on queries by consistency level

[ https://issues.apache.org/jira/browse/CASSANDRA-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli resolved CASSANDRA-7384. -- Resolution: Won't Fix > Collect metrics on queries by consistency level > --

[jira] [Commented] (CASSANDRA-7384) Collect metrics on queries by consistency level

[ https://issues.apache.org/jira/browse/CASSANDRA-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285097#comment-14285097 ] sankalp kohli commented on CASSANDRA-7384: -- Closing this ticket as won't fix

[jira] [Commented] (CASSANDRA-8649) CAS per (partition key + clustering key) and not only per (partition key)

[ https://issues.apache.org/jira/browse/CASSANDRA-8649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285099#comment-14285099 ] sankalp kohli commented on CASSANDRA-8649: -- +1 for won't fix. > CAS per (pa

[jira] [Commented] (CASSANDRA-8957) Move TRUNCATE from MODIFY to DROP permission group

[ https://issues.apache.org/jira/browse/CASSANDRA-8957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364084#comment-14364084 ] sankalp kohli commented on CASSANDRA-8957: -- [~iamaleksey] Can we create a n

[jira] [Commented] (CASSANDRA-8957) Move TRUNCATE from MODIFY to DROP permission group

[ https://issues.apache.org/jira/browse/CASSANDRA-8957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364245#comment-14364245 ] sankalp kohli commented on CASSANDRA-8957: -- Fair enough > Move TRUNCATE from

[jira] [Commented] (CASSANDRA-6157) Selectively Disable hinted handoff for a data center

[ https://issues.apache.org/jira/browse/CASSANDRA-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376550#comment-14376550 ] sankalp kohli commented on CASSANDRA-6157: -- Look at Jonathan comment. "Requi

[jira] [Commented] (CASSANDRA-5839) Save repair data to system table

[ https://issues.apache.org/jira/browse/CASSANDRA-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378616#comment-14378616 ] sankalp kohli commented on CASSANDRA-5839: -- +1 looks good > Save repair data

[jira] [Assigned] (CASSANDRA-7715) Add a credentials cache to the PasswordAuthenticator

[ https://issues.apache.org/jira/browse/CASSANDRA-7715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli reassigned CASSANDRA-7715: Assignee: sankalp kohli > Add a credentials cache to the PasswordAuthenticator

[jira] [Commented] (CASSANDRA-9129) HintedHandoff in pending state forever after upgrading to 2.0.14 from 2.0.11 and 2.0.12

[ https://issues.apache.org/jira/browse/CASSANDRA-9129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484557#comment-14484557 ] sankalp kohli commented on CASSANDRA-9129: -- The issue is due to CASSANDRA-828

[jira] [Commented] (CASSANDRA-9129) HintedHandoff in pending state forever after upgrading to 2.0.14 from 2.0.11 and 2.0.12

[ https://issues.apache.org/jira/browse/CASSANDRA-9129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484563#comment-14484563 ] sankalp kohli commented on CASSANDRA-9129: -- [~iamaleksey] Is this bug only af

[jira] [Commented] (CASSANDRA-9129) HintedHandoff in pending state forever after upgrading to 2.0.14 from 2.0.11 and 2.0.12

[ https://issues.apache.org/jira/browse/CASSANDRA-9129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485930#comment-14485930 ] sankalp kohli commented on CASSANDRA-9129: -- Its not a problem in some sense b

[jira] [Commented] (CASSANDRA-9151) Anti-compaction is blocking ANTI_ENTROPY stage

[ https://issues.apache.org/jira/browse/CASSANDRA-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487845#comment-14487845 ] sankalp kohli commented on CASSANDRA-9151: -- This affects 2.1.3 and trunk(3.0)

[jira] [Updated] (CASSANDRA-9151) Anti-compaction is blocking ANTI_ENTROPY stage

[ https://issues.apache.org/jira/browse/CASSANDRA-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-9151: - Since Version: 2.1.0 > Anti-compaction is blocking ANTI_ENTROPY stage > -

[jira] [Commented] (CASSANDRA-9143) Improving consistency of repairAt field across replicas

[ https://issues.apache.org/jira/browse/CASSANDRA-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14486455#comment-14486455 ] sankalp kohli commented on CASSANDRA-9143: -- Another improvement we can do is

[jira] [Created] (CASSANDRA-9151) Anti-compaction is blocking ANTI_ENTROPY stage

sankalp kohli created CASSANDRA-9151: Summary: Anti-compaction is blocking ANTI_ENTROPY stage Key: CASSANDRA-9151 URL: https://issues.apache.org/jira/browse/CASSANDRA-9151 Project: Cassandra

[jira] [Created] (CASSANDRA-9142) DC Local repair or -hosts should only be allowed with -full repair

sankalp kohli created CASSANDRA-9142: Summary: DC Local repair or -hosts should only be allowed with -full repair Key: CASSANDRA-9142 URL: https://issues.apache.org/jira/browse/CASSANDRA-9142 Proj

[jira] [Created] (CASSANDRA-9144) Isolate failures at RepairJob level and not RepairSession.

sankalp kohli created CASSANDRA-9144: Summary: Isolate failures at RepairJob level and not RepairSession. Key: CASSANDRA-9144 URL: https://issues.apache.org/jira/browse/CASSANDRA-9144 Project: Ca

[jira] [Commented] (CASSANDRA-9151) Anti-compaction is blocking ANTI_ENTROPY stage

[ https://issues.apache.org/jira/browse/CASSANDRA-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487855#comment-14487855 ] sankalp kohli commented on CASSANDRA-9151: -- This might be causing CASSANDRA-8

[jira] [Commented] (CASSANDRA-8327) snapshots taken before repair are not cleared if snapshot fails

[ https://issues.apache.org/jira/browse/CASSANDRA-8327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14486409#comment-14486409 ] sankalp kohli commented on CASSANDRA-8327: -- I happen to find a place where sn

[jira] [Updated] (CASSANDRA-9143) Improving consistency of repairAt field across replicas

[ https://issues.apache.org/jira/browse/CASSANDRA-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-9143: - Issue Type: Improvement (was: Bug) > Improving consistency of repairAt field across r

[jira] [Created] (CASSANDRA-9143) Improving consistency of repairAt field across replicas

sankalp kohli created CASSANDRA-9143: Summary: Improving consistency of repairAt field across replicas Key: CASSANDRA-9143 URL: https://issues.apache.org/jira/browse/CASSANDRA-9143 Project: Cassan

[jira] [Commented] (CASSANDRA-9143) Improving consistency of repairAt field across replicas

[ https://issues.apache.org/jira/browse/CASSANDRA-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487879#comment-14487879 ] sankalp kohli commented on CASSANDRA-9143: -- Make sense. We can send anticompa

[jira] [Commented] (CASSANDRA-8696) nodetool repair on cassandra 2.1.2 keyspaces return java.lang.RuntimeException: Could not create snapshot

[ https://issues.apache.org/jira/browse/CASSANDRA-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487866#comment-14487866 ] sankalp kohli commented on CASSANDRA-8696: -- This might be due to CASSANDRA-91

[jira] [Assigned] (CASSANDRA-9142) DC Local repair or -hosts should only be allowed with -full repair

[ https://issues.apache.org/jira/browse/CASSANDRA-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli reassigned CASSANDRA-9142: Assignee: sankalp kohli > DC Local repair or -hosts should only be allowed with

[jira] [Created] (CASSANDRA-9145) First RepairJob unregisters RepairSession from FailureDetector

sankalp kohli created CASSANDRA-9145: Summary: First RepairJob unregisters RepairSession from FailureDetector Key: CASSANDRA-9145 URL: https://issues.apache.org/jira/browse/CASSANDRA-9145 Project:

[jira] [Commented] (CASSANDRA-6434) Repair-aware gc grace period

[ https://issues.apache.org/jira/browse/CASSANDRA-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498107#comment-14498107 ] sankalp kohli commented on CASSANDRA-6434: -- Yes we can do that. Once this is

[jira] [Commented] (CASSANDRA-9205) Allow per statement time outs or request cancel method

[ https://issues.apache.org/jira/browse/CASSANDRA-9205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503633#comment-14503633 ] sankalp kohli commented on CASSANDRA-9205: -- We should do this in this way CAS

[jira] [Commented] (CASSANDRA-7168) Add repair aware consistency levels

[ https://issues.apache.org/jira/browse/CASSANDRA-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505783#comment-14505783 ] sankalp kohli commented on CASSANDRA-7168: -- cc [~krummas] I agree with [~sleb

[jira] [Commented] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node

[ https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510017#comment-14510017 ] sankalp kohli commented on CASSANDRA-5901: -- One of the fixes for this could b

[jira] [Commented] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node

[ https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510214#comment-14510214 ] sankalp kohli commented on CASSANDRA-5901: -- That would be ideal however if re

[jira] [Updated] (CASSANDRA-9142) DC Local repair or -hosts should only be allowed with -full repair

[ https://issues.apache.org/jira/browse/CASSANDRA-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-9142: - Attachment: trunk_9142.txt > DC Local repair or -hosts should only be allowed with -fu

[jira] [Assigned] (CASSANDRA-9260) Threadpool in RepairSession is not shutdown on failure

[ https://issues.apache.org/jira/browse/CASSANDRA-9260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli reassigned CASSANDRA-9260: Assignee: sankalp kohli > Threadpool in RepairSession is not shutdown on failur

[jira] [Created] (CASSANDRA-9260) Threadpool in RepairSession is not shutdown on failure

sankalp kohli created CASSANDRA-9260: Summary: Threadpool in RepairSession is not shutdown on failure Key: CASSANDRA-9260 URL: https://issues.apache.org/jira/browse/CASSANDRA-9260 Project: Cassandr

[jira] [Commented] (CASSANDRA-9260) Threadpool in RepairSession is not shutdown on failure

[ https://issues.apache.org/jira/browse/CASSANDRA-9260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518392#comment-14518392 ] sankalp kohli commented on CASSANDRA-9260: -- This patch also fixes a visibilit

[jira] [Updated] (CASSANDRA-9260) Threadpool in RepairSession is not shutdown on failure

[ https://issues.apache.org/jira/browse/CASSANDRA-9260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-9260: - Attachment: trunk_9260.txt > Threadpool in RepairSession is not shutdown on failure >

[jira] [Created] (CASSANDRA-9261) Prepare and Snapshot for repairs should use higher timeouts for expiring map

sankalp kohli created CASSANDRA-9261: Summary: Prepare and Snapshot for repairs should use higher timeouts for expiring map Key: CASSANDRA-9261 URL: https://issues.apache.org/jira/browse/CASSANDRA-9261

[jira] [Updated] (CASSANDRA-9261) Prepare and Snapshot for repairs should use higher timeouts for expiring map

[ https://issues.apache.org/jira/browse/CASSANDRA-9261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-9261: - Attachment: trunk_9261.txt > Prepare and Snapshot for repairs should use higher timeou

[jira] [Assigned] (CASSANDRA-9261) Prepare and Snapshot for repairs should use higher timeouts for expiring map

[ https://issues.apache.org/jira/browse/CASSANDRA-9261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli reassigned CASSANDRA-9261: Assignee: sankalp kohli > Prepare and Snapshot for repairs should use higher ti

[jira] [Commented] (CASSANDRA-9261) Prepare and Snapshot for repairs should use higher timeouts for expiring map

[ https://issues.apache.org/jira/browse/CASSANDRA-9261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518411#comment-14518411 ] sankalp kohli commented on CASSANDRA-9261: -- In this patch, snapshot command w

[jira] [Created] (CASSANDRA-9262) IncomingTcpConnection thread is not named

sankalp kohli created CASSANDRA-9262: Summary: IncomingTcpConnection thread is not named Key: CASSANDRA-9262 URL: https://issues.apache.org/jira/browse/CASSANDRA-9262 Project: Cassandra I

[jira] [Assigned] (CASSANDRA-9262) IncomingTcpConnection thread is not named

[ https://issues.apache.org/jira/browse/CASSANDRA-9262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli reassigned CASSANDRA-9262: Assignee: sankalp kohli > IncomingTcpConnection thread is not named > -

[jira] [Updated] (CASSANDRA-9262) IncomingTcpConnection thread is not named

[ https://issues.apache.org/jira/browse/CASSANDRA-9262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-9262: - Attachment: trunk_9262.txt > IncomingTcpConnection thread is not named > -

[jira] [Commented] (CASSANDRA-9261) Prepare and Snapshot for repairs should use higher timeouts for expiring map

[ https://issues.apache.org/jira/browse/CASSANDRA-9261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522023#comment-14522023 ] sankalp kohli commented on CASSANDRA-9261: -- [~yukim] Do you need a new patch

[jira] [Commented] (CASSANDRA-9151) Anti-compaction is blocking ANTI_ENTROPY stage

[ https://issues.apache.org/jira/browse/CASSANDRA-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522067#comment-14522067 ] sankalp kohli commented on CASSANDRA-9151: -- I am +1 on the patch which I appl

[jira] [Commented] (CASSANDRA-9261) Prepare and Snapshot for repairs should use higher timeouts for expiring map

[ https://issues.apache.org/jira/browse/CASSANDRA-9261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522613#comment-14522613 ] sankalp kohli commented on CASSANDRA-9261: -- +1 > Prepare and Snapshot for re

[jira] [Created] (CASSANDRA-5842) Cassandra should ignore sstables which it could not delete.

sankalp kohli created CASSANDRA-5842: Summary: Cassandra should ignore sstables which it could not delete. Key: CASSANDRA-5842 URL: https://issues.apache.org/jira/browse/CASSANDRA-5842 Project: C

[jira] [Created] (CASSANDRA-5843) SStableReader should enforce through code that no one creates multiple objects of it for same sstable.

sankalp kohli created CASSANDRA-5843: Summary: SStableReader should enforce through code that no one creates multiple objects of it for same sstable. Key: CASSANDRA-5843 URL: https://issues.apache.org/jira/br

[jira] [Commented] (CASSANDRA-5843) SStableReader should enforce through code that no one creates multiple objects of it for same sstable.

[ https://issues.apache.org/jira/browse/CASSANDRA-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728377#comment-13728377 ] sankalp kohli commented on CASSANDRA-5843: -- That was really fast.

[jira] [Comment Edited] (CASSANDRA-5843) SStableReader should enforce through code that no one creates multiple objects of it for same sstable.

[ https://issues.apache.org/jira/browse/CASSANDRA-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728377#comment-13728377 ] sankalp kohli edited comment on CASSANDRA-5843 at 8/3/13 1:30 AM: --

[jira] [Commented] (CASSANDRA-5791) A nodetool command to validate all sstables in a node

[ https://issues.apache.org/jira/browse/CASSANDRA-5791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740301#comment-13740301 ] sankalp kohli commented on CASSANDRA-5791: -- We might also want to check wheth

[jira] [Created] (CASSANDRA-5891) Scrub disk footprint needs to be reduced

sankalp kohli created CASSANDRA-5891: Summary: Scrub disk footprint needs to be reduced Key: CASSANDRA-5891 URL: https://issues.apache.org/jira/browse/CASSANDRA-5891 Project: Cassandra Is

[jira] [Created] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node

sankalp kohli created CASSANDRA-5901: Summary: Bootstrap should also make the data consistent on the new node Key: CASSANDRA-5901 URL: https://issues.apache.org/jira/browse/CASSANDRA-5901 Project:

[jira] [Commented] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node

[ https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744500#comment-13744500 ] sankalp kohli commented on CASSANDRA-5901: -- If you have stale data in one nod

[jira] [Commented] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node

[ https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744522#comment-13744522 ] sankalp kohli commented on CASSANDRA-5901: -- Hinted Handoff is best effort I g

[jira] [Commented] (CASSANDRA-5988) Make hint TTL customizable

[ https://issues.apache.org/jira/browse/CASSANDRA-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762414#comment-13762414 ] sankalp kohli commented on CASSANDRA-5988: -- We also want to make sure that hi

[jira] [Created] (CASSANDRA-6044) FailureDetectorMBean should expose an integer of machines which are up and down.

sankalp kohli created CASSANDRA-6044: Summary: FailureDetectorMBean should expose an integer of machines which are up and down. Key: CASSANDRA-6044 URL: https://issues.apache.org/jira/browse/CASSANDRA-6044

[jira] [Commented] (CASSANDRA-6044) FailureDetectorMBean should expose an integer of machines which are up and down.

[ https://issues.apache.org/jira/browse/CASSANDRA-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769922#comment-13769922 ] sankalp kohli commented on CASSANDRA-6044: -- The reason for this is that some

[jira] [Updated] (CASSANDRA-6044) FailureDetectorMBean should expose an integer of machines which are up and down.

[ https://issues.apache.org/jira/browse/CASSANDRA-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-6044: - Assignee: sankalp kohli (was: Brandon Williams) > FailureDetectorMBean should ex

[jira] [Commented] (CASSANDRA-6044) FailureDetectorMBean should expose an integer of machines which are up and down.

[ https://issues.apache.org/jira/browse/CASSANDRA-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770073#comment-13770073 ] sankalp kohli commented on CASSANDRA-6044: -- Well I can assign it to myself :)

[jira] [Commented] (CASSANDRA-5932) Speculative read performance data show unexpected results

[ https://issues.apache.org/jira/browse/CASSANDRA-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770170#comment-13770170 ] sankalp kohli commented on CASSANDRA-5932: -- SpeculateAlwaysExecutor - Here we

[jira] [Commented] (CASSANDRA-6042) Add WARN when there are a lot of tombstones in a query

[ https://issues.apache.org/jira/browse/CASSANDRA-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771189#comment-13771189 ] sankalp kohli commented on CASSANDRA-6042: -- Should I update the JIRA title or

[jira] [Commented] (CASSANDRA-6042) Add WARN when there are a lot of tombstones in a query

[ https://issues.apache.org/jira/browse/CASSANDRA-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771188#comment-13771188 ] sankalp kohli commented on CASSANDRA-6042: -- It will also be good to emit JMX

[jira] [Created] (CASSANDRA-6057) JMX Metric for number of tombstones per read

sankalp kohli created CASSANDRA-6057: Summary: JMX Metric for number of tombstones per read Key: CASSANDRA-6057 URL: https://issues.apache.org/jira/browse/CASSANDRA-6057 Project: Cassandra

[jira] [Commented] (CASSANDRA-4736) Cassandra should expose a native existence check API

[ https://issues.apache.org/jira/browse/CASSANDRA-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773581#comment-13773581 ] sankalp kohli commented on CASSANDRA-4736: -- No. We want to check whether a pa

[jira] [Commented] (CASSANDRA-4736) Cassandra should expose a native existence check API

[ https://issues.apache.org/jira/browse/CASSANDRA-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773885#comment-13773885 ] sankalp kohli commented on CASSANDRA-4736: -- Got your argument. Yes we sometim

[jira] [Updated] (CASSANDRA-4925) Failure Detector should log or ignore sudden time change to the past

[ https://issues.apache.org/jira/browse/CASSANDRA-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-4925: - Assignee: sankalp kohli > Failure Detector should log or ignore sudden time chang

[jira] [Updated] (CASSANDRA-4650) RangeStreamer should be smarter when picking endpoints for streaming in case of N >=3 in each DC.

[ https://issues.apache.org/jira/browse/CASSANDRA-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-4650: - Assignee: sankalp kohli > RangeStreamer should be smarter when picking endpoints

[jira] [Commented] (CASSANDRA-2834) Avoid repair getting started twice at the same time for the same CF

[ https://issues.apache.org/jira/browse/CASSANDRA-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782465#comment-13782465 ] sankalp kohli commented on CASSANDRA-2834: -- Running two repairs on the same C

[jira] [Updated] (CASSANDRA-2848) Make the Client API support passing down timeouts

[ https://issues.apache.org/jira/browse/CASSANDRA-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-2848: - Component/s: Core > Make the Client API support passing down timeouts > -

[jira] [Commented] (CASSANDRA-2848) Make the Client API support passing down timeouts

[ https://issues.apache.org/jira/browse/CASSANDRA-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784287#comment-13784287 ] sankalp kohli commented on CASSANDRA-2848: -- This will be very useful for read

[jira] [Comment Edited] (CASSANDRA-2848) Make the Client API support passing down timeouts

[ https://issues.apache.org/jira/browse/CASSANDRA-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784287#comment-13784287 ] sankalp kohli edited comment on CASSANDRA-2848 at 10/2/13 7:00 PM: -

[jira] [Commented] (CASSANDRA-5683) Write timeout in multi-dc environment

[ https://issues.apache.org/jira/browse/CASSANDRA-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784398#comment-13784398 ] sankalp kohli commented on CASSANDRA-5683: -- Timeouts will differ based on a c

[jira] [Commented] (CASSANDRA-2848) Make the Client API support passing down timeouts

[ https://issues.apache.org/jira/browse/CASSANDRA-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788390#comment-13788390 ] sankalp kohli commented on CASSANDRA-2848: -- So what we can do is that rpc spe

[jira] [Created] (CASSANDRA-6157) Selectively Disable hinted handoff for a data center

sankalp kohli created CASSANDRA-6157: Summary: Selectively Disable hinted handoff for a data center Key: CASSANDRA-6157 URL: https://issues.apache.org/jira/browse/CASSANDRA-6157 Project: Cassandra

[jira] [Created] (CASSANDRA-6158) Nodetool command to purge hints

sankalp kohli created CASSANDRA-6158: Summary: Nodetool command to purge hints Key: CASSANDRA-6158 URL: https://issues.apache.org/jira/browse/CASSANDRA-6158 Project: Cassandra Issue Type:

[jira] [Updated] (CASSANDRA-6044) FailureDetectorMBean should expose an integer of machines which are up and down.

[ https://issues.apache.org/jira/browse/CASSANDRA-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-6044: - Attachment: trunk-6044.patch > FailureDetectorMBean should expose an integer of machi

[jira] [Updated] (CASSANDRA-4925) Failure Detector should log or ignore sudden time change to the past

[ https://issues.apache.org/jira/browse/CASSANDRA-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-4925: - Attachment: trunk-4925.patch Changed Double to Long in BoundedStatsDeque. Changed the

[jira] [Updated] (CASSANDRA-4925) Failure Detector should log or ignore sudden time change to the past

[ https://issues.apache.org/jira/browse/CASSANDRA-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-4925: - Attachment: (was: trunk-4925.patch) > Failure Detector should log or ignore sudde

[jira] [Updated] (CASSANDRA-4925) Failure Detector should log or ignore sudden time change to the past

[ https://issues.apache.org/jira/browse/CASSANDRA-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-4925: - Attachment: trunk-4925.patch With the Gossiper milli fix > Failure Detector should l

[jira] [Comment Edited] (CASSANDRA-4925) Failure Detector should log or ignore sudden time change to the past

[ https://issues.apache.org/jira/browse/CASSANDRA-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789412#comment-13789412 ] sankalp kohli edited comment on CASSANDRA-4925 at 10/8/13 5:23 PM: -

[jira] [Updated] (CASSANDRA-4650) RangeStreamer should be smarter when picking endpoints for streaming in case of N >=3 in each DC.

[ https://issues.apache.org/jira/browse/CASSANDRA-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sankalp kohli updated CASSANDRA-4650: - Attachment: photo-1.JPG > RangeStreamer should be smarter when picking endpoints for

[jira] [Commented] (CASSANDRA-4650) RangeStreamer should be smarter when picking endpoints for streaming in case of N >=3 in each DC.

[ https://issues.apache.org/jira/browse/CASSANDRA-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789969#comment-13789969 ] sankalp kohli commented on CASSANDRA-4650: -- This will be very useful for vnod

[jira] [Comment Edited] (CASSANDRA-4650) RangeStreamer should be smarter when picking endpoints for streaming in case of N >=3 in each DC.

[ https://issues.apache.org/jira/browse/CASSANDRA-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789969#comment-13789969 ] sankalp kohli edited comment on CASSANDRA-4650 at 10/9/13 3:06 AM: -

[jira] [Comment Edited] (CASSANDRA-4650) RangeStreamer should be smarter when picking endpoints for streaming in case of N >=3 in each DC.

[ https://issues.apache.org/jira/browse/CASSANDRA-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789969#comment-13789969 ] sankalp kohli edited comment on CASSANDRA-4650 at 10/9/13 3:05 AM: -

[jira] [Commented] (CASSANDRA-4925) Failure Detector should log or ignore sudden time change to the past

[ https://issues.apache.org/jira/browse/CASSANDRA-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790631#comment-13790631 ] sankalp kohli commented on CASSANDRA-4925: -- Yes now I am doing (Gossiper.inte

[jira] [Commented] (CASSANDRA-4925) Failure Detector should log or ignore sudden time change to the past

[ https://issues.apache.org/jira/browse/CASSANDRA-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791182#comment-13791182 ] sankalp kohli commented on CASSANDRA-4925: -- I wanted to check whether passing

<    2   3   4   5   6   7   8   9   10   11   >