[jira] [Assigned] (CASSANDRA-11748) Schema version mismatch may leads to Casandra OOM at bootstrap during a rolling upgrade process

[ https://issues.apache.org/jira/browse/CASSANDRA-11748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Byrd reassigned CASSANDRA-11748: - Assignee: (was: Nirmal Singh KPS) > Schema version mismatch may leads to

[jira] [Comment Edited] (CASSANDRA-11748) Schema version mismatch may leads to Casandra OOM at bootstrap during a rolling upgrade process

[ https://issues.apache.org/jira/browse/CASSANDRA-11748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663994#comment-16663994 ] Matt Byrd edited comment on CASSANDRA-11748 at 10/25/18 4:46 PM: - I

[jira] [Commented] (CASSANDRA-11748) Schema version mismatch may leads to Casandra OOM at bootstrap during a rolling upgrade process

[ https://issues.apache.org/jira/browse/CASSANDRA-11748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663994#comment-16663994 ] Matt Byrd commented on CASSANDRA-11748: --- I think it would be great to try and fix these

[jira] [Created] (CASSANDRA-14531) Only include data owned by the node in totals for repaired, un-repaired and pending repair.

Matt Byrd created CASSANDRA-14531: - Summary: Only include data owned by the node in totals for repaired, un-repaired and pending repair. Key: CASSANDRA-14531 URL:

[jira] [Assigned] (CASSANDRA-14531) Only include data owned by the node in totals for repaired, un-repaired and pending repair.

[ https://issues.apache.org/jira/browse/CASSANDRA-14531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Byrd reassigned CASSANDRA-14531: - Assignee: Matt Byrd > Only include data owned by the node in totals for repaired,

[jira] [Commented] (CASSANDRA-13557) allow different NUMACTL_ARGS to be passed in

[ https://issues.apache.org/jira/browse/CASSANDRA-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129276#comment-16129276 ] Matt Byrd commented on CASSANDRA-13557: --- for reference the commit is actually here I believe:

[jira] [Commented] (CASSANDRA-11748) Schema version mismatch may leads to Casandra OOM at bootstrap during a rolling upgrade process

[ https://issues.apache.org/jira/browse/CASSANDRA-11748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129137#comment-16129137 ] Matt Byrd commented on CASSANDRA-11748: --- Hi [~mcfongtw], Hopefully I'm interpreting your

[jira] [Commented] (CASSANDRA-11748) Schema version mismatch may leads to Casandra OOM at bootstrap during a rolling upgrade process

[ https://issues.apache.org/jira/browse/CASSANDRA-11748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122194#comment-16122194 ] Matt Byrd commented on CASSANDRA-11748: --- {quote} But we should at least take the schema Ids

[jira] [Commented] (CASSANDRA-11748) Schema version mismatch may leads to Casandra OOM at bootstrap during a rolling upgrade process

[ https://issues.apache.org/jira/browse/CASSANDRA-11748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16117330#comment-16117330 ] Matt Byrd commented on CASSANDRA-11748: --- Hey [~iamaleksey], I know as part of

[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-tabpanel=16111857#comment-16111857 ] Matt Byrd commented on CASSANDRA-8076: -- Looks like this issue was trying to address a similar

[jira] [Updated] (CASSANDRA-13480) nodetool repair can hang forever if we lose the notification for the repair completing/failing

[ https://issues.apache.org/jira/browse/CASSANDRA-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Byrd updated CASSANDRA-13480: -- Status: Ready to Commit (was: Patch Available) > nodetool repair can hang forever if we

[jira] [Updated] (CASSANDRA-13480) nodetool repair can hang forever if we lose the notification for the repair completing/failing

[ https://issues.apache.org/jira/browse/CASSANDRA-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Byrd updated CASSANDRA-13480: -- Reviewer: Chris Lohfink (was: Blake Eggleston) > nodetool repair can hang forever if we

[jira] [Commented] (CASSANDRA-13557) allow different NUMACTL_ARGS to be passed in

[ https://issues.apache.org/jira/browse/CASSANDRA-13557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056599#comment-16056599 ] Matt Byrd commented on CASSANDRA-13557: --- |3.0|3.11|Trunk|

[jira] [Commented] (CASSANDRA-11748) Schema version mismatch may leads to Casandra OOM at bootstrap during a rolling upgrade process

[ https://issues.apache.org/jira/browse/CASSANDRA-11748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054926#comment-16054926 ] Matt Byrd commented on CASSANDRA-11748: --- |3.0|3.11|Trunk|

[jira] [Comment Edited] (CASSANDRA-13480) nodetool repair can hang forever if we lose the notification for the repair completing/failing

[ https://issues.apache.org/jira/browse/CASSANDRA-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054909#comment-16054909 ] Matt Byrd edited comment on CASSANDRA-13480 at 6/19/17 11:11 PM: -

[jira] [Updated] (CASSANDRA-13480) nodetool repair can hang forever if we lose the notification for the repair completing/failing

[ https://issues.apache.org/jira/browse/CASSANDRA-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Byrd updated CASSANDRA-13480: -- Reviewer: Blake Eggleston Reproduced In: 3.0.13, 2.1.16, 4.x (was: 2.1.16,

[jira] [Comment Edited] (CASSANDRA-13480) nodetool repair can hang forever if we lose the notification for the repair completing/failing

[ https://issues.apache.org/jira/browse/CASSANDRA-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054909#comment-16054909 ] Matt Byrd edited comment on CASSANDRA-13480 at 6/19/17 11:03 PM: -

[jira] [Comment Edited] (CASSANDRA-13480) nodetool repair can hang forever if we lose the notification for the repair completing/failing

[ https://issues.apache.org/jira/browse/CASSANDRA-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054909#comment-16054909 ] Matt Byrd edited comment on CASSANDRA-13480 at 6/19/17 11:02 PM: -

[jira] [Commented] (CASSANDRA-13480) nodetool repair can hang forever if we lose the notification for the repair completing/failing

[ https://issues.apache.org/jira/browse/CASSANDRA-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054909#comment-16054909 ] Matt Byrd commented on CASSANDRA-13480: --- ||Trunk|||

[jira] [Commented] (CASSANDRA-13570) allow sub-range repairs (specifying -et -st) for a preview of repaired data

[ https://issues.apache.org/jira/browse/CASSANDRA-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16046826#comment-16046826 ] Matt Byrd commented on CASSANDRA-13570: --- Done, thanks > allow sub-range repairs (specifying

[jira] [Commented] (CASSANDRA-13569) Schedule schema pulls just once per endpoint

[ https://issues.apache.org/jira/browse/CASSANDRA-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16044683#comment-16044683 ] Matt Byrd commented on CASSANDRA-13569: --- [~spod] Yes avoiding multiple schema migrations in

[jira] [Commented] (CASSANDRA-13569) Schedule schema pulls just once per endpoint

[ https://issues.apache.org/jira/browse/CASSANDRA-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035393#comment-16035393 ] Matt Byrd commented on CASSANDRA-13569: --- Sure n.p [~spo...@gmail.com] Yes, so adding jitter in

[jira] [Comment Edited] (CASSANDRA-10699) Make schema alterations strongly consistent

[ https://issues.apache.org/jira/browse/CASSANDRA-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035130#comment-16035130 ] Matt Byrd edited comment on CASSANDRA-10699 at 6/2/17 5:56 PM: --- In

[jira] [Assigned] (CASSANDRA-10699) Make schema alterations strongly consistent

[ https://issues.apache.org/jira/browse/CASSANDRA-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Byrd reassigned CASSANDRA-10699: - Assignee: Aleksey Yeschenko (was: Matt Byrd) > Make schema alterations strongly

[jira] [Commented] (CASSANDRA-10699) Make schema alterations strongly consistent

[ https://issues.apache.org/jira/browse/CASSANDRA-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16035130#comment-16035130 ] Matt Byrd commented on CASSANDRA-10699: --- In particular I'm interested in how to avoid

[jira] [Assigned] (CASSANDRA-10699) Make schema alterations strongly consistent

[ https://issues.apache.org/jira/browse/CASSANDRA-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Byrd reassigned CASSANDRA-10699: - Assignee: Matt Byrd > Make schema alterations strongly consistent >

[jira] [Created] (CASSANDRA-13570) allow sub-range repairs (specifying -et -st) for a preview of repaired data

Matt Byrd created CASSANDRA-13570: - Summary: allow sub-range repairs (specifying -et -st) for a preview of repaired data Key: CASSANDRA-13570 URL: https://issues.apache.org/jira/browse/CASSANDRA-13570

[jira] [Commented] (CASSANDRA-11748) Schema version mismatch may leads to Casandra OOM at bootstrap during a rolling upgrade process

[ https://issues.apache.org/jira/browse/CASSANDRA-11748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16034971#comment-16034971 ] Matt Byrd commented on CASSANDRA-11748: --- So I believe the crux of this problem is: On startup

[jira] [Created] (CASSANDRA-13557) allow different NUMACTL_ARGS to be passed in

Matt Byrd created CASSANDRA-13557: - Summary: allow different NUMACTL_ARGS to be passed in Key: CASSANDRA-13557 URL: https://issues.apache.org/jira/browse/CASSANDRA-13557 Project: Cassandra

[jira] [Commented] (CASSANDRA-13480) nodetool repair can hang forever if we lose the notification for the repair completing/failing

[ https://issues.apache.org/jira/browse/CASSANDRA-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15989556#comment-15989556 ] Matt Byrd commented on CASSANDRA-13480: --- So the patch I have currently also caches the

[jira] [Created] (CASSANDRA-13480) nodetool repair can hang forever if we lose the notification for the repair completing/failing

Matt Byrd created CASSANDRA-13480: - Summary: nodetool repair can hang forever if we lose the notification for the repair completing/failing Key: CASSANDRA-13480 URL:

[jira] [Commented] (CASSANDRA-13307) The specification of protocol version in cqlsh means the python driver doesn't automatically downgrade protocol version.

[ https://issues.apache.org/jira/browse/CASSANDRA-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15968247#comment-15968247 ] Matt Byrd commented on CASSANDRA-13307: --- Hey [~michaelsembwever] Did you still want me to take

[jira] [Commented] (CASSANDRA-13307) The specification of protocol version in cqlsh means the python driver doesn't automatically downgrade protocol version.

[ https://issues.apache.org/jira/browse/CASSANDRA-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947667#comment-15947667 ] Matt Byrd commented on CASSANDRA-13307: --- Hey [~tjake] are you at all keen to review? or shall I

[jira] [Updated] (CASSANDRA-13307) The specification of protocol version in cqlsh means the python driver doesn't automatically downgrade protocol version.

[ https://issues.apache.org/jira/browse/CASSANDRA-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Byrd updated CASSANDRA-13307: -- Status: Patch Available (was: Open)

[jira] [Created] (CASSANDRA-13307) The specification of protocol version in cqlsh means the python driver doesn't automatically downgrade protocol version.

Matt Byrd created CASSANDRA-13307: - Summary: The specification of protocol version in cqlsh means the python driver doesn't automatically downgrade protocol version. Key: CASSANDRA-13307 URL:

[jira] [Commented] (CASSANDRA-7688) Add data sizing to a system table

[ https://issues.apache.org/jira/browse/CASSANDRA-7688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14299242#comment-14299242 ] Matt Byrd commented on CASSANDRA-7688: -- So I suppose the reason for suggesting

[jira] [Created] (CASSANDRA-8052) OOMs from allocating large arrays when deserializing (e.g probably corrupted EstimatedHistogram data)

Matt Byrd created CASSANDRA-8052: Summary: OOMs from allocating large arrays when deserializing (e.g probably corrupted EstimatedHistogram data) Key: CASSANDRA-8052 URL:

[jira] [Commented] (CASSANDRA-7688) Add data sizing to a system table

[ https://issues.apache.org/jira/browse/CASSANDRA-7688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14091315#comment-14091315 ] Matt Byrd commented on CASSANDRA-7688: -- Originally I was just thinking of

[jira] [Commented] (CASSANDRA-7543) Assertion error when compacting large row with map//list field or range tombstone

[ https://issues.apache.org/jira/browse/CASSANDRA-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14064110#comment-14064110 ] Matt Byrd commented on CASSANDRA-7543: -- Thanks for looking at this. With the

[jira] [Created] (CASSANDRA-7543) Assertion error when compacting large row with map//list field or range tombstone

Matt Byrd created CASSANDRA-7543: Summary: Assertion error when compacting large row with map//list field or range tombstone Key: CASSANDRA-7543 URL: https://issues.apache.org/jira/browse/CASSANDRA-7543

[jira] [Commented] (CASSANDRA-7543) Assertion error when compacting large row with map//list field or range tombstone

[ https://issues.apache.org/jira/browse/CASSANDRA-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14061463#comment-14061463 ] Matt Byrd commented on CASSANDRA-7543: -- I believe this is the same issue, which

[jira] [Updated] (CASSANDRA-7543) Assertion error when compacting large row with map//list field or range tombstone

[ https://issues.apache.org/jira/browse/CASSANDRA-7543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Byrd updated CASSANDRA-7543: - Environment: linux (was: linux cassandra 1.2.16) Assertion error when compacting large row

[jira] [Commented] (CASSANDRA-7533) Let MAX_OUTSTANDING_REPLAY_COUNT be configurable

[ https://issues.apache.org/jira/browse/CASSANDRA-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14061506#comment-14061506 ] Matt Byrd commented on CASSANDRA-7533: -- Just to add a bit more context, we had a

[jira] [Updated] (CASSANDRA-5345) Potential problem with GarbageCollectorMXBean

[ https://issues.apache.org/jira/browse/CASSANDRA-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Byrd updated CASSANDRA-5345: - Reproduced In: 1.0.7 Potential problem with GarbageCollectorMXBean

[jira] [Updated] (CASSANDRA-5345) Potential problem with GarbageCollectorMXBean

[ https://issues.apache.org/jira/browse/CASSANDRA-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Byrd updated CASSANDRA-5345: - Reproduced In: (was: 1.0.7) Since Version: 1.0.7 Potential problem with

[jira] [Updated] (CASSANDRA-5345) Potential problem with GarbageCollectorMXBean

[ https://issues.apache.org/jira/browse/CASSANDRA-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Byrd updated CASSANDRA-5345: - Priority: Major (was: Trivial) Potential problem with GarbageCollectorMXBean

[jira] [Commented] (CASSANDRA-5345) Potential problem with GarbageCollectorMXBean

[ https://issues.apache.org/jira/browse/CASSANDRA-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13946228#comment-13946228 ] Matt Byrd commented on CASSANDRA-5345: -- The cluster in question was running on

[jira] [Created] (CASSANDRA-6797) compaction and scrub data directories race on startup

Matt Byrd created CASSANDRA-6797: Summary: compaction and scrub data directories race on startup Key: CASSANDRA-6797 URL: https://issues.apache.org/jira/browse/CASSANDRA-6797 Project: Cassandra

[jira] [Commented] (CASSANDRA-6797) compaction and scrub data directories race on startup

[ https://issues.apache.org/jira/browse/CASSANDRA-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13918938#comment-13918938 ] Matt Byrd commented on CASSANDRA-6797: -- I think this may be the same or a similar

[jira] [Comment Edited] (CASSANDRA-6797) compaction and scrub data directories race on startup

[ https://issues.apache.org/jira/browse/CASSANDRA-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13918938#comment-13918938 ] Matt Byrd edited comment on CASSANDRA-6797 at 3/4/14 5:18 AM:

[jira] [Created] (CASSANDRA-5345) Potential problem with GarbageCollectorMXBean

Matt Byrd created CASSANDRA-5345: Summary: Potential problem with GarbageCollectorMXBean Key: CASSANDRA-5345 URL: https://issues.apache.org/jira/browse/CASSANDRA-5345 Project: Cassandra