[jira] [Updated] (CASSANDRA-6688) Avoid possible sstable overlaps with leveled compaction

[ https://issues.apache.org/jira/browse/CASSANDRA-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-6688: --- Attachment: 6688-v3.patch v3 attached that removes skipLevels > Avoid possible s

[jira] [Updated] (CASSANDRA-6688) Avoid possible sstable overlaps with leveled compaction

[ https://issues.apache.org/jira/browse/CASSANDRA-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-6688: --- Since Version: 2.0 beta 1 Fix Version/s: 2.0.6 1.2 is not affected since it r

[jira] [Commented] (CASSANDRA-6683) BADNESS_THRESHOLD does not working correctly with DynamicEndpointSnitch

[ https://issues.apache.org/jira/browse/CASSANDRA-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898928#comment-13898928 ] Kirill Bogdanov commented on CASSANDRA-6683: Thank you for your answer. I

[jira] [Updated] (CASSANDRA-4911) Lift limitation that order by columns must be selected for IN queries

[ https://issues.apache.org/jira/browse/CASSANDRA-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-4911: Attachment: 4911-v2.txt Ok, the logic in that first patch was a bit confused. A

[jira] [Commented] (CASSANDRA-6561) Static columns in CQL3

[ https://issues.apache.org/jira/browse/CASSANDRA-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898963#comment-13898963 ] Sylvain Lebresne commented on CASSANDRA-6561: - bq. ALTER TABLE ADD should

[jira] [Created] (CASSANDRA-6691) Improvements and FIxes to Stress

Benedict created CASSANDRA-6691: --- Summary: Improvements and FIxes to Stress Key: CASSANDRA-6691 URL: https://issues.apache.org/jira/browse/CASSANDRA-6691 Project: Cassandra Issue Type: Bug

[jira] [Created] (CASSANDRA-6692) AtomicBTreeColumns Improvements

Benedict created CASSANDRA-6692: --- Summary: AtomicBTreeColumns Improvements Key: CASSANDRA-6692 URL: https://issues.apache.org/jira/browse/CASSANDRA-6692 Project: Cassandra Issue Type: Improveme

[jira] [Commented] (CASSANDRA-6689) Partially Off Heap Memtables

[ https://issues.apache.org/jira/browse/CASSANDRA-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899081#comment-13899081 ] Marcus Eriksson commented on CASSANDRA-6689: [~jasobrown] [~xedin] I would

[jira] [Commented] (CASSANDRA-6689) Partially Off Heap Memtables

[ https://issues.apache.org/jira/browse/CASSANDRA-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899096#comment-13899096 ] Benedict commented on CASSANDRA-6689: - There are some natural boundaries if you wa

[jira] [Created] (CASSANDRA-6693) cqlsh fails to insert row with huge blob

Aleksander Stasiak created CASSANDRA-6693: - Summary: cqlsh fails to insert row with huge blob Key: CASSANDRA-6693 URL: https://issues.apache.org/jira/browse/CASSANDRA-6693 Project: Cassandra

[jira] [Commented] (CASSANDRA-6683) BADNESS_THRESHOLD does not working correctly with DynamicEndpointSnitch

[ https://issues.apache.org/jira/browse/CASSANDRA-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899130#comment-13899130 ] Brandon Williams commented on CASSANDRA-6683: - You could test by disabling

[jira] [Comment Edited] (CASSANDRA-6683) BADNESS_THRESHOLD does not working correctly with DynamicEndpointSnitch

[ https://issues.apache.org/jira/browse/CASSANDRA-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899130#comment-13899130 ] Brandon Williams edited comment on CASSANDRA-6683 at 2/12/14 2:12 PM: --

[jira] [Resolved] (CASSANDRA-6693) cqlsh fails to insert row with huge blob

[ https://issues.apache.org/jira/browse/CASSANDRA-6693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams resolved CASSANDRA-6693. - Resolution: Invalid You're probably exceeding your thrift_framed_transport_si

[jira] [Created] (CASSANDRA-6694) Slightly More Off-Heap Memtables

Benedict created CASSANDRA-6694: --- Summary: Slightly More Off-Heap Memtables Key: CASSANDRA-6694 URL: https://issues.apache.org/jira/browse/CASSANDRA-6694 Project: Cassandra Issue Type: Improvem

[jira] [Created] (CASSANDRA-6695) Cassandra should not push schema updates to nodes with unknown version

Piotr Kołaczkowski created CASSANDRA-6695: - Summary: Cassandra should not push schema updates to nodes with unknown version Key: CASSANDRA-6695 URL: https://issues.apache.org/jira/browse/CASSANDRA-6695

[jira] [Updated] (CASSANDRA-6695) Cassandra should not push schema updates to nodes with unknown version

[ https://issues.apache.org/jira/browse/CASSANDRA-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Kołaczkowski updated CASSANDRA-6695: -- Description: MigrationManager#announce() must not send schema to nodes it d

[jira] [Updated] (CASSANDRA-6695) Cassandra should not push schema updates to nodes with unknown version

[ https://issues.apache.org/jira/browse/CASSANDRA-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Kołaczkowski updated CASSANDRA-6695: -- Attachment: CASSANDRA-6695-2.0.patch > Cassandra should not push schema upd

[jira] [Updated] (CASSANDRA-6695) Cassandra should not push schema updates to nodes with unknown version

[ https://issues.apache.org/jira/browse/CASSANDRA-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Kołaczkowski updated CASSANDRA-6695: -- Attachment: 6695.patch > Cassandra should not push schema updates to nodes

[jira] [Updated] (CASSANDRA-6695) Cassandra should not push schema updates to nodes with unknown version

[ https://issues.apache.org/jira/browse/CASSANDRA-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Kołaczkowski updated CASSANDRA-6695: -- Attachment: (was: CASSANDRA-6695-2.0.patch) > Cassandra should not push

[jira] [Updated] (CASSANDRA-6695) Cassandra should not push schema updates to nodes with unknown version

[ https://issues.apache.org/jira/browse/CASSANDRA-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-6695: -- Reviewer: Aleksey Yeschenko > Cassandra should not push schema updates to nodes wit

[jira] [Commented] (CASSANDRA-6688) Avoid possible sstable overlaps with leveled compaction

[ https://issues.apache.org/jira/browse/CASSANDRA-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899212#comment-13899212 ] Jonathan Ellis commented on CASSANDRA-6688: --- +1 > Avoid possible sstable ov

[jira] [Updated] (CASSANDRA-6596) Split out outgoing stream throughput within a DC and inter-DC

[ https://issues.apache.org/jira/browse/CASSANDRA-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-6596: -- Reviewer: Benedict > Split out outgoing stream throughput within a DC and inter-DC

[jira] [Commented] (CASSANDRA-6596) Split out outgoing stream throughput within a DC and inter-DC

[ https://issues.apache.org/jira/browse/CASSANDRA-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899215#comment-13899215 ] Jonathan Ellis commented on CASSANDRA-6596: --- Adding [~benedict] as reviewer

[jira] [Updated] (CASSANDRA-6575) By default, Cassandra should refuse to start if JNA can't be initialized properly

[ https://issues.apache.org/jira/browse/CASSANDRA-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-6575: -- Reviewer: Joshua McKenzie (was: Dave Brosius) > By default, Cassandra should refus

[jira] [Created] (CASSANDRA-6696) Drive replacement in JBOD can cause data to reappear.

sankalp kohli created CASSANDRA-6696: Summary: Drive replacement in JBOD can cause data to reappear. Key: CASSANDRA-6696 URL: https://issues.apache.org/jira/browse/CASSANDRA-6696 Project: Cassandr

[jira] [Updated] (CASSANDRA-6695) Cassandra should not push schema updates to nodes with unknown version

[ https://issues.apache.org/jira/browse/CASSANDRA-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-6695: - Attachment: 6695-v2.txt > Cassandra should not push schema updates to nodes w

[jira] [Updated] (CASSANDRA-6695) Don't exchange schema between nodes with different versions (no pull, no push)

[ https://issues.apache.org/jira/browse/CASSANDRA-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-6695: - Reproduced In: (was: 2.0.5) Description: Subject. Don't push schema t

[jira] [Commented] (CASSANDRA-6695) Don't exchange schema between nodes with different versions (no pull, no push)

[ https://issues.apache.org/jira/browse/CASSANDRA-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899243#comment-13899243 ] Piotr Kołaczkowski commented on CASSANDRA-6695: --- LGTM :) > Don't exchan

[jira] [Updated] (CASSANDRA-6695) Don't exchange schema between nodes with different versions (no pull, no push)

[ https://issues.apache.org/jira/browse/CASSANDRA-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-6695: - Reviewer: Piotr Kołaczkowski (was: Aleksey Yeschenko) > Don't exchange schem

[jira] [Comment Edited] (CASSANDRA-6695) Don't exchange schema between nodes with different versions (no pull, no push)

[ https://issues.apache.org/jira/browse/CASSANDRA-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899243#comment-13899243 ] Piotr Kołaczkowski edited comment on CASSANDRA-6695 at 2/12/14 4:34 PM:

git commit: Don't exchange schema between nodes with different versions

Updated Branches: refs/heads/cassandra-1.2 00a8b1e6e -> b2dfaed31 Don't exchange schema between nodes with different versions patch by Aleksey Yeschenko; reviewed by Piotr Kołaczkowski for CASSANDRA-6695 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-u

[jira] [Commented] (CASSANDRA-6596) Split out outgoing stream throughput within a DC and inter-DC

[ https://issues.apache.org/jira/browse/CASSANDRA-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899256#comment-13899256 ] Benedict commented on CASSANDRA-6596: - Mostly LGTM. A couple of sort-of-nits: 1)

[1/2] git commit: Don't exchange schema between nodes with different versions

Updated Branches: refs/heads/cassandra-2.0 80cebec5d -> babc2de3e Don't exchange schema between nodes with different versions patch by Aleksey Yeschenko; reviewed by Piotr Kołaczkowski for CASSANDRA-6695 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-u

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

Merge branch 'cassandra-1.2' into cassandra-2.0 Conflicts: src/java/org/apache/cassandra/service/MigrationManager.java Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/babc2de3 Tree: http://git-wip-us.apache.or

[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/f5b3515e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/f5b3515e Diff: http://git-wip-us.apache.org/repos/asf/cassand

[1/3] git commit: Don't exchange schema between nodes with different versions

Updated Branches: refs/heads/trunk 5cf381f57 -> f5b3515ee Don't exchange schema between nodes with different versions patch by Aleksey Yeschenko; reviewed by Piotr Kołaczkowski for CASSANDRA-6695 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache

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

Merge branch 'cassandra-1.2' into cassandra-2.0 Conflicts: src/java/org/apache/cassandra/service/MigrationManager.java Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/babc2de3 Tree: http://git-wip-us.apache.or

[jira] [Commented] (CASSANDRA-6691) Improvements and FIxes to Stress

[ https://issues.apache.org/jira/browse/CASSANDRA-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899274#comment-13899274 ] Jonathan Ellis commented on CASSANDRA-6691: --- Can you review [~xedin]? > Imp

[jira] [Updated] (CASSANDRA-6691) Improvements and FIxes to Stress

[ https://issues.apache.org/jira/browse/CASSANDRA-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-6691: -- Reviewer: Pavel Yaskevich > Improvements and FIxes to Stress >

[jira] [Commented] (CASSANDRA-5483) Repair tracing

[ https://issues.apache.org/jira/browse/CASSANDRA-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899275#comment-13899275 ] Jonathan Ellis commented on CASSANDRA-5483: --- Can you review, Lyuben? > Repa

[jira] [Commented] (CASSANDRA-6683) BADNESS_THRESHOLD does not working correctly with DynamicEndpointSnitch

[ https://issues.apache.org/jira/browse/CASSANDRA-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899277#comment-13899277 ] Tyler Hobbs commented on CASSANDRA-6683: [~brandon.williams] was our motivatio

[jira] [Updated] (CASSANDRA-5483) Repair tracing

[ https://issues.apache.org/jira/browse/CASSANDRA-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5483: -- Reviewer: Lyuben Todorov (was: Yuki Morishita) > Repair tracing > -- >

[jira] [Commented] (CASSANDRA-6683) BADNESS_THRESHOLD does not working correctly with DynamicEndpointSnitch

[ https://issues.apache.org/jira/browse/CASSANDRA-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899295#comment-13899295 ] Brandon Williams commented on CASSANDRA-6683: - bq. was our motivation for

[jira] [Commented] (CASSANDRA-6696) Drive replacement in JBOD can cause data to reappear.

[ https://issues.apache.org/jira/browse/CASSANDRA-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899297#comment-13899297 ] sankalp kohli commented on CASSANDRA-6696: -- With this, the whole disk_failure

git commit: Fix stress

Updated Branches: refs/heads/trunk f5b3515ee -> 0d0acac6c Fix stress Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/0d0acac6 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/0d0acac6 Diff: http://git-wi

[jira] [Commented] (CASSANDRA-6631) cassandra-stress failing in trunk

[ https://issues.apache.org/jira/browse/CASSANDRA-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899309#comment-13899309 ] Sylvain Lebresne commented on CASSANDRA-6631: - Committed [a fix|https://g

[jira] [Commented] (CASSANDRA-6631) cassandra-stress failing in trunk

[ https://issues.apache.org/jira/browse/CASSANDRA-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899314#comment-13899314 ] Michael Shuler commented on CASSANDRA-6631: --- +1 Thanks a bunch! > cassandra

[jira] [Commented] (CASSANDRA-6631) cassandra-stress failing in trunk

[ https://issues.apache.org/jira/browse/CASSANDRA-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899323#comment-13899323 ] Michael Shuler commented on CASSANDRA-6631: --- hmm.. write worked, read throws

[jira] [Commented] (CASSANDRA-6663) Connecting to a Raspberry PI Cassandra Cluster crashes the node being connected to

[ https://issues.apache.org/jira/browse/CASSANDRA-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899326#comment-13899326 ] Tyler Hobbs commented on CASSANDRA-6663: Alright, the python driver now avoids

[jira] [Commented] (CASSANDRA-6631) cassandra-stress failing in trunk

[ https://issues.apache.org/jira/browse/CASSANDRA-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899334#comment-13899334 ] Benedict commented on CASSANDRA-6631: - I've improved the error messages with CASSA

[jira] [Commented] (CASSANDRA-4867) Add verbose option to cqlsh when using file input

[ https://issues.apache.org/jira/browse/CASSANDRA-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899335#comment-13899335 ] Cyril Scetbon commented on CASSANDRA-4867: -- Is there any information about th

[jira] [Resolved] (CASSANDRA-6663) Connecting to a Raspberry PI Cassandra Cluster crashes the node being connected to

[ https://issues.apache.org/jira/browse/CASSANDRA-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams resolved CASSANDRA-6663. - Resolution: Invalid > Connecting to a Raspberry PI Cassandra Cluster crashes

[jira] [Commented] (CASSANDRA-6631) cassandra-stress failing in trunk

[ https://issues.apache.org/jira/browse/CASSANDRA-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899336#comment-13899336 ] Michael Shuler commented on CASSANDRA-6631: --- I'm running again until complet

[jira] [Commented] (CASSANDRA-6631) cassandra-stress failing in trunk

[ https://issues.apache.org/jira/browse/CASSANDRA-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899343#comment-13899343 ] Michael Shuler commented on CASSANDRA-6631: --- +2 ;) Working fine with a litt

[jira] [Resolved] (CASSANDRA-6631) cassandra-stress failing in trunk

[ https://issues.apache.org/jira/browse/CASSANDRA-6631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne resolved CASSANDRA-6631. - Resolution: Fixed Let's close that then > cassandra-stress failing in trunk

[jira] [Commented] (CASSANDRA-6683) BADNESS_THRESHOLD does not working correctly with DynamicEndpointSnitch

[ https://issues.apache.org/jira/browse/CASSANDRA-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899375#comment-13899375 ] Tyler Hobbs commented on CASSANDRA-6683: bq. I'm not sure what you mean exactl

[jira] [Commented] (CASSANDRA-6683) BADNESS_THRESHOLD does not working correctly with DynamicEndpointSnitch

[ https://issues.apache.org/jira/browse/CASSANDRA-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899388#comment-13899388 ] Brandon Williams commented on CASSANDRA-6683: - I see what you meant. Yeah

[jira] [Commented] (CASSANDRA-6696) Drive replacement in JBOD can cause data to reappear.

[ https://issues.apache.org/jira/browse/CASSANDRA-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899398#comment-13899398 ] Benedict commented on CASSANDRA-6696: - One possibility here is that we could split

[jira] [Commented] (CASSANDRA-6696) Drive replacement in JBOD can cause data to reappear.

[ https://issues.apache.org/jira/browse/CASSANDRA-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899425#comment-13899425 ] Jonathan Ellis commented on CASSANDRA-6696: --- bq. the whole disk_failure_poli

[jira] [Updated] (CASSANDRA-6696) Drive replacement in JBOD can cause data to reappear.

[ https://issues.apache.org/jira/browse/CASSANDRA-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-6696: -- Issue Type: Improvement (was: Bug) (Classifying this an Improvement since while th

[jira] [Updated] (CASSANDRA-6696) Drive replacement in JBOD can cause data to reappear.

[ https://issues.apache.org/jira/browse/CASSANDRA-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-6696: -- Component/s: Core Priority: Major (was: Minor) Fix Version/s: 3.0 >

[jira] [Updated] (CASSANDRA-5962) Support trigger parametrization

[ https://issues.apache.org/jira/browse/CASSANDRA-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-5962: - Labels: (╯°□°)╯︵┻━┻ cql3 triggers (was: cql3 triggers) > Support trigger par

[jira] [Commented] (CASSANDRA-4911) Lift limitation that order by columns must be selected for IN queries

[ https://issues.apache.org/jira/browse/CASSANDRA-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899508#comment-13899508 ] Tyler Hobbs commented on CASSANDRA-4911: Thanks for adding the dtest. If I ch

[jira] [Commented] (CASSANDRA-6696) Drive replacement in JBOD can cause data to reappear.

[ https://issues.apache.org/jira/browse/CASSANDRA-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899519#comment-13899519 ] Benedict commented on CASSANDRA-6696: - bq. if you lose "data" then you scrub/repai

[jira] [Comment Edited] (CASSANDRA-6696) Drive replacement in JBOD can cause data to reappear.

[ https://issues.apache.org/jira/browse/CASSANDRA-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899519#comment-13899519 ] Benedict edited comment on CASSANDRA-6696 at 2/12/14 8:04 PM: --

[jira] [Commented] (CASSANDRA-6697) Refactor Cell and CellName ByteBuffer accessors to avoid garbage allocation where possible

[ https://issues.apache.org/jira/browse/CASSANDRA-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899559#comment-13899559 ] Benedict commented on CASSANDRA-6697: - I've uploaded a preliminary patch [here|ht

[jira] [Created] (CASSANDRA-6697) Refactor Cell and CellName ByteBuffer accessors to avoid garbage allocation where possible

Benedict created CASSANDRA-6697: --- Summary: Refactor Cell and CellName ByteBuffer accessors to avoid garbage allocation where possible Key: CASSANDRA-6697 URL: https://issues.apache.org/jira/browse/CASSANDRA-6697

[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/1ede2967 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/1ede2967 Diff: http://git-wip-us.apache.org/repos/asf/cassand

[1/3] git commit: log at info when gossip is fine or people think it's still waiting

Updated Branches: refs/heads/cassandra-2.0 babc2de3e -> cafaa8eea refs/heads/trunk 0d0acac6c -> 1ede2967b log at info when gossip is fine or people think it's still waiting Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandr

[2/3] git commit: log at info when gossip is fine or people think it's still waiting

log at info when gossip is fine or people think it's still waiting Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/cafaa8ee Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/cafaa8ee Diff: http://git-wip-us.a

[1/3] git commit: SS logging 'now serving reads' is misleading

Updated Branches: refs/heads/cassandra-2.0 cafaa8eea -> efec07e11 refs/heads/trunk 1ede2967b -> f78db5307 SS logging 'now serving reads' is misleading Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/efec07e1 Tree

[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/f78db530 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/f78db530 Diff: http://git-wip-us.apache.org/repos/asf/cassand

[2/3] git commit: SS logging 'now serving reads' is misleading

SS logging 'now serving reads' is misleading Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/efec07e1 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/efec07e1 Diff: http://git-wip-us.apache.org/repos/asf/ca

[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/d4461f83 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/d4461f83 Diff: http://git-wip-us.apache.org/repos/asf/cassand

[2/3] git commit: only waitForGossip if we're configured for a multinode cluster

only waitForGossip if we're configured for a multinode cluster Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/c6c686f4 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/c6c686f4 Diff: http://git-wip-us.apach

[1/3] git commit: only waitForGossip if we're configured for a multinode cluster

Updated Branches: refs/heads/cassandra-2.0 efec07e11 -> c6c686f41 refs/heads/trunk f78db5307 -> d4461f832 only waitForGossip if we're configured for a multinode cluster Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/co

[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/15d60756 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/15d60756 Diff: http://git-wip-us.apache.org/repos/asf/cassand

[2/3] git commit: turns out there's already a getLoopbackAddress

turns out there's already a getLoopbackAddress Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/de6a74a2 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/de6a74a2 Diff: http://git-wip-us.apache.org/repos/asf/

[1/3] git commit: turns out there's already a getLoopbackAddress

Updated Branches: refs/heads/cassandra-2.0 c6c686f41 -> de6a74a2d refs/heads/trunk d4461f832 -> 15d607568 turns out there's already a getLoopbackAddress Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/de6a74a2 Tr

[jira] [Updated] (CASSANDRA-6698) Many too small SSTables when full repair

[ https://issues.apache.org/jira/browse/CASSANDRA-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Skvazh updated CASSANDRA-6698: Reproduced In: 2.0.5, 2.0.4 (was: 2.0.5) > Many too small SSTables when full repair >

[jira] [Created] (CASSANDRA-6698) Many too small SSTables when full repair

Roman Skvazh created CASSANDRA-6698: --- Summary: Many too small SSTables when full repair Key: CASSANDRA-6698 URL: https://issues.apache.org/jira/browse/CASSANDRA-6698 Project: Cassandra Issu

[jira] [Comment Edited] (CASSANDRA-6698) Many too small SSTables when full repair

[ https://issues.apache.org/jira/browse/CASSANDRA-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899737#comment-13899737 ] Roman Skvazh edited comment on CASSANDRA-6698 at 2/12/14 11:11 PM: -

[jira] [Updated] (CASSANDRA-6698) Many too small SSTables when full repair

[ https://issues.apache.org/jira/browse/CASSANDRA-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Skvazh updated CASSANDRA-6698: Attachment: cassa-many-small-sstables.txt Some of files > Many too small SSTables when

[jira] [Updated] (CASSANDRA-6698) Many too small SSTables when full repair

[ https://issues.apache.org/jira/browse/CASSANDRA-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Skvazh updated CASSANDRA-6698: Description: We are have troubles when cassandra drops messages because there is too ma

[jira] [Updated] (CASSANDRA-6698) Many too small SSTables when full repair

[ https://issues.apache.org/jira/browse/CASSANDRA-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Skvazh updated CASSANDRA-6698: Description: We are have troubles when cassandra drops messages because there is too ma

[jira] [Updated] (CASSANDRA-6698) Many too small SSTables when full repair

[ https://issues.apache.org/jira/browse/CASSANDRA-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Skvazh updated CASSANDRA-6698: Description: We are have troubles when cassandra drops messages because there is too ma

[jira] [Updated] (CASSANDRA-6698) Many too small SSTables when full repair

[ https://issues.apache.org/jira/browse/CASSANDRA-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-6698: -- Reproduced In: 2.0.5, 2.0.4 (was: 2.0.4, 2.0.5) Priority: Minor (was: Cri

[jira] [Updated] (CASSANDRA-6698) Many too small SSTables when full repair

[ https://issues.apache.org/jira/browse/CASSANDRA-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Skvazh updated CASSANDRA-6698: Description: We have troubles when cassandra drops messages because there is too many (

[jira] [Commented] (CASSANDRA-6698) Many too small SSTables when full repair

[ https://issues.apache.org/jira/browse/CASSANDRA-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899747#comment-13899747 ] Jonathan Ellis commented on CASSANDRA-6698: --- Can you elaborate as to why CAS

[jira] [Commented] (CASSANDRA-6698) Many too small SSTables when full repair

[ https://issues.apache.org/jira/browse/CASSANDRA-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899769#comment-13899769 ] Roman Skvazh commented on CASSANDRA-6698: - We can not use STCS because we have

[jira] [Updated] (CASSANDRA-6379) Replace index_interval with min/max_index_interval

[ https://issues.apache.org/jira/browse/CASSANDRA-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Hobbs updated CASSANDRA-6379: --- Reviewer: Aleksey Yeschenko > Replace index_interval with min/max_index_interval > --

git commit: Remove dead ColumnSlice.NavigatableMapIterator

Updated Branches: refs/heads/trunk 15d607568 -> f66b9eb27 Remove dead ColumnSlice.NavigatableMapIterator Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/f66b9eb2 Tree: http://git-wip-us.apache.org/repos/asf/cassand

[jira] [Updated] (CASSANDRA-6697) Refactor Cell and CellName ByteBuffer accessors to avoid garbage allocation where possible

[ https://issues.apache.org/jira/browse/CASSANDRA-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-6697: Description: This is a prerequisite for CASSANDRA-6689. The basic idea is to, if unsafe is ava

[jira] [Updated] (CASSANDRA-6697) Refactor Cell and CellName ByteBuffer accessors to avoid garbage allocation where possible

[ https://issues.apache.org/jira/browse/CASSANDRA-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-6697: Description: This is a prerequisite for CASSANDRA-6691. The basic idea is to, if unsafe is ava

[jira] [Commented] (CASSANDRA-6697) Refactor Cell and CellName ByteBuffer accessors to avoid garbage allocation where possible

[ https://issues.apache.org/jira/browse/CASSANDRA-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899835#comment-13899835 ] Benedict commented on CASSANDRA-6697: - Updated the repository with a different app

[jira] [Updated] (CASSANDRA-6379) Replace index_interval with min/max_index_interval

[ https://issues.apache.org/jira/browse/CASSANDRA-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Hobbs updated CASSANDRA-6379: --- Attachment: 6379-thrift-gen.txt 6379.txt 6379.txt (and [branch|https://gi

[jira] [Comment Edited] (CASSANDRA-6379) Replace index_interval with min/max_index_interval

[ https://issues.apache.org/jira/browse/CASSANDRA-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899839#comment-13899839 ] Tyler Hobbs edited comment on CASSANDRA-6379 at 2/13/14 12:39 AM: --

git commit: Improvements and fixes to cassandra/stress Patch by Benedict; reviewed by Pavel Yaskevich for CASSANDRA-6691

Updated Branches: refs/heads/trunk f66b9eb27 -> 10b617364 Improvements and fixes to cassandra/stress Patch by Benedict; reviewed by Pavel Yaskevich for CASSANDRA-6691 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit

git commit: remove dead code

Updated Branches: refs/heads/cassandra-2.0 de6a74a2d -> 5f60fcc39 remove dead code Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/5f60fcc3 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/5f60fcc3 Diff:

[1/2] git commit: remove dead code

Updated Branches: refs/heads/trunk 10b617364 -> 4b4a8dd4f remove dead code Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/5f60fcc3 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/5f60fcc3 Diff: http://

  1   2   >