[jira] [Commented] (CASSANDRA-12676) Message coalescing regression

[ https://issues.apache.org/jira/browse/CASSANDRA-12676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129162#comment-16129162 ] Mike Bulman commented on CASSANDRA-12676: - Thoughts on removing 3.0.12 from Fix Version, to

[jira] [Commented] (CASSANDRA-9195) commitlog replay only actually replays mutation every other time

[ https://issues.apache.org/jira/browse/CASSANDRA-9195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14509289#comment-14509289 ] Mike Bulman commented on CASSANDRA-9195: bq. It could be replaced with drop

[jira] [Commented] (CASSANDRA-9179) Unable to point in time restore if table/cf has been recreated

[ https://issues.apache.org/jira/browse/CASSANDRA-9179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494442#comment-14494442 ] Mike Bulman commented on CASSANDRA-9179: Given this only affects DROP, I'll

[jira] [Comment Edited] (CASSANDRA-9179) Unable to point in time restore if table/cf has been recreated

[ https://issues.apache.org/jira/browse/CASSANDRA-9179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494255#comment-14494255 ] Mike Bulman edited comment on CASSANDRA-9179 at 4/14/15 5:22 PM:

[jira] [Commented] (CASSANDRA-9179) Unable to point in time restore if table/cf has been recreated

[ https://issues.apache.org/jira/browse/CASSANDRA-9179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494255#comment-14494255 ] Mike Bulman commented on CASSANDRA-9179: Two things to add: * This also

[jira] [Commented] (CASSANDRA-9179) Unable to point in time restore if table/cf has been recreated

[ https://issues.apache.org/jira/browse/CASSANDRA-9179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494283#comment-14494283 ] Mike Bulman commented on CASSANDRA-9179: Is it possible to manually change the

[jira] [Commented] (CASSANDRA-8734) Expose commit log archive status

[ https://issues.apache.org/jira/browse/CASSANDRA-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14318952#comment-14318952 ] Mike Bulman commented on CASSANDRA-8734: Can we backport this to 2.0.x as

[jira] [Commented] (CASSANDRA-8076) Expose an mbean method to poll for repair job status

[ https://issues.apache.org/jira/browse/CASSANDRA-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173276#comment-14173276 ] Mike Bulman commented on CASSANDRA-8076: I think that would work just fine.

[jira] [Commented] (CASSANDRA-8076) Expose an mbean method to poll for repair job status

[ https://issues.apache.org/jira/browse/CASSANDRA-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163296#comment-14163296 ] Mike Bulman commented on CASSANDRA-8076: This ticket is meant to stop the

[jira] [Comment Edited] (CASSANDRA-8076) Expose an mbean method to poll for repair job status

[ https://issues.apache.org/jira/browse/CASSANDRA-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14163296#comment-14163296 ] Mike Bulman edited comment on CASSANDRA-8076 at 10/8/14 10:20 AM:

[jira] [Commented] (CASSANDRA-4809) Allow restoring specific column families from archived commitlog

[ https://issues.apache.org/jira/browse/CASSANDRA-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13788157#comment-13788157 ] Mike Bulman commented on CASSANDRA-4809: Fwiw, it would be great if multiple

[jira] [Commented] (CASSANDRA-4809) Allow restoring specific column families from archived commitlog

[ https://issues.apache.org/jira/browse/CASSANDRA-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13788210#comment-13788210 ] Mike Bulman commented on CASSANDRA-4809: bq. and this does occur before thrift

[jira] [Commented] (CASSANDRA-5555) Allow sstableloader to handle a larger number of files

[ https://issues.apache.org/jira/browse/CASSANDRA-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679863#comment-13679863 ] Mike Bulman commented on CASSANDRA-: bq. We already committed a fix for

[jira] [Created] (CASSANDRA-5567) DESCRIBE TABLES is empty after case insensitive use

Mike Bulman created CASSANDRA-5567: -- Summary: DESCRIBE TABLES is empty after case insensitive use Key: CASSANDRA-5567 URL: https://issues.apache.org/jira/browse/CASSANDRA-5567 Project: Cassandra

[jira] [Commented] (CASSANDRA-4482) In-memory merkle trees for repair

[ https://issues.apache.org/jira/browse/CASSANDRA-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427489#comment-13427489 ] Mike Bulman commented on CASSANDRA-4482: fwiw, continuous repair is on the

[jira] [Created] (CASSANDRA-4276) Multiple SLF4J bindings warning when running stress

Mike Bulman created CASSANDRA-4276: -- Summary: Multiple SLF4J bindings warning when running stress Key: CASSANDRA-4276 URL: https://issues.apache.org/jira/browse/CASSANDRA-4276 Project: Cassandra

[jira] [Commented] (CASSANDRA-4267) cassandra-stress.bat can't find o.a.c.stress.Stress

[ https://issues.apache.org/jira/browse/CASSANDRA-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13281971#comment-13281971 ] Mike Bulman commented on CASSANDRA-4267: As long as you ignore the multiple

[jira] [Created] (CASSANDRA-4267) cassandra-stress.bat can't find o.a.c.stress.Stress

Mike Bulman created CASSANDRA-4267: -- Summary: cassandra-stress.bat can't find o.a.c.stress.Stress Key: CASSANDRA-4267 URL: https://issues.apache.org/jira/browse/CASSANDRA-4267 Project: Cassandra

[jira] [Updated] (CASSANDRA-4267) cassandra-stress.bat can't find o.a.c.stress.Stress

[ https://issues.apache.org/jira/browse/CASSANDRA-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Bulman updated CASSANDRA-4267: --- Reviewer: jbellis cassandra-stress.bat can't find o.a.c.stress.Stress

[jira] [Updated] (CASSANDRA-4267) cassandra-stress.bat can't find o.a.c.stress.Stress

[ https://issues.apache.org/jira/browse/CASSANDRA-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Bulman updated CASSANDRA-4267: --- Attachment: 0001-CASSANDRA-4267.patch Added patch that explicitly references stress.jar.

[jira] [Updated] (CASSANDRA-4267) cassandra-stress.bat can't find o.a.c.stress.Stress

[ https://issues.apache.org/jira/browse/CASSANDRA-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Bulman updated CASSANDRA-4267: --- Attachment: 0001-CASSANDRA-4267-V2.patch New patch that puts you back in the directory

[jira] [Updated] (CASSANDRA-2770) Expose data_dir though jmx

[ https://issues.apache.org/jira/browse/CASSANDRA-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Bulman updated CASSANDRA-2770: --- Attachment: CASSANDRA-2770-1-trunk.txt I couldn't assign this to myself, but here's a

[jira] [Updated] (CASSANDRA-2770) Expose data_dir though jmx

[ https://issues.apache.org/jira/browse/CASSANDRA-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Bulman updated CASSANDRA-2770: --- Assignee: Mike Bulman Expose data_dir though jmx --

[jira] [Created] (CASSANDRA-2770) Expose cassandra.yaml location though jmx

Expose cassandra.yaml location though jmx - Key: CASSANDRA-2770 URL: https://issues.apache.org/jira/browse/CASSANDRA-2770 Project: Cassandra Issue Type: New Feature Reporter: Mike Bulman

[jira] [Updated] (CASSANDRA-2770) Expose data_dir though jmx

[ https://issues.apache.org/jira/browse/CASSANDRA-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Bulman updated CASSANDRA-2770: --- Summary: Expose data_dir though jmx (was: Expose cassandra.yaml location though jmx)

[jira] [Created] (CASSANDRA-2571) Invalid super cf incr command puts c* in bad state

Invalid super cf incr command puts c* in bad state -- Key: CASSANDRA-2571 URL: https://issues.apache.org/jira/browse/CASSANDRA-2571 Project: Cassandra Issue Type: Bug Affects Versions: 0.8

[jira] [Commented] (CASSANDRA-2536) Schema disagreements when using connections to multiple hosts

[ https://issues.apache.org/jira/browse/CASSANDRA-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13022978#comment-13022978 ] Mike Bulman commented on CASSANDRA-2536: I feel like a better, more critical

[jira] Commented: (CASSANDRA-2177) OPP + NTS + RF=2 reports wrong getRangeToEndpointMap

[ https://issues.apache.org/jira/browse/CASSANDRA-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12996627#comment-12996627 ] Mike Bulman commented on CASSANDRA-2177: So I'm not sure what happened here

[jira] Created: (CASSANDRA-2177) OPP + NTS + RF=2 reports wrong getRangeToEndpointMap

OPP + NTS + RF=2 reports wrong getRangeToEndpointMap Key: CASSANDRA-2177 URL: https://issues.apache.org/jira/browse/CASSANDRA-2177 Project: Cassandra Issue Type: Bug Reporter:

[jira] Commented: (CASSANDRA-2129) removetoken after removetoken rf error fails to work

[ https://issues.apache.org/jira/browse/CASSANDRA-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12992029#comment-12992029 ] Mike Bulman commented on CASSANDRA-2129: No. force and status both report no

[jira] Created: (CASSANDRA-2129) removetoken after removetoken rf error fails to work

removetoken after removetoken rf error fails to work Key: CASSANDRA-2129 URL: https://issues.apache.org/jira/browse/CASSANDRA-2129 Project: Cassandra Issue Type: Bug Affects Versions:

[jira] Commented: (CASSANDRA-1738) Decommission fails after original bootstrap

[ https://issues.apache.org/jira/browse/CASSANDRA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12931681#action_12931681 ] Mike Bulman commented on CASSANDRA-1738: autobootstrap=true for node1 + 2

[jira] Created: (CASSANDRA-1738) Decommission fails after original bootstrap

Decommission fails after original bootstrap --- Key: CASSANDRA-1738 URL: https://issues.apache.org/jira/browse/CASSANDRA-1738 Project: Cassandra Issue Type: Bug Affects Versions: 0.7 beta 3

[jira] Commented: (CASSANDRA-1670) cannot move a node

[ https://issues.apache.org/jira/browse/CASSANDRA-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12927463#action_12927463 ] Mike Bulman commented on CASSANDRA-1670: That's all I get. The only other

[jira] Commented: (CASSANDRA-1670) cannot move a node

[ https://issues.apache.org/jira/browse/CASSANDRA-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12927484#action_12927484 ] Mike Bulman commented on CASSANDRA-1670: INFO 15:48:22,176 Joining: getting

[jira] Commented: (CASSANDRA-1670) cannot move a node

[ https://issues.apache.org/jira/browse/CASSANDRA-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12927652#action_12927652 ] Mike Bulman commented on CASSANDRA-1670: Ok got it working properly. Patch

[jira] Commented: (CASSANDRA-1691) Repair blocking forever when RF=1

[ https://issues.apache.org/jira/browse/CASSANDRA-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12927167#action_12927167 ] Mike Bulman commented on CASSANDRA-1691: It definitely does _something_ for

[jira] Commented: (CASSANDRA-1670) cannot decom a node then bring it back to the cluster

[ https://issues.apache.org/jira/browse/CASSANDRA-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12926469#action_12926469 ] Mike Bulman commented on CASSANDRA-1670: Because move is