[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13779715#comment-13779715 ] Christopher Smith commented on CASSANDRA-6106: -- Ah, you are right about

[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13779718#comment-13779718 ] Christopher Smith commented on CASSANDRA-6106: -- As for my proposed

[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13779804#comment-13779804 ] Sylvain Lebresne commented on CASSANDRA-6106: - I agree it would be nice to

[jira] [Commented] (CASSANDRA-5906) Avoid allocating over-large bloom filters

[ https://issues.apache.org/jira/browse/CASSANDRA-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13779946#comment-13779946 ] Jonathan Ellis commented on CASSANDRA-5906: --- That's starting to get to be a

[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13779985#comment-13779985 ] Jonathan Ellis commented on CASSANDRA-6106: --- bq. I'm assuming here that

[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13779983#comment-13779983 ] Jonathan Ellis commented on CASSANDRA-6106: --- I like it. I'd be inclined to

[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13779988#comment-13779988 ] Sylvain Lebresne commented on CASSANDRA-6106: - bq. noting that we have

[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-tabpanelfocusedCommentId=13779994#comment-13779994 ] Ryan McGuire commented on CASSANDRA-5932: - The good news is that speculative

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

[ https://issues.apache.org/jira/browse/CASSANDRA-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McGuire updated CASSANDRA-5932: Attachment: 5933-logs.tar.gz 5933-128_and_200rc1.png

[jira] [Comment Edited] (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-tabpanelfocusedCommentId=13779994#comment-13779994 ] Ryan McGuire edited comment on CASSANDRA-5932 at 9/27/13 2:56 PM:

[jira] [Comment Edited] (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-tabpanelfocusedCommentId=13779994#comment-13779994 ] Ryan McGuire edited comment on CASSANDRA-5932 at 9/27/13 2:58 PM:

[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-tabpanelfocusedCommentId=13779997#comment-13779997 ] Jeremiah Jordan commented on CASSANDRA-5932: Yeah. The graphs for ALWAYS

[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-tabpanelfocusedCommentId=1377#comment-1377 ] Ryan McGuire commented on CASSANDRA-5932: - The other thing that I note, is

[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-tabpanelfocusedCommentId=13780003#comment-13780003 ] Jonathan Ellis commented on CASSANDRA-5932: --- Hmm. I wonder if it's just

[jira] [Created] (CASSANDRA-6107) CQL3 Batch statement memory leak

Constance Eustace created CASSANDRA-6107: Summary: CQL3 Batch statement memory leak Key: CASSANDRA-6107 URL: https://issues.apache.org/jira/browse/CASSANDRA-6107 Project: Cassandra

[jira] [Updated] (CASSANDRA-6107) CQL3 Batch statement memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Constance Eustace updated CASSANDRA-6107: - Description: We are doing large volume insert/update tests on a CASS via

[jira] [Commented] (CASSANDRA-6107) CQL3 Batch statement memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780018#comment-13780018 ] Constance Eustace commented on CASSANDRA-6107: -- - Further examination of

[jira] [Commented] (CASSANDRA-6107) CQL3 Batch statement memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780037#comment-13780037 ] Constance Eustace commented on CASSANDRA-6107: -- It appears that since we

[jira] [Updated] (CASSANDRA-6107) CQL3 Batch statement memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-6107: Priority: Minor (was: Critical) CQL3 Batch statement memory leak

[jira] [Commented] (CASSANDRA-6107) CQL3 Batch statement memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780045#comment-13780045 ] Sylvain Lebresne commented on CASSANDRA-6107: - bq. but shouldn't there be

[jira] [Commented] (CASSANDRA-6107) CQL3 Batch statement memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780049#comment-13780049 ] Constance Eustace commented on CASSANDRA-6107: -- It appears you are using

[jira] [Commented] (CASSANDRA-6107) CQL3 Batch statement memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780053#comment-13780053 ] Constance Eustace commented on CASSANDRA-6107: -- I agree, there is client

[jira] [Commented] (CASSANDRA-6107) CQL3 Batch statement memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780066#comment-13780066 ] Constance Eustace commented on CASSANDRA-6107: -- We're using SpringJDBC on

[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-tabpanelfocusedCommentId=13780072#comment-13780072 ] Brandon Williams commented on CASSANDRA-5932: - Couldn't we just do a run

[jira] [Commented] (CASSANDRA-6107) CQL3 Batch statement memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780073#comment-13780073 ] Jonathan Ellis commented on CASSANDRA-6107: --- Could we fix the OOM by adding

[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-tabpanelfocusedCommentId=13780074#comment-13780074 ] Jonathan Ellis commented on CASSANDRA-5932: --- That still gives you

[jira] [Commented] (CASSANDRA-5906) Avoid allocating over-large bloom filters

[ https://issues.apache.org/jira/browse/CASSANDRA-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780084#comment-13780084 ] Jonathan Ellis commented on CASSANDRA-5906: --- Also, this is more involved

[jira] [Commented] (CASSANDRA-6107) CQL3 Batch statement memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780083#comment-13780083 ] Sylvain Lebresne commented on CASSANDRA-6107: - Given that prepared is not

[jira] [Updated] (CASSANDRA-6107) CQL3 Batch statement memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-6107: -- Assignee: Lyuben Todorov That sounds reasonable. I'd actually just pin it as

[jira] [Commented] (CASSANDRA-6107) CQL3 Batch statement memory leak

[ https://issues.apache.org/jira/browse/CASSANDRA-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780095#comment-13780095 ] Constance Eustace commented on CASSANDRA-6107: -- Yep, removing statement

[jira] [Commented] (CASSANDRA-5906) Avoid allocating over-large bloom filters

[ https://issues.apache.org/jira/browse/CASSANDRA-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780098#comment-13780098 ] Yuki Morishita commented on CASSANDRA-5906: --- bq. Should we target for 2.1?

[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-tabpanelfocusedCommentId=13780102#comment-13780102 ] Ryan McGuire commented on CASSANDRA-5932: - This looks exactly what I was

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

[ https://issues.apache.org/jira/browse/CASSANDRA-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McGuire updated CASSANDRA-5932: Attachment: 5933-randomized-dsnitch-replica.png Speculative read performance data

[jira] [Comment Edited] (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-tabpanelfocusedCommentId=13780102#comment-13780102 ] Ryan McGuire edited comment on CASSANDRA-5932 at 9/27/13 5:15 PM:

[jira] [Updated] (CASSANDRA-4681) SlabAllocator spends a lot of time in Thread.yield

[ https://issues.apache.org/jira/browse/CASSANDRA-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-4681: -- Attachment: 4691-v3-rebased.txt Rebased to trunk. [~enigmacurry], can we test

[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-tabpanelfocusedCommentId=13780113#comment-13780113 ] Jonathan Ellis commented on CASSANDRA-5932: --- That's awesome. Can you test

[jira] [Updated] (CASSANDRA-4681) SlabAllocator spends a lot of time in Thread.yield

[ https://issues.apache.org/jira/browse/CASSANDRA-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McGuire updated CASSANDRA-4681: Tester: enigmacurry SlabAllocator spends a lot of time in Thread.yield

[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] [Updated] (CASSANDRA-5515) Track sstable coldness

[ https://issues.apache.org/jira/browse/CASSANDRA-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Hobbs updated CASSANDRA-5515: --- Attachment: 5515-2.0-v2.txt 5515-2.0-v2.txt moves the row clearing to

[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780152#comment-13780152 ] Christopher Smith commented on CASSANDRA-6106: -- I agree there are two

[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780173#comment-13780173 ] Christopher Smith commented on CASSANDRA-6106: -- I should clarify my

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

[ https://issues.apache.org/jira/browse/CASSANDRA-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McGuire updated CASSANDRA-5932: Attachment: 5933-randomized-dsnitch-replica.2.png Speculative read performance

[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-tabpanelfocusedCommentId=13780228#comment-13780228 ] Ryan McGuire commented on CASSANDRA-5932: - Seems like it's quite tunable, but

[jira] [Comment Edited] (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-tabpanelfocusedCommentId=13780228#comment-13780228 ] Ryan McGuire edited comment on CASSANDRA-5932 at 9/27/13 6:49 PM:

[jira] [Commented] (CASSANDRA-6053) system.peers table not updated after decommissioning nodes in C* 2.0

[ https://issues.apache.org/jira/browse/CASSANDRA-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780245#comment-13780245 ] Christopher J. Bottaro commented on CASSANDRA-6053: --- Is there a way

[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780267#comment-13780267 ] Christopher Smith commented on CASSANDRA-6106: -- Regarding resyncing the

[jira] [Commented] (CASSANDRA-6053) system.peers table not updated after decommissioning nodes in C* 2.0

[ https://issues.apache.org/jira/browse/CASSANDRA-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780277#comment-13780277 ] Brandon Williams commented on CASSANDRA-6053: - You can simply delete them

[jira] [Commented] (CASSANDRA-6053) system.peers table not updated after decommissioning nodes in C* 2.0

[ https://issues.apache.org/jira/browse/CASSANDRA-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780281#comment-13780281 ] Brandon Williams commented on CASSANDRA-6053: - Not sure how this can

[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780287#comment-13780287 ] Sylvain Lebresne commented on CASSANDRA-6106: - bq. if a new node comes on,

[jira] [Comment Edited] (CASSANDRA-5515) Track sstable coldness

[ https://issues.apache.org/jira/browse/CASSANDRA-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780150#comment-13780150 ] Tyler Hobbs edited comment on CASSANDRA-5515 at 9/27/13 7:26 PM:

[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-tabpanelfocusedCommentId=13780298#comment-13780298 ] Jonathan Ellis commented on CASSANDRA-5932: --- Yeah, that makes sense.

[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-tabpanelfocusedCommentId=13780307#comment-13780307 ] Jonathan Ellis commented on CASSANDRA-5932: --- Also, did that stress patch

[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780318#comment-13780318 ] Christopher Smith commented on CASSANDRA-6106: -- {quote} Given the fact we

[jira] [Updated] (CASSANDRA-6016) Ability to change replication factor for the trace keyspace

[ https://issues.apache.org/jira/browse/CASSANDRA-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuki Morishita updated CASSANDRA-6016: -- Attachment: 6016-2.0.txt I think the most straight way to achieve this it to allow

[jira] [Updated] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Smith updated CASSANDRA-6106: - Attachment: microtimstamp_random.patch An alternate resolution to the

[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780336#comment-13780336 ] Christopher Smith commented on CASSANDRA-6106: -- OUt of curiosity, is

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

[ https://issues.apache.org/jira/browse/CASSANDRA-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McGuire updated CASSANDRA-5932: Attachment: 5933-randomized-dsnitch-replica.3.png Speculative read performance

[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-tabpanelfocusedCommentId=13780413#comment-13780413 ] Ryan McGuire commented on CASSANDRA-5932: - Here's 99th and 99.9th percentiles:

[jira] [Commented] (CASSANDRA-6053) system.peers table not updated after decommissioning nodes in C* 2.0

[ https://issues.apache.org/jira/browse/CASSANDRA-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780421#comment-13780421 ] Christopher J. Bottaro commented on CASSANDRA-6053: --- I did a

[jira] [Comment Edited] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780336#comment-13780336 ] Christopher Smith edited comment on CASSANDRA-6106 at 9/27/13 9:20 PM:

[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-tabpanelfocusedCommentId=13780457#comment-13780457 ] Jonathan Ellis commented on CASSANDRA-5932: --- Starting to think we still have

[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-tabpanelfocusedCommentId=13780475#comment-13780475 ] Jonathan Ellis commented on CASSANDRA-5932: --- Maybe the problem is that we're

[jira] [Updated] (CASSANDRA-5239) Asynchronous (non-blocking) StorageProxy

[ https://issues.apache.org/jira/browse/CASSANDRA-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5239: -- Summary: Asynchronous (non-blocking) StorageProxy (was: Fully Aysnc Server

[jira] [Updated] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Smith updated CASSANDRA-6106: - Attachment: microtimstamp_random_rev2.patch I realized the random patch had

[jira] [Commented] (CASSANDRA-6106) QueryState.getTimestamp() FBUtilities.timestampMicros() reads current timestamp with System.currentTimeMillis() * 1000 instead of System.nanoTime() / 1000

[ https://issues.apache.org/jira/browse/CASSANDRA-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780521#comment-13780521 ] Christopher Smith commented on CASSANDRA-6106: -- The issue behind the rev2

[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-tabpanelfocusedCommentId=13780524#comment-13780524 ] Jonathan Ellis commented on CASSANDRA-5932: --- Pretty sure that's our smoking

[jira] [Updated] (CASSANDRA-5239) Asynchronous (non-blocking) StorageProxy

[ https://issues.apache.org/jira/browse/CASSANDRA-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5239: -- Labels: performance (was: ) Asynchronous (non-blocking) StorageProxy

[jira] [Updated] (CASSANDRA-5663) Add write batching for the native protocol

[ https://issues.apache.org/jira/browse/CASSANDRA-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5663: -- Priority: Major (was: Minor) Add write batching for the native protocol

[jira] [Updated] (CASSANDRA-5239) Asynchronous (non-blocking) StorageProxy

[ https://issues.apache.org/jira/browse/CASSANDRA-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5239: -- Priority: Major (was: Minor) Asynchronous (non-blocking) StorageProxy

[jira] [Commented] (CASSANDRA-6016) Ability to change replication factor for the trace keyspace

[ https://issues.apache.org/jira/browse/CASSANDRA-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780529#comment-13780529 ] Jonathan Ellis commented on CASSANDRA-6016: --- Does that actually work? I

[jira] [Assigned] (CASSANDRA-5818) Duplicated error messages on directory creation error at startup

[ https://issues.apache.org/jira/browse/CASSANDRA-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis reassigned CASSANDRA-5818: - Assignee: Lyuben Todorov (was: Aleksey Yeschenko) Duplicated error

[jira] [Assigned] (CASSANDRA-5957) Cannot drop keyspace Keyspace1 after running cassandra-stress

[ https://issues.apache.org/jira/browse/CASSANDRA-5957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis reassigned CASSANDRA-5957: - Assignee: Yuki Morishita (was: Aleksey Yeschenko) Cannot drop keyspace

[jira] [Updated] (CASSANDRA-5374) Errors while opening SSTables on Cassandra start after an outage

[ https://issues.apache.org/jira/browse/CASSANDRA-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5374: -- Assignee: (was: Aleksey Yeschenko) Has anyone seen this on 1.2.x?

[jira] [Updated] (CASSANDRA-5019) Still too much object allocation on reads

[ https://issues.apache.org/jira/browse/CASSANDRA-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5019: -- Assignee: (was: Aleksey Yeschenko) Still too much object allocation on

[jira] [Updated] (CASSANDRA-5561) Compaction strategy that minimizes re-compaction of old/frozen data

[ https://issues.apache.org/jira/browse/CASSANDRA-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5561: -- Assignee: (was: Aleksey Yeschenko) Compaction strategy that minimizes

[jira] [Updated] (CASSANDRA-6068) Support login/password auth in cassandra-stress

[ https://issues.apache.org/jira/browse/CASSANDRA-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-6068: -- Assignee: (was: Aleksey Yeschenko) Support login/password auth in

[jira] [Commented] (CASSANDRA-6053) system.peers table not updated after decommissioning nodes in C* 2.0

[ https://issues.apache.org/jira/browse/CASSANDRA-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780571#comment-13780571 ] Brandon Williams commented on CASSANDRA-6053: - Yes.

git commit: make sequential nodetool repair the default patch by ltodorov reviewed by dbrosius for cassandra-5950

Updated Branches: refs/heads/cassandra-2.0 2fb089e4c - 3a7093356 make sequential nodetool repair the default patch by ltodorov reviewed by dbrosius for cassandra-5950 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[2/2] git commit: Merge branch 'cassandra-2.0' into trunk

Merge branch 'cassandra-2.0' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/fe54388b Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/fe54388b Diff:

[1/2] git commit: make sequential nodetool repair the default patch by ltodorov reviewed by dbrosius for cassandra-5950

Updated Branches: refs/heads/trunk bce594f38 - fe54388ba make sequential nodetool repair the default patch by ltodorov reviewed by dbrosius for cassandra-5950 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[1/2] git commit: fix typo in test

Updated Branches: refs/heads/cassandra-2.0 3a7093356 - ed7b08b39 fix typo in test Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/8d3d67e5 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/8d3d67e5 Diff:

[2/2] git commit: Merge branch 'cassandra-1.2' into cassandra-2.0

Merge branch 'cassandra-1.2' into cassandra-2.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/ed7b08b3 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/ed7b08b3 Diff:

git commit: fix typo in test

Updated Branches: refs/heads/cassandra-1.2 bdb269af0 - 8d3d67e5f fix typo in test Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/8d3d67e5 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/8d3d67e5 Diff:

[1/3] git commit: fix typo in test

Updated Branches: refs/heads/trunk fe54388ba - bb8e95c2b fix typo in test Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/8d3d67e5 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/8d3d67e5 Diff:

[3/3] git commit: Merge branch 'cassandra-2.0' into trunk

Merge branch 'cassandra-2.0' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/bb8e95c2 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/bb8e95c2 Diff:

[2/3] git commit: Merge branch 'cassandra-1.2' into cassandra-2.0

Merge branch 'cassandra-1.2' into cassandra-2.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/ed7b08b3 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/ed7b08b3 Diff:

[jira] [Commented] (CASSANDRA-6103) ConcurrentModificationException in TokenMetadata.cloneOnlyTokenMap

[ https://issues.apache.org/jira/browse/CASSANDRA-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780651#comment-13780651 ] dan jatnieks commented on CASSANDRA-6103: - I've run into the same error a

[jira] [Commented] (CASSANDRA-6103) ConcurrentModificationException in TokenMetadata.cloneOnlyTokenMap

[ https://issues.apache.org/jira/browse/CASSANDRA-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780667#comment-13780667 ] Mikhail Stepura commented on CASSANDRA-6103: I'm curious, each access to

[jira] [Commented] (CASSANDRA-5374) Errors while opening SSTables on Cassandra start after an outage

[ https://issues.apache.org/jira/browse/CASSANDRA-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780686#comment-13780686 ] Arya Goudarzi commented on CASSANDRA-5374: -- I haven't seen it. I am running

[jira] [Updated] (CASSANDRA-6102) CassandraStorage broken for bigints and ints

[ https://issues.apache.org/jira/browse/CASSANDRA-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Liu updated CASSANDRA-6102: Attachment: 6102-1.2-branch.txt CassandraStorage broken for bigints and ints

[jira] [Commented] (CASSANDRA-6102) CassandraStorage broken for bigints and ints

[ https://issues.apache.org/jira/browse/CASSANDRA-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780701#comment-13780701 ] Alex Liu commented on CASSANDRA-6102: - For regular Cql table e.g. {code} CREATE

[jira] [Commented] (CASSANDRA-6102) CassandraStorage broken for bigints and ints

[ https://issues.apache.org/jira/browse/CASSANDRA-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780702#comment-13780702 ] Alex Liu commented on CASSANDRA-6102: - For compact storage cql table, we just need

[jira] [Updated] (CASSANDRA-6102) CassandraStorage broken for bigints and ints

[ https://issues.apache.org/jira/browse/CASSANDRA-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Liu updated CASSANDRA-6102: Attachment: 6102-1.2-branch.txt CassandraStorage broken for bigints and ints

[jira] [Updated] (CASSANDRA-6102) CassandraStorage broken for bigints and ints

[ https://issues.apache.org/jira/browse/CASSANDRA-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Liu updated CASSANDRA-6102: Reviewer: brandon.williams CassandraStorage broken for bigints and ints

[1/2] git commit: remove deprecation

Updated Branches: refs/heads/trunk bb8e95c2b - a1be1a913 remove deprecation Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/ee553f32 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/ee553f32 Diff:

git commit: remove deprecation

Updated Branches: refs/heads/cassandra-2.0 ed7b08b39 - ee553f32d remove deprecation Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/ee553f32 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/ee553f32

[2/2] git commit: Merge branch 'cassandra-2.0' into trunk

Merge branch 'cassandra-2.0' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/a1be1a91 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/a1be1a91 Diff:

[jira] [Commented] (CASSANDRA-6102) CassandraStorage broken for bigints and ints

[ https://issues.apache.org/jira/browse/CASSANDRA-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780708#comment-13780708 ] Janne Jalkanen commented on CASSANDRA-6102: --- What is the patch against?

[jira] [Updated] (CASSANDRA-6102) CassandraStorage broken for bigints and ints

[ https://issues.apache.org/jira/browse/CASSANDRA-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Liu updated CASSANDRA-6102: Attachment: 6102-1.2-branch.txt CassandraStorage broken for bigints and ints

[jira] [Updated] (CASSANDRA-6102) CassandraStorage broken for bigints and ints

[ https://issues.apache.org/jira/browse/CASSANDRA-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Liu updated CASSANDRA-6102: Attachment: (was: 6102-1.2-branch.txt) CassandraStorage broken for bigints and ints

  1   2   >