[jira] [Updated] (CASSANDRA-19975) TopologyMixupTestBase does not fix replication factor for Keyspaces after reaching rf=3
[
https://issues.apache.org/jira/browse/CASSANDRA-19975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19975:
Bug Category: Parent values: Correctness(12982)Level 1 values: Test
Failure(12990) (was: Parent values: Correctness(12982)Level 1 values:
Unrecoverable Corruption / Loss(13161))
> TopologyMixupTestBase does not fix replication factor for Keyspaces after
> reaching rf=3
> ---
>
> Key: CASSANDRA-19975
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19975
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 5.x
>
>
> This issue was found by the HarryTopologyMixupTest… in the cep-15-accord
> branch we added stopping nodes as well as restarting nodes (now that accord
> supports it) and this looks to break TCM if the down node is a CMS voting
> member.
> Here is the test that shows it
> {code}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one
> * or more contributor license agreements. See the NOTICE file
> * distributed with this work for additional information
> * regarding copyright ownership. The ASF licenses this file
> * to you under the Apache License, Version 2.0 (the
> * "License"); you may not use this file except in compliance
> * with the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.cassandra.distributed.test.tcm;
> import accord.utils.Invariants;
> import accord.utils.async.TimeoutUtils;
> import org.agrona.collections.Long2LongHashMap;
> import org.apache.cassandra.distributed.Cluster;
> import org.apache.cassandra.distributed.api.Feature;
> import org.apache.cassandra.distributed.api.IInvokableInstance;
> import org.apache.cassandra.distributed.impl.INodeProvisionStrategy;
> import org.apache.cassandra.distributed.shared.ClusterUtils;
> import org.apache.cassandra.distributed.test.TestBaseImpl;
> import org.junit.Test;
> import java.io.IOException;
> import java.time.Duration;
> import java.util.concurrent.ExecutionException;
> import java.util.concurrent.TimeoutException;
> import java.util.concurrent.atomic.AtomicInteger;
> public class RepoTest extends TestBaseImpl
> {
> /**
> * This is the history reported from HarryTopologyMixupTest
> *
> History:
> 2: Add Node3; epoch=18, cms=[1, 2]
> // hidden - reconfigure to rf=3
> 3: Waiting for CMS to Quiesce; epoch=18, cms=[1, 2]
> 5: Harry Validate All; epoch=31, cms=[1, 2, 3]
> 6: Harry Insert; epoch=31, cms=[1, 2, 3]
> 8: Add Node4; epoch=31, cms=[1, 2, 3]
> 9: Waiting for CMS to Quiesce; epoch=31, cms=[1, 2, 3]
> 10: Harry Validate All; epoch=38, cms=[1, 2, 3]
> 11: nodetool repair harry tbl_0 from node2; epoch=38, cms=[1, 2, 3]
> 12: Stop Node3 for nodetool removenode; epoch=38, cms=[1, 2, 3]
> 13: nodetool removenode node3 from node1; epoch=38, cms=[1, 2, 3]
> 14: nodetool repair harry tbl_0 from node1; epoch=49, cms=[1, 2, 3]
> 15: Waiting for CMS to Quiesce; epoch=49, cms=[1, 2, 3]
> 16: Stop Node1 for Normal Stop; epoch=49, cms=[1, 2, 4]
> 18: Add Node5; epoch=49, cms=[1, 2, 4]
> */
> @Test
> public void test() throws IOException, ExecutionException,
> InterruptedException, TimeoutException
> {
> Long2LongHashMap nodeToToken = new Long2LongHashMap(-0);
> nodeToToken.put(1, -1799911656L);
> nodeToToken.put(2, -1005197310L);
> nodeToToken.put(3, -834315596L);
> nodeToToken.put(4, 335272232L);
> nodeToToken.put(5, -1829188286L);
> final AtomicInteger counter = new AtomicInteger(0);
> try (Cluster cluster = Cluster.build(2)
> .withTokenSupplier(i ->
> nodeToToken.get(i))
> .withConfig(c ->
> c.with(Feature.values()))
> .withNodeProvisionStrategy((subnet,
> portMap) -> new INodeProvisionStrategy.AbstractNodeProvisionStrategy(portMap)
> {
> {
> Invariants.checkArgument(subnet
> == 0, "Unexpected subnet detected: %d", subnet);
>
[jira] [Updated] (CASSANDRA-19975) TopologyMixupTestBase does not fix replication factor for Keyspaces after reaching rf=3
[
https://issues.apache.org/jira/browse/CASSANDRA-19975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19975:
Component/s: (was: Transactional Cluster Metadata)
> TopologyMixupTestBase does not fix replication factor for Keyspaces after
> reaching rf=3
> ---
>
> Key: CASSANDRA-19975
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19975
> Project: Cassandra
> Issue Type: Bug
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Low
> Fix For: 5.x
>
>
> This issue was found by the HarryTopologyMixupTest… in the cep-15-accord
> branch we added stopping nodes as well as restarting nodes (now that accord
> supports it) and this looks to break TCM if the down node is a CMS voting
> member.
> Here is the test that shows it
> {code}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one
> * or more contributor license agreements. See the NOTICE file
> * distributed with this work for additional information
> * regarding copyright ownership. The ASF licenses this file
> * to you under the Apache License, Version 2.0 (the
> * "License"); you may not use this file except in compliance
> * with the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.cassandra.distributed.test.tcm;
> import accord.utils.Invariants;
> import accord.utils.async.TimeoutUtils;
> import org.agrona.collections.Long2LongHashMap;
> import org.apache.cassandra.distributed.Cluster;
> import org.apache.cassandra.distributed.api.Feature;
> import org.apache.cassandra.distributed.api.IInvokableInstance;
> import org.apache.cassandra.distributed.impl.INodeProvisionStrategy;
> import org.apache.cassandra.distributed.shared.ClusterUtils;
> import org.apache.cassandra.distributed.test.TestBaseImpl;
> import org.junit.Test;
> import java.io.IOException;
> import java.time.Duration;
> import java.util.concurrent.ExecutionException;
> import java.util.concurrent.TimeoutException;
> import java.util.concurrent.atomic.AtomicInteger;
> public class RepoTest extends TestBaseImpl
> {
> /**
> * This is the history reported from HarryTopologyMixupTest
> *
> History:
> 2: Add Node3; epoch=18, cms=[1, 2]
> // hidden - reconfigure to rf=3
> 3: Waiting for CMS to Quiesce; epoch=18, cms=[1, 2]
> 5: Harry Validate All; epoch=31, cms=[1, 2, 3]
> 6: Harry Insert; epoch=31, cms=[1, 2, 3]
> 8: Add Node4; epoch=31, cms=[1, 2, 3]
> 9: Waiting for CMS to Quiesce; epoch=31, cms=[1, 2, 3]
> 10: Harry Validate All; epoch=38, cms=[1, 2, 3]
> 11: nodetool repair harry tbl_0 from node2; epoch=38, cms=[1, 2, 3]
> 12: Stop Node3 for nodetool removenode; epoch=38, cms=[1, 2, 3]
> 13: nodetool removenode node3 from node1; epoch=38, cms=[1, 2, 3]
> 14: nodetool repair harry tbl_0 from node1; epoch=49, cms=[1, 2, 3]
> 15: Waiting for CMS to Quiesce; epoch=49, cms=[1, 2, 3]
> 16: Stop Node1 for Normal Stop; epoch=49, cms=[1, 2, 4]
> 18: Add Node5; epoch=49, cms=[1, 2, 4]
> */
> @Test
> public void test() throws IOException, ExecutionException,
> InterruptedException, TimeoutException
> {
> Long2LongHashMap nodeToToken = new Long2LongHashMap(-0);
> nodeToToken.put(1, -1799911656L);
> nodeToToken.put(2, -1005197310L);
> nodeToToken.put(3, -834315596L);
> nodeToToken.put(4, 335272232L);
> nodeToToken.put(5, -1829188286L);
> final AtomicInteger counter = new AtomicInteger(0);
> try (Cluster cluster = Cluster.build(2)
> .withTokenSupplier(i ->
> nodeToToken.get(i))
> .withConfig(c ->
> c.with(Feature.values()))
> .withNodeProvisionStrategy((subnet,
> portMap) -> new INodeProvisionStrategy.AbstractNodeProvisionStrategy(portMap)
> {
> {
> Invariants.checkArgument(subnet
> == 0, "Unexpected subnet detected: %d", subnet);
> }
> private final String ipPrefix =
> "127.0." + subnet + '.';
> @Overr
[jira] [Updated] (CASSANDRA-19975) TopologyMixupTestBase does not fix replication factor for Keyspaces after reaching rf=3
[
https://issues.apache.org/jira/browse/CASSANDRA-19975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19975:
Severity: Low (was: Critical)
> TopologyMixupTestBase does not fix replication factor for Keyspaces after
> reaching rf=3
> ---
>
> Key: CASSANDRA-19975
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19975
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Low
> Fix For: 5.x
>
>
> This issue was found by the HarryTopologyMixupTest… in the cep-15-accord
> branch we added stopping nodes as well as restarting nodes (now that accord
> supports it) and this looks to break TCM if the down node is a CMS voting
> member.
> Here is the test that shows it
> {code}
> /*
> * Licensed to the Apache Software Foundation (ASF) under one
> * or more contributor license agreements. See the NOTICE file
> * distributed with this work for additional information
> * regarding copyright ownership. The ASF licenses this file
> * to you under the Apache License, Version 2.0 (the
> * "License"); you may not use this file except in compliance
> * with the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> package org.apache.cassandra.distributed.test.tcm;
> import accord.utils.Invariants;
> import accord.utils.async.TimeoutUtils;
> import org.agrona.collections.Long2LongHashMap;
> import org.apache.cassandra.distributed.Cluster;
> import org.apache.cassandra.distributed.api.Feature;
> import org.apache.cassandra.distributed.api.IInvokableInstance;
> import org.apache.cassandra.distributed.impl.INodeProvisionStrategy;
> import org.apache.cassandra.distributed.shared.ClusterUtils;
> import org.apache.cassandra.distributed.test.TestBaseImpl;
> import org.junit.Test;
> import java.io.IOException;
> import java.time.Duration;
> import java.util.concurrent.ExecutionException;
> import java.util.concurrent.TimeoutException;
> import java.util.concurrent.atomic.AtomicInteger;
> public class RepoTest extends TestBaseImpl
> {
> /**
> * This is the history reported from HarryTopologyMixupTest
> *
> History:
> 2: Add Node3; epoch=18, cms=[1, 2]
> // hidden - reconfigure to rf=3
> 3: Waiting for CMS to Quiesce; epoch=18, cms=[1, 2]
> 5: Harry Validate All; epoch=31, cms=[1, 2, 3]
> 6: Harry Insert; epoch=31, cms=[1, 2, 3]
> 8: Add Node4; epoch=31, cms=[1, 2, 3]
> 9: Waiting for CMS to Quiesce; epoch=31, cms=[1, 2, 3]
> 10: Harry Validate All; epoch=38, cms=[1, 2, 3]
> 11: nodetool repair harry tbl_0 from node2; epoch=38, cms=[1, 2, 3]
> 12: Stop Node3 for nodetool removenode; epoch=38, cms=[1, 2, 3]
> 13: nodetool removenode node3 from node1; epoch=38, cms=[1, 2, 3]
> 14: nodetool repair harry tbl_0 from node1; epoch=49, cms=[1, 2, 3]
> 15: Waiting for CMS to Quiesce; epoch=49, cms=[1, 2, 3]
> 16: Stop Node1 for Normal Stop; epoch=49, cms=[1, 2, 4]
> 18: Add Node5; epoch=49, cms=[1, 2, 4]
> */
> @Test
> public void test() throws IOException, ExecutionException,
> InterruptedException, TimeoutException
> {
> Long2LongHashMap nodeToToken = new Long2LongHashMap(-0);
> nodeToToken.put(1, -1799911656L);
> nodeToToken.put(2, -1005197310L);
> nodeToToken.put(3, -834315596L);
> nodeToToken.put(4, 335272232L);
> nodeToToken.put(5, -1829188286L);
> final AtomicInteger counter = new AtomicInteger(0);
> try (Cluster cluster = Cluster.build(2)
> .withTokenSupplier(i ->
> nodeToToken.get(i))
> .withConfig(c ->
> c.with(Feature.values()))
> .withNodeProvisionStrategy((subnet,
> portMap) -> new INodeProvisionStrategy.AbstractNodeProvisionStrategy(portMap)
> {
> {
> Invariants.checkArgument(subnet
> == 0, "Unexpected subnet detected: %d", subnet);
> }
> private final String ipPrefix =
> "127.0." + subnet + '.';
>
[jira] [Updated] (CASSANDRA-19970) Introduce metadata serialization version V4
[ https://issues.apache.org/jira/browse/CASSANDRA-19970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19970: Status: In Progress (was: Patch Available) > Introduce metadata serialization version V4 > --- > > Key: CASSANDRA-19970 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19970 > Project: Cassandra > Issue Type: Task > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > > To resolve a version conflict we need to introduce metadata serialization > version V4 and move the TableParams from CASSANDRA-19954 there -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19970) Introduce metadata serialization version V4
[ https://issues.apache.org/jira/browse/CASSANDRA-19970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19970: Change Category: Operability Complexity: Low Hanging Fruit Component/s: Transactional Cluster Metadata Status: Open (was: Triage Needed) > Introduce metadata serialization version V4 > --- > > Key: CASSANDRA-19970 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19970 > Project: Cassandra > Issue Type: Task > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > > To resolve a version conflict we need to introduce metadata serialization > version V4 and move the TableParams from CASSANDRA-19954 there -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19970) Introduce metadata serialization version V4
[ https://issues.apache.org/jira/browse/CASSANDRA-19970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19970: Test and Documentation Plan: ci run Status: Patch Available (was: Open) > Introduce metadata serialization version V4 > --- > > Key: CASSANDRA-19970 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19970 > Project: Cassandra > Issue Type: Task > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > > To resolve a version conflict we need to introduce metadata serialization > version V4 and move the TableParams from CASSANDRA-19954 there -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19970) Introduce metadata serialization version V4
Marcus Eriksson created CASSANDRA-19970: --- Summary: Introduce metadata serialization version V4 Key: CASSANDRA-19970 URL: https://issues.apache.org/jira/browse/CASSANDRA-19970 Project: Cassandra Issue Type: Task Reporter: Marcus Eriksson Assignee: Marcus Eriksson To resolve a version conflict we need to introduce metadata serialization version V4 and move the TableParams from CASSANDRA-19954 there -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19970) Introduce metadata serialization version V4
[ https://issues.apache.org/jira/browse/CASSANDRA-19970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19970: Status: Review In Progress (was: Patch Available) > Introduce metadata serialization version V4 > --- > > Key: CASSANDRA-19970 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19970 > Project: Cassandra > Issue Type: Task > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > > To resolve a version conflict we need to introduce metadata serialization > version V4 and move the TableParams from CASSANDRA-19954 there -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19970) Introduce metadata serialization version V4
[ https://issues.apache.org/jira/browse/CASSANDRA-19970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19970: Fix Version/s: 5.1-alpha1 Source Control Link: https://github.com/apache/cassandra/commit/6111a60ad68725f1a318a2301788ec50023d4c85 Resolution: Fixed Status: Resolved (was: Ready to Commit) committed, thanks! > Introduce metadata serialization version V4 > --- > > Key: CASSANDRA-19970 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19970 > Project: Cassandra > Issue Type: Task > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 5.1-alpha1 > > Attachments: ci_summary.html > > > To resolve a version conflict we need to introduce metadata serialization > version V4 and move the TableParams from CASSANDRA-19954 there -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19970) Introduce metadata serialization version V4
[ https://issues.apache.org/jira/browse/CASSANDRA-19970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19970: Status: Ready to Commit (was: Review In Progress) > Introduce metadata serialization version V4 > --- > > Key: CASSANDRA-19970 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19970 > Project: Cassandra > Issue Type: Task > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > > To resolve a version conflict we need to introduce metadata serialization > version V4 and move the TableParams from CASSANDRA-19954 there -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19970) Introduce metadata serialization version V4
[ https://issues.apache.org/jira/browse/CASSANDRA-19970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19970: Status: Patch Available (was: In Progress) > Introduce metadata serialization version V4 > --- > > Key: CASSANDRA-19970 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19970 > Project: Cassandra > Issue Type: Task > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > > To resolve a version conflict we need to introduce metadata serialization > version V4 and move the TableParams from CASSANDRA-19954 there -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19970) Introduce metadata serialization version V4
[ https://issues.apache.org/jira/browse/CASSANDRA-19970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19970: Attachment: ci_summary.html > Introduce metadata serialization version V4 > --- > > Key: CASSANDRA-19970 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19970 > Project: Cassandra > Issue Type: Task >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > > To resolve a version conflict we need to introduce metadata serialization > version V4 and move the TableParams from CASSANDRA-19954 there -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19970) Introduce metadata serialization version V4
[ https://issues.apache.org/jira/browse/CASSANDRA-19970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19970: Reviewers: Stefan Miklosovic (was: Sam Tunnicliffe) > Introduce metadata serialization version V4 > --- > > Key: CASSANDRA-19970 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19970 > Project: Cassandra > Issue Type: Task >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > > To resolve a version conflict we need to introduce metadata serialization > version V4 and move the TableParams from CASSANDRA-19954 there -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19970) Introduce metadata serialization version V4
[ https://issues.apache.org/jira/browse/CASSANDRA-19970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19970: Reviewers: Sam Tunnicliffe > Introduce metadata serialization version V4 > --- > > Key: CASSANDRA-19970 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19970 > Project: Cassandra > Issue Type: Task >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > > To resolve a version conflict we need to introduce metadata serialization > version V4 and move the TableParams from CASSANDRA-19954 there -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19943) Allow CMS reconfiguration to work around DOWN nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19943: Fix Version/s: 5.1-alpha1 Since Version: 5.1-alpha1 Source Control Link: https://github.com/apache/cassandra/commit/279c0527aa3d52e1474fee5f37c0227ed6f9da5f Resolution: Fixed Status: Resolved (was: Ready to Commit) > Allow CMS reconfiguration to work around DOWN nodes > --- > > Key: CASSANDRA-19943 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19943 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 5.1-alpha1 > > Attachments: ci_summary.html > > Time Spent: 20m > Remaining Estimate: 0h > > When replacing a node with several instances DOWN in a cluster we might move > the CMS on to those DOWN nodes, making a majority of the CMS down. When > reconfiguring we should avoid those instances. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-19881) Test Failure: org.apache.cassandra.distributed.test.tcm.CMSPlacementAfterMoveTest.testMoveToCMS
[
https://issues.apache.org/jira/browse/CASSANDRA-19881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson reassigned CASSANDRA-19881:
---
Assignee: Marcus Eriksson
> Test Failure:
> org.apache.cassandra.distributed.test.tcm.CMSPlacementAfterMoveTest.testMoveToCMS
> ---
>
> Key: CASSANDRA-19881
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19881
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
>
> Seen
> [here|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2731/workflows/b987651a-5280-4dd6-9895-3298456406c8/jobs/61576/tests#failed-test-0]
> and
> [here|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2731/workflows/b987651a-5280-4dd6-9895-3298456406c8/jobs/61577/tests#failed-test-0]
> {code:java}
> junit.framework.AssertionFailedError: /127.0.0.4:7012 did not become a CMS
> member after 11 seconds
> at
> org.apache.cassandra.distributed.test.tcm.CMSPlacementAfterReplacementTest.lambda$assertInCMS$18759fb3$1(CMSPlacementAfterReplacementTest.java:104)
> at
> org.apache.cassandra.concurrent.FutureTask$2.call(FutureTask.java:124)
> at org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:61)
> at org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:71)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19943) Allow CMS reconfiguration to work around DOWN nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19943: Test and Documentation Plan: ci run Status: Patch Available (was: Open) > Allow CMS reconfiguration to work around DOWN nodes > --- > > Key: CASSANDRA-19943 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19943 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > Time Spent: 20m > Remaining Estimate: 0h > > When replacing a node with several instances DOWN in a cluster we might move > the CMS on to those DOWN nodes, making a majority of the CMS down. When > reconfiguring we should avoid those instances. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19954) TableParams.Serializer does not set allowAutoSnapshots nor incrementalBackups
[ https://issues.apache.org/jira/browse/CASSANDRA-19954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884926#comment-17884926 ] Marcus Eriksson commented on CASSANDRA-19954: - +1 assuming clean CI > TableParams.Serializer does not set allowAutoSnapshots nor incrementalBackups > -- > > Key: CASSANDRA-19954 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19954 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > They are missing in trunk, probably not included as TCM was materializing. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19943) Allow CMS reconfiguration to work around DOWN nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19943: Bug Category: Parent values: Availability(12983)Level 1 values: Unavailable(12994) Complexity: Normal Component/s: Transactional Cluster Metadata Discovered By: Adhoc Test Reviewers: Sam Tunnicliffe Severity: Normal Status: Open (was: Triage Needed) > Allow CMS reconfiguration to work around DOWN nodes > --- > > Key: CASSANDRA-19943 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19943 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > Time Spent: 20m > Remaining Estimate: 0h > > When replacing a node with several instances DOWN in a cluster we might move > the CMS on to those DOWN nodes, making a majority of the CMS down. When > reconfiguring we should avoid those instances. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19943) Allow CMS reconfiguration to work around DOWN nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19943: Attachment: ci_summary.html > Allow CMS reconfiguration to work around DOWN nodes > --- > > Key: CASSANDRA-19943 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19943 > Project: Cassandra > Issue Type: Bug >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > Time Spent: 20m > Remaining Estimate: 0h > > When replacing a node with several instances DOWN in a cluster we might move > the CMS on to those DOWN nodes, making a majority of the CMS down. When > reconfiguring we should avoid those instances. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19943) Allow CMS reconfiguration to work around DOWN nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884901#comment-17884901 ] Marcus Eriksson commented on CASSANDRA-19943: - ci run with the attached python-dtest branch PR, avoids placing the CMS on the node we're about to wipe > Allow CMS reconfiguration to work around DOWN nodes > --- > > Key: CASSANDRA-19943 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19943 > Project: Cassandra > Issue Type: Bug >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > Time Spent: 20m > Remaining Estimate: 0h > > When replacing a node with several instances DOWN in a cluster we might move > the CMS on to those DOWN nodes, making a majority of the CMS down. When > reconfiguring we should avoid those instances. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19954) TableParams.Serializer does not set allowAutoSnapshots nor incrementalBackups
[ https://issues.apache.org/jira/browse/CASSANDRA-19954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19954: Reviewers: David Capwell, Marcus Eriksson > TableParams.Serializer does not set allowAutoSnapshots nor incrementalBackups > -- > > Key: CASSANDRA-19954 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19954 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > Time Spent: 20m > Remaining Estimate: 0h > > They are missing in trunk, probably not included as TCM was materializing. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19943) Allow CMS reconfiguration to work around DOWN nodes
Marcus Eriksson created CASSANDRA-19943: --- Summary: Allow CMS reconfiguration to work around DOWN nodes Key: CASSANDRA-19943 URL: https://issues.apache.org/jira/browse/CASSANDRA-19943 Project: Cassandra Issue Type: Bug Reporter: Marcus Eriksson Assignee: Marcus Eriksson When replacing a node with several instances DOWN in a cluster we might move the CMS on to those DOWN nodes, making a majority of the CMS down. When reconfiguring we should avoid those instances. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19921) Allow nodes to change IP address while upgrading to TCM
[
https://issues.apache.org/jira/browse/CASSANDRA-19921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19921:
Fix Version/s: 5.1-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/cdfce6b4ac5b2d3a6106001f4d6eb9234bbaa300
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Allow nodes to change IP address while upgrading to TCM
> ---
>
> Key: CASSANDRA-19921
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19921
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We currently only allow node version to change via gossip while upgrading to
> TCM (in mixed mode or before {{nodetool cms initialize}} has been run). We
> should also allow ip addresses to change since that can happen while bouncing
> nodes in some environments.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19916) Retain keyspace params after upgrade
[ https://issues.apache.org/jira/browse/CASSANDRA-19916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19916: Fix Version/s: 5.1-alpha1 Since Version: 5.1-alpha1 Source Control Link: https://github.com/apache/cassandra/commit/8d082508ef7fd6590dda1d777092dd3524b2c27a Resolution: Fixed Status: Resolved (was: Ready to Commit) > Retain keyspace params after upgrade > > > Key: CASSANDRA-19916 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19916 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 5.1-alpha1 > > Attachments: ci_summary.html > > > If a user has altered the keyspace params (replication factor) on a > system-defined table (like system_auth), we should retain that on upgrade. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19921) Allow nodes to change IP address while upgrading to TCM
[
https://issues.apache.org/jira/browse/CASSANDRA-19921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19921:
Attachment: ci_summary.html
> Allow nodes to change IP address while upgrading to TCM
> ---
>
> Key: CASSANDRA-19921
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19921
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We currently only allow node version to change via gossip while upgrading to
> TCM (in mixed mode or before {{nodetool cms initialize}} has been run). We
> should also allow ip addresses to change since that can happen while bouncing
> nodes in some environments.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19921) Allow nodes to change IP address while upgrading to TCM
[
https://issues.apache.org/jira/browse/CASSANDRA-19921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19921:
Change Category: Operability
Complexity: Normal
Reviewers: Sam Tunnicliffe
Status: Open (was: Triage Needed)
> Allow nodes to change IP address while upgrading to TCM
> ---
>
> Key: CASSANDRA-19921
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19921
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We currently only allow node version to change via gossip while upgrading to
> TCM (in mixed mode or before {{nodetool cms initialize}} has been run). We
> should also allow ip addresses to change since that can happen while bouncing
> nodes in some environments.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19921) Allow nodes to change IP address while upgrading to TCM
[
https://issues.apache.org/jira/browse/CASSANDRA-19921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19921:
Test and Documentation Plan: ci run
Status: Patch Available (was: Open)
> Allow nodes to change IP address while upgrading to TCM
> ---
>
> Key: CASSANDRA-19921
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19921
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We currently only allow node version to change via gossip while upgrading to
> TCM (in mixed mode or before {{nodetool cms initialize}} has been run). We
> should also allow ip addresses to change since that can happen while bouncing
> nodes in some environments.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19921) Allow nodes to change IP address while upgrading to TCM
Marcus Eriksson created CASSANDRA-19921:
---
Summary: Allow nodes to change IP address while upgrading to TCM
Key: CASSANDRA-19921
URL: https://issues.apache.org/jira/browse/CASSANDRA-19921
Project: Cassandra
Issue Type: Improvement
Components: Transactional Cluster Metadata
Reporter: Marcus Eriksson
Assignee: Marcus Eriksson
We currently only allow node version to change via gossip while upgrading to
TCM (in mixed mode or before {{nodetool cms initialize}} has been run). We
should also allow ip addresses to change since that can happen while bouncing
nodes in some environments.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19916) Retain keyspace params after upgrade
[ https://issues.apache.org/jira/browse/CASSANDRA-19916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881291#comment-17881291 ] Marcus Eriksson commented on CASSANDRA-19916: - ci a bit noisy, a few timeouts, https://issues.apache.org/jira/browse/CASSANDRA-19280 and https://issues.apache.org/jira/browse/CASSANDRA-19848 > Retain keyspace params after upgrade > > > Key: CASSANDRA-19916 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19916 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > > If a user has altered the keyspace params (replication factor) on a > system-defined table (like system_auth), we should retain that on upgrade. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19916) Retain keyspace params after upgrade
[ https://issues.apache.org/jira/browse/CASSANDRA-19916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19916: Attachment: ci_summary.html > Retain keyspace params after upgrade > > > Key: CASSANDRA-19916 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19916 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > > If a user has altered the keyspace params (replication factor) on a > system-defined table (like system_auth), we should retain that on upgrade. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19916) Retain keyspace params after upgrade
[ https://issues.apache.org/jira/browse/CASSANDRA-19916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19916: Bug Category: Parent values: Availability(12983)Level 1 values: Unavailable(12994) Complexity: Low Hanging Fruit Discovered By: Adhoc Test Reviewers: Sam Tunnicliffe Severity: Normal Status: Open (was: Triage Needed) > Retain keyspace params after upgrade > > > Key: CASSANDRA-19916 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19916 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > > If a user has altered the keyspace params (replication factor) on a > system-defined table (like system_auth), we should retain that on upgrade. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19916) Retain keyspace params after upgrade
Marcus Eriksson created CASSANDRA-19916: --- Summary: Retain keyspace params after upgrade Key: CASSANDRA-19916 URL: https://issues.apache.org/jira/browse/CASSANDRA-19916 Project: Cassandra Issue Type: Bug Components: Transactional Cluster Metadata Reporter: Marcus Eriksson Assignee: Marcus Eriksson If a user has altered the keyspace params (replication factor) on a system-defined table (like system_auth), we should retain that on upgrade. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19871) Add size to the segment index for safer journal reads
[ https://issues.apache.org/jira/browse/CASSANDRA-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877415#comment-17877415 ] Marcus Eriksson commented on CASSANDRA-19871: - +1 > Add size to the segment index for safer journal reads > - > > Key: CASSANDRA-19871 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19871 > Project: Cassandra > Issue Type: New Feature > Components: Accord >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: Normal > Attachments: ci_summary.html, result_details.tar.gz > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19872) Handle losing CMS status while committing a transformation
[ https://issues.apache.org/jira/browse/CASSANDRA-19872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19872: Reviewers: David Capwell, Sam Tunnicliffe (was: David Capwell) > Handle losing CMS status while committing a transformation > -- > > Key: CASSANDRA-19872 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19872 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 5.x > > Attachments: ci_summary.html > > Time Spent: 0.5h > Remaining Estimate: 0h > > There is a small window where we might try to use the wrong processor when > committing a transformation while the CMS changes - in this case we should > just retry the commit and we'll use the RemoteProcessor -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19846) Allow looking up local tables in nodetool getendpoints
[
https://issues.apache.org/jira/browse/CASSANDRA-19846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19846:
Fix Version/s: 5.1-alpha1
(was: 5.x)
Since Version: 5.1
Source Control Link:
https://github.com/apache/cassandra/commit/a2dad4ab1947971cb2c92995ab25a8adba7ef40b
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Allow looking up local tables in nodetool getendpoints
> --
>
> Key: CASSANDRA-19846
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19846
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In versions before 5.1 we allow looking up the endpoints for local tables
> using {{nodetool getendpoints}} - we only return the local node, but some
> scripts might depend on this so we should support it in 5.1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19845) Handle existing tables with non-expected table ids
[ https://issues.apache.org/jira/browse/CASSANDRA-19845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19845: Fix Version/s: 5.1 (was: 5.x) Since Version: 5.1-alpha1 Source Control Link: https://github.com/apache/cassandra/commit/e1540fc85b1429f339e0251ecc3e048620df943a Resolution: Fixed Status: Resolved (was: Ready to Commit) > Handle existing tables with non-expected table ids > -- > > Key: CASSANDRA-19845 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19845 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 5.1 > > Attachments: ci_summary.html > > Time Spent: 10m > Remaining Estimate: 0h > > On upgrade we merge the existing tables with the pre-defined ones, but we > only check if the tableid exists, we should also check the name of the table > since the id can be defined by the user. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19768) nodetool assassinate of a CMS voting member should be allowed and should remove it from the CMS group
[
https://issues.apache.org/jira/browse/CASSANDRA-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19768:
Fix Version/s: 5.1
(was: 5.x)
Since Version: 5.1-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/e5973bf34f7f61347f7e5d6aaafad3ed38f2f8b7
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> nodetool assassinate of a CMS voting member should be allowed and should
> remove it from the CMS group
> -
>
> Key: CASSANDRA-19768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19768
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.1
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> nodetool assassinate is a dangerous command but is needed when the node to be
> removed really can’t be accessed anymore (such as host failures). But when
> the node to be removed is a member of CMS, we block this action with the
> following error
> {code}
> Can not commit transformation: "INVALID"(Rejecting this plan as the node
> NodeId{id=3} is still a part of CMS.).
> {code}
> If the node in question is not up, and we call nodetool assassinate, we
> should then try to remove that node from the CMS membership group
> Steps to repo
> * Start 4 node cluster
> * nodetool cms reconfigure 3
> * targetNode =
> * stop targetNode
> * nodetool assassinate targetNode
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19846) Allow looking up local tables in nodetool getendpoints
[
https://issues.apache.org/jira/browse/CASSANDRA-19846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877258#comment-17877258
]
Marcus Eriksson commented on CASSANDRA-19846:
-
attaching CI run with CASSANDRA-19768 + CASSANDRA-19845 + CASSANDRA-19846
> Allow looking up local tables in nodetool getendpoints
> --
>
> Key: CASSANDRA-19846
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19846
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In versions before 5.1 we allow looking up the endpoints for local tables
> using {{nodetool getendpoints}} - we only return the local node, but some
> scripts might depend on this so we should support it in 5.1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19846) Allow looking up local tables in nodetool getendpoints
[
https://issues.apache.org/jira/browse/CASSANDRA-19846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19846:
Attachment: ci_summary.html
> Allow looking up local tables in nodetool getendpoints
> --
>
> Key: CASSANDRA-19846
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19846
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In versions before 5.1 we allow looking up the endpoints for local tables
> using {{nodetool getendpoints}} - we only return the local node, but some
> scripts might depend on this so we should support it in 5.1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19872) Handle losing CMS status while committing a transformation
[ https://issues.apache.org/jira/browse/CASSANDRA-19872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19872: Attachment: ci_summary.html > Handle losing CMS status while committing a transformation > -- > > Key: CASSANDRA-19872 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19872 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 5.x > > Attachments: ci_summary.html > > Time Spent: 10m > Remaining Estimate: 0h > > There is a small window where we might try to use the wrong processor when > committing a transformation while the CMS changes - in this case we should > just retry the commit and we'll use the RemoteProcessor -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19872) Handle losing CMS status while committing a transformation
[ https://issues.apache.org/jira/browse/CASSANDRA-19872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19872: Bug Category: Parent values: Degradation(12984)Level 1 values: Other Exception(12998) Complexity: Normal Discovered By: Fuzz Test Fix Version/s: 5.x Reviewers: David Capwell Severity: Low Status: Open (was: Triage Needed) Found by [~dcapwell] in CASSANDRA-19847 - test is in that ticket > Handle losing CMS status while committing a transformation > -- > > Key: CASSANDRA-19872 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19872 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > There is a small window where we might try to use the wrong processor when > committing a transformation while the CMS changes - in this case we should > just retry the commit and we'll use the RemoteProcessor -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19872) Handle losing CMS status while committing a transformation
Marcus Eriksson created CASSANDRA-19872: --- Summary: Handle losing CMS status while committing a transformation Key: CASSANDRA-19872 URL: https://issues.apache.org/jira/browse/CASSANDRA-19872 Project: Cassandra Issue Type: Bug Components: Transactional Cluster Metadata Reporter: Marcus Eriksson Assignee: Marcus Eriksson There is a small window where we might try to use the wrong processor when committing a transformation while the CMS changes - in this case we should just retry the commit and we'll use the RemoteProcessor -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19790) Add an ability to reconstruct arbitrary epoch state from the log to TCM
[ https://issues.apache.org/jira/browse/CASSANDRA-19790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876642#comment-17876642 ] Marcus Eriksson commented on CASSANDRA-19790: - +1 > Add an ability to reconstruct arbitrary epoch state from the log to TCM > --- > > Key: CASSANDRA-19790 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19790 > Project: Cassandra > Issue Type: New Feature > Components: Transactional Cluster Metadata >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: High > Fix For: 5.1 > > Attachments: ci_summary.html, result_details.tar.gz > > > Current Accord functionality requires TCM to be able to provide cluster > metadata for an arbitrary epoch. Unfortunately, epochs are not always > available locally especially on bootstrapping non-CMS nodes. For this, we > need to reconstruct from the log. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19849) Test Failure: org.apache.cassandra.tcm.sequences.ProgressBarrierTest.testProgressBarrier
[
https://issues.apache.org/jira/browse/CASSANDRA-19849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875879#comment-17875879
]
Marcus Eriksson commented on CASSANDRA-19849:
-
+1
> Test Failure:
> org.apache.cassandra.tcm.sequences.ProgressBarrierTest.testProgressBarrier
>
>
> Key: CASSANDRA-19849
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19849
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Alex Petrov
>Priority: Normal
> Fix For: 5.x
>
> Attachments: ci_summary-1.html, result_details.tar-1.gz
>
>
> Seen on current trunk here:
> https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2726/workflows/2d5c888b-d5b8-4f72-9fcb-9e7ae0887940/jobs/61321/tests
> {code:java}
> junit.framework.AssertionFailedError: Should have collected at least 15 nodes
> but got 14.
> RF: NtsReplicationFactor{map={datacenter1=5, datacenter2=5, datacenter3=5}}
> Replicas: [/127.0.0.1:7012, /127.0.0.2:7012, /127.0.0.3:7012,
> /127.0.0.4:7012, /127.0.0.5:7012, /127.0.0.6:7012, /127.0.0.7:7012,
> /127.0.0.8:7012, /127.0.0.9:7012, /127.0.0.10:7012, /127.0.0.11:7012,
> /127.0.0.12:7012, /127.0.0.13:7012, /127.0.0.14:7012]
> Nodes: [/127.0.0.1:7012, /127.0.0.2:7012, /127.0.0.3:7012, /127.0.0.4:7012,
> /127.0.0.5:7012, /127.0.0.6:7012, /127.0.0.7:7012, /127.0.0.8:7012,
> /127.0.0.9:7012, /127.0.0.10:7012, /127.0.0.11:7012, /127.0.0.12:7012,
> /127.0.0.13:7012, /127.0.0.14:7012]
> at
> org.apache.cassandra.tcm.sequences.ProgressBarrierTest.testProgressBarrier(ProgressBarrierTest.java:176)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19845) Handle existing tables with non-expected table ids
[
https://issues.apache.org/jira/browse/CASSANDRA-19845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875446#comment-17875446
]
Marcus Eriksson commented on CASSANDRA-19845:
-
ci looks alright, filing a ticket for {{testProgressBarrier}} as I've seen that
on other branches, the rest of the failures seem to be flaky/timeouts
> Handle existing tables with non-expected table ids
> --
>
> Key: CASSANDRA-19845
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19845
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> On upgrade we merge the existing tables with the pre-defined ones, but we
> only check if the tableid exists, we should also check the name of the table
> since the id can be defined by the user.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19845) Handle existing tables with non-expected table ids
[ https://issues.apache.org/jira/browse/CASSANDRA-19845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19845: Attachment: ci_summary.html > Handle existing tables with non-expected table ids > -- > > Key: CASSANDRA-19845 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19845 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 5.x > > Attachments: ci_summary.html > > Time Spent: 10m > Remaining Estimate: 0h > > On upgrade we merge the existing tables with the pre-defined ones, but we > only check if the tableid exists, we should also check the name of the table > since the id can be defined by the user. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19768) nodetool assassinate of a CMS voting member should be allowed and should remove it from the CMS group
[
https://issues.apache.org/jira/browse/CASSANDRA-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19768:
Attachment: ci_summary.html
> nodetool assassinate of a CMS voting member should be allowed and should
> remove it from the CMS group
> -
>
> Key: CASSANDRA-19768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19768
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> nodetool assassinate is a dangerous command but is needed when the node to be
> removed really can’t be accessed anymore (such as host failures). But when
> the node to be removed is a member of CMS, we block this action with the
> following error
> {code}
> Can not commit transformation: "INVALID"(Rejecting this plan as the node
> NodeId{id=3} is still a part of CMS.).
> {code}
> If the node in question is not up, and we call nodetool assassinate, we
> should then try to remove that node from the CMS membership group
> Steps to repo
> * Start 4 node cluster
> * nodetool cms reconfigure 3
> * targetNode =
> * stop targetNode
> * nodetool assassinate targetNode
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19768) nodetool assassinate of a CMS voting member should be allowed and should remove it from the CMS group
[
https://issues.apache.org/jira/browse/CASSANDRA-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19768:
Attachment: (was: ci_summary.html)
> nodetool assassinate of a CMS voting member should be allowed and should
> remove it from the CMS group
> -
>
> Key: CASSANDRA-19768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19768
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> nodetool assassinate is a dangerous command but is needed when the node to be
> removed really can’t be accessed anymore (such as host failures). But when
> the node to be removed is a member of CMS, we block this action with the
> following error
> {code}
> Can not commit transformation: "INVALID"(Rejecting this plan as the node
> NodeId{id=3} is still a part of CMS.).
> {code}
> If the node in question is not up, and we call nodetool assassinate, we
> should then try to remove that node from the CMS membership group
> Steps to repo
> * Start 4 node cluster
> * nodetool cms reconfigure 3
> * targetNode =
> * stop targetNode
> * nodetool assassinate targetNode
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19846) Allow looking up local tables in nodetool getendpoints
[
https://issues.apache.org/jira/browse/CASSANDRA-19846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19846:
Bug Category: Parent values: Degradation(12984)Level 1 values: Other
Exception(12998)
Complexity: Low Hanging Fruit
Discovered By: Adhoc Test
Fix Version/s: 5.x
Reviewers: Sam Tunnicliffe
Severity: Low
Status: Open (was: Triage Needed)
> Allow looking up local tables in nodetool getendpoints
> --
>
> Key: CASSANDRA-19846
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19846
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In versions before 5.1 we allow looking up the endpoints for local tables
> using {{nodetool getendpoints}} - we only return the local node, but some
> scripts might depend on this so we should support it in 5.1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19846) Allow looking up local tables in nodetool getendpoints
[
https://issues.apache.org/jira/browse/CASSANDRA-19846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19846:
Test and Documentation Plan: ci run
Status: Patch Available (was: Open)
> Allow looking up local tables in nodetool getendpoints
> --
>
> Key: CASSANDRA-19846
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19846
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In versions before 5.1 we allow looking up the endpoints for local tables
> using {{nodetool getendpoints}} - we only return the local node, but some
> scripts might depend on this so we should support it in 5.1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19846) Allow looking up local tables in nodetool getendpoints
Marcus Eriksson created CASSANDRA-19846:
---
Summary: Allow looking up local tables in nodetool getendpoints
Key: CASSANDRA-19846
URL: https://issues.apache.org/jira/browse/CASSANDRA-19846
Project: Cassandra
Issue Type: Bug
Components: Transactional Cluster Metadata
Reporter: Marcus Eriksson
Assignee: Marcus Eriksson
In versions before 5.1 we allow looking up the endpoints for local tables using
{{nodetool getendpoints}} - we only return the local node, but some scripts
might depend on this so we should support it in 5.1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19845) Handle existing tables with non-expected table ids
[ https://issues.apache.org/jira/browse/CASSANDRA-19845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19845: Bug Category: Parent values: Degradation(12984)Level 1 values: Other Exception(12998) Complexity: Low Hanging Fruit Discovered By: Adhoc Test Fix Version/s: 5.x Reviewers: Sam Tunnicliffe Severity: Normal Status: Open (was: Triage Needed) > Handle existing tables with non-expected table ids > -- > > Key: CASSANDRA-19845 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19845 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > On upgrade we merge the existing tables with the pre-defined ones, but we > only check if the tableid exists, we should also check the name of the table > since the id can be defined by the user. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19845) Handle existing tables with non-expected table ids
[ https://issues.apache.org/jira/browse/CASSANDRA-19845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19845: Test and Documentation Plan: ci run Status: Patch Available (was: Open) > Handle existing tables with non-expected table ids > -- > > Key: CASSANDRA-19845 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19845 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > On upgrade we merge the existing tables with the pre-defined ones, but we > only check if the tableid exists, we should also check the name of the table > since the id can be defined by the user. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19845) Handle existing tables with non-expected table ids
Marcus Eriksson created CASSANDRA-19845: --- Summary: Handle existing tables with non-expected table ids Key: CASSANDRA-19845 URL: https://issues.apache.org/jira/browse/CASSANDRA-19845 Project: Cassandra Issue Type: Bug Components: Transactional Cluster Metadata Reporter: Marcus Eriksson Assignee: Marcus Eriksson On upgrade we merge the existing tables with the pre-defined ones, but we only check if the tableid exists, we should also check the name of the table since the id can be defined by the user. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19768) nodetool assassinate of a CMS voting member should be allowed and should remove it from the CMS group
[
https://issues.apache.org/jira/browse/CASSANDRA-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19768:
Attachment: ci_summary.html
> nodetool assassinate of a CMS voting member should be allowed and should
> remove it from the CMS group
> -
>
> Key: CASSANDRA-19768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19768
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> nodetool assassinate is a dangerous command but is needed when the node to be
> removed really can’t be accessed anymore (such as host failures). But when
> the node to be removed is a member of CMS, we block this action with the
> following error
> {code}
> Can not commit transformation: "INVALID"(Rejecting this plan as the node
> NodeId{id=3} is still a part of CMS.).
> {code}
> If the node in question is not up, and we call nodetool assassinate, we
> should then try to remove that node from the CMS membership group
> Steps to repo
> * Start 4 node cluster
> * nodetool cms reconfigure 3
> * targetNode =
> * stop targetNode
> * nodetool assassinate targetNode
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19768) nodetool assassinate of a CMS voting member should be allowed and should remove it from the CMS group
[
https://issues.apache.org/jira/browse/CASSANDRA-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19768:
Attachment: (was: ci_summary.html)
> nodetool assassinate of a CMS voting member should be allowed and should
> remove it from the CMS group
> -
>
> Key: CASSANDRA-19768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19768
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> nodetool assassinate is a dangerous command but is needed when the node to be
> removed really can’t be accessed anymore (such as host failures). But when
> the node to be removed is a member of CMS, we block this action with the
> following error
> {code}
> Can not commit transformation: "INVALID"(Rejecting this plan as the node
> NodeId{id=3} is still a part of CMS.).
> {code}
> If the node in question is not up, and we call nodetool assassinate, we
> should then try to remove that node from the CMS membership group
> Steps to repo
> * Start 4 node cluster
> * nodetool cms reconfigure 3
> * targetNode =
> * stop targetNode
> * nodetool assassinate targetNode
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19803) Flakey test org.apache.cassandra.distributed.test.TransientRangeMovement2Test#testMoveForward
[
https://issues.apache.org/jira/browse/CASSANDRA-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19803:
Fix Version/s: 5.1
(was: 5.x)
Since Version: 5.1
Source Control Link:
https://github.com/apache/cassandra/commit/86a353b4436ee5d6794d4968dfde30ed6f791030
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
committed, thanks!
> Flakey test
> org.apache.cassandra.distributed.test.TransientRangeMovement2Test#testMoveForward
> -
>
> Key: CASSANDRA-19803
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19803
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.1
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> junit.framework.AssertionFailedError: SHOULD NOT BE ON NODE: 11 --
> [(16,30)]: [00, 02, 04, 06, 08, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20,
> 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 42, 44, 46, 48]
> at
> org.apache.cassandra.distributed.test.TransientRangeMovementTest.assertAllContained(TransientRangeMovementTest.java:231)
> at
> org.apache.cassandra.distributed.test.TransientRangeMovement2Test.testMoveForward(TransientRangeMovement2Test.java:143)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19804) Flakey test upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD#test_rolling_upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-19804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19804:
Fix Version/s: 5.1-alpha1
(was: 5.x)
Since Version: 5.0-alpha1
Source Control Link:
https://github.com/apache/cassandra/commit/9fb141ffcc26108f04a4faf6848ad6080ca4d481
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
committed, thanks!
> Flakey test
> upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD#test_rolling_upgrade
> -
>
> Key: CASSANDRA-19804
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19804
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary.html
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {code}
> ERRORS
>
> _ ERROR at teardown of
> TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD.test_rolling_upgrade _
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node3] 'ERROR [InternalResponseStage:3] 2024-07-26 04:35:12,345
> MessagingService.java:509 - Cannot send the message (from:/127.0.0.3:7000,
> type:FETCH_LOG verb:TCM_FETCH_PEER_LOG_REQ) to /127.0.0.1:7000, as messaging
> service is shutting down', [node3] 'ERROR [InternalResponseStage:4]
> 2024-07-26 04:35:27,412 MessagingService.java:509 - Cannot send the message
> (from:/127.0.0.3:7000, type:FETCH_LOG verb:TCM_FETCH_PEER_LOG_REQ) to
> /127.0.0.1:7000, as messaging service is shutting down']
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19803) Flakey test org.apache.cassandra.distributed.test.TransientRangeMovement2Test#testMoveForward
[
https://issues.apache.org/jira/browse/CASSANDRA-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19803:
Test and Documentation Plan: ci run
Status: Patch Available (was: Open)
we don't wait for move to finish before running cleanup
> Flakey test
> org.apache.cassandra.distributed.test.TransientRangeMovement2Test#testMoveForward
> -
>
> Key: CASSANDRA-19803
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19803
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> junit.framework.AssertionFailedError: SHOULD NOT BE ON NODE: 11 --
> [(16,30)]: [00, 02, 04, 06, 08, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20,
> 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 42, 44, 46, 48]
> at
> org.apache.cassandra.distributed.test.TransientRangeMovementTest.assertAllContained(TransientRangeMovementTest.java:231)
> at
> org.apache.cassandra.distributed.test.TransientRangeMovement2Test.testMoveForward(TransientRangeMovement2Test.java:143)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19803) Flakey test org.apache.cassandra.distributed.test.TransientRangeMovement2Test#testMoveForward
[
https://issues.apache.org/jira/browse/CASSANDRA-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19803:
Attachment: ci_summary.html
> Flakey test
> org.apache.cassandra.distributed.test.TransientRangeMovement2Test#testMoveForward
> -
>
> Key: CASSANDRA-19803
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19803
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> junit.framework.AssertionFailedError: SHOULD NOT BE ON NODE: 11 --
> [(16,30)]: [00, 02, 04, 06, 08, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20,
> 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 42, 44, 46, 48]
> at
> org.apache.cassandra.distributed.test.TransientRangeMovementTest.assertAllContained(TransientRangeMovementTest.java:231)
> at
> org.apache.cassandra.distributed.test.TransientRangeMovement2Test.testMoveForward(TransientRangeMovement2Test.java:143)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19794) NPE on Directory access during Memtable flush fails ShortPaxosSimulationTest
[
https://issues.apache.org/jira/browse/CASSANDRA-19794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869609#comment-17869609
]
Marcus Eriksson commented on CASSANDRA-19794:
-
+1 assuming clean CI (if that's even needed as this only touches test files,
verified it fixes the issue locally)
> NPE on Directory access during Memtable flush fails ShortPaxosSimulationTest
>
>
> Key: CASSANDRA-19794
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19794
> Project: Cassandra
> Issue Type: Bug
> Components: Test/burn, Transactional Cluster Metadata
>Reporter: Caleb Rackliffe
>Assignee: Alex Petrov
>Priority: Normal
> Fix For: 5.x
>
>
> Run {{ShortPaxosSimulationTest}} w/ the following arguments on trunk:
> {noformat}
> PaxosSimulationRunner.main(new String[] { "run", "-n", "3..6", "-t", "1000",
> "-c", "2", "--cluster-action-limit", "2", "-s", "30", "--seed",
> "0xe0247e19a75e3bba" });
> {noformat}
> You should see a failure, starting with...
> {noformat}
> [junit-timeout] WARN [OptionalTasks:1] node5 2024-07-22 15:46:00,210
> LegacyStateListener.java:158 - Token -6148914691236517205 changing ownership
> from /127.0.0.1:7012 to /127.0.0.6:7012
> [junit-timeout] WARN [OptionalTasks:1] node6 2024-07-22 15:46:00,259
> SystemKeyspace.java:1287 - Using stored Gossip Generation 1577894856 as it is
> greater than current system time 1577894855. See CASSANDRA-3654 if you
> experience problems
> [junit-timeout] WARN [OptionalTasks:1] node6 2024-07-22 15:46:00,277
> LegacyStateListener.java:158 - Token -6148914691236517205 changing ownership
> from /127.0.0.1:7012 to /127.0.0.6:7012
> [junit-timeout] ERROR [isolatedExecutor:3] node6 2024-07-22 15:46:00,469
> ReconfigureCMS.java:184 - Could not finish adding the node to the Cluster
> Metadata Service
> [junit-timeout] java.lang.IllegalStateException: Can not commit
> transformation: "SERVER_ERROR"(class java.lang.NullPointerException).
> [junit-timeout] at
> org.apache.cassandra.tcm.ClusterMetadataService.lambda$commit$6(ClusterMetadataService.java:491)
> [junit-timeout] at
> org.apache.cassandra.tcm.ClusterMetadataService.commit(ClusterMetadataService.java:535)
> [junit-timeout] at
> org.apache.cassandra.tcm.ClusterMetadataService.commit(ClusterMetadataService.java:488)
> [junit-timeout] at
> org.apache.cassandra.tcm.sequences.ReconfigureCMS.executeNext(ReconfigureCMS.java:179)
> [junit-timeout] at
> org.apache.cassandra.tcm.sequences.InProgressSequences.resume(InProgressSequences.java:200)
> [junit-timeout] at
> org.apache.cassandra.tcm.sequences.InProgressSequences.finishInProgressSequences(InProgressSequences.java:72)
> [junit-timeout] at
> org.apache.cassandra.tcm.ClusterMetadataService.reconfigureCMS(ClusterMetadataService.java:372)
> [junit-timeout] at
> org.apache.cassandra.tcm.ClusterMetadataService.ensureCMSPlacement(ClusterMetadataService.java:379)
> [junit-timeout] at
> org.apache.cassandra.tcm.sequences.BootstrapAndReplace.executeNext(BootstrapAndReplace.java:274)
> [junit-timeout] at
> org.apache.cassandra.simulator.cluster.OnClusterReplace$ExecuteNextStep.lambda$new$f5e64c00$1(OnClusterReplace.java:162)
> [junit-timeout] at
> org.apache.cassandra.distributed.api.IInvokableInstance.unsafeRunOnThisThread(IInvokableInstance.java:85)
> [junit-timeout] at
> org.apache.cassandra.simulator.systems.SimulatedActionTask.lambda$asSafeRunnable$0(SimulatedActionTask.java:83)
> [junit-timeout] at
> org.apache.cassandra.simulator.systems.SimulatedActionTask$1.run(SimulatedActionTask.java:93)
> [junit-timeout] at
> org.apache.cassandra.simulator.systems.InterceptingExecutor$InterceptingPooledExecutor$WaitingThread.lambda$new$1(InterceptingExecutor.java:318)
> [junit-timeout] at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> [junit-timeout] at java.base/java.lang.Thread.run(Thread.java:829)
> {noformat}
> ...and underneath that...
> {noformat}
> [junit-timeout] Thread[ScheduledTasks:1,5,node3]
> [junit-timeout] java.lang.NullPointerException
> [junit-timeout] at
> org.apache.cassandra.utils.btree.AbstractBTreeMap.get(AbstractBTreeMap.java:92)
> [junit-timeout] at
> org.apache.cassandra.tcm.membership.Directory.endpoint(Directory.java:312)
> [junit-timeout] at
> org.apache.cassandra.tcm.transformations.cms.AdvanceCMSReconfiguration.executeRemove(AdvanceCMSReconfiguration.java:242)
> [junit-timeout] at
> org.apache.cassandra.tcm.transformations.cms.AdvanceCMSReconfiguration.execute(AdvanceCMSReconfiguration.java:123)
> [junit-timeout] at
> org.apache.cassandra.tcm.sequences.ReconfigureCMS.ap
[jira] [Commented] (CASSANDRA-19803) Flakey test org.apache.cassandra.distributed.test.TransientRangeMovement2Test#testMoveForward
[
https://issues.apache.org/jira/browse/CASSANDRA-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869581#comment-17869581
]
Marcus Eriksson commented on CASSANDRA-19803:
-
error is the same as if cleanup isn't run at all - do you have full logs for
this?
> Flakey test
> org.apache.cassandra.distributed.test.TransientRangeMovement2Test#testMoveForward
> -
>
> Key: CASSANDRA-19803
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19803
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
>
> {code}
> junit.framework.AssertionFailedError: SHOULD NOT BE ON NODE: 11 --
> [(16,30)]: [00, 02, 04, 06, 08, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20,
> 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 42, 44, 46, 48]
> at
> org.apache.cassandra.distributed.test.TransientRangeMovementTest.assertAllContained(TransientRangeMovementTest.java:231)
> at
> org.apache.cassandra.distributed.test.TransientRangeMovement2Test.testMoveForward(TransientRangeMovement2Test.java:143)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-19803) Flakey test org.apache.cassandra.distributed.test.TransientRangeMovement2Test#testMoveForward
[
https://issues.apache.org/jira/browse/CASSANDRA-19803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson reassigned CASSANDRA-19803:
---
Assignee: Marcus Eriksson
> Flakey test
> org.apache.cassandra.distributed.test.TransientRangeMovement2Test#testMoveForward
> -
>
> Key: CASSANDRA-19803
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19803
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
>
> {code}
> junit.framework.AssertionFailedError: SHOULD NOT BE ON NODE: 11 --
> [(16,30)]: [00, 02, 04, 06, 08, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20,
> 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 42, 44, 46, 48]
> at
> org.apache.cassandra.distributed.test.TransientRangeMovementTest.assertAllContained(TransientRangeMovementTest.java:231)
> at
> org.apache.cassandra.distributed.test.TransientRangeMovement2Test.testMoveForward(TransientRangeMovement2Test.java:143)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19804) Flakey test upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD#test_rolling_upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-19804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19804:
Test and Documentation Plan: ci run
Status: Patch Available (was: Open)
> Flakey test
> upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD#test_rolling_upgrade
> -
>
> Key: CASSANDRA-19804
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19804
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> ERRORS
>
> _ ERROR at teardown of
> TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD.test_rolling_upgrade _
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node3] 'ERROR [InternalResponseStage:3] 2024-07-26 04:35:12,345
> MessagingService.java:509 - Cannot send the message (from:/127.0.0.3:7000,
> type:FETCH_LOG verb:TCM_FETCH_PEER_LOG_REQ) to /127.0.0.1:7000, as messaging
> service is shutting down', [node3] 'ERROR [InternalResponseStage:4]
> 2024-07-26 04:35:27,412 MessagingService.java:509 - Cannot send the message
> (from:/127.0.0.3:7000, type:FETCH_LOG verb:TCM_FETCH_PEER_LOG_REQ) to
> /127.0.0.1:7000, as messaging service is shutting down']
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19804) Flakey test upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD#test_rolling_upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-19804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19804:
Reviewers: Sam Tunnicliffe
> Flakey test
> upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD#test_rolling_upgrade
> -
>
> Key: CASSANDRA-19804
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19804
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> ERRORS
>
> _ ERROR at teardown of
> TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD.test_rolling_upgrade _
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node3] 'ERROR [InternalResponseStage:3] 2024-07-26 04:35:12,345
> MessagingService.java:509 - Cannot send the message (from:/127.0.0.3:7000,
> type:FETCH_LOG verb:TCM_FETCH_PEER_LOG_REQ) to /127.0.0.1:7000, as messaging
> service is shutting down', [node3] 'ERROR [InternalResponseStage:4]
> 2024-07-26 04:35:27,412 MessagingService.java:509 - Cannot send the message
> (from:/127.0.0.3:7000, type:FETCH_LOG verb:TCM_FETCH_PEER_LOG_REQ) to
> /127.0.0.1:7000, as messaging service is shutting down']
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19804) Flakey test upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD#test_rolling_upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-19804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19804:
Attachment: ci_summary.html
> Flakey test
> upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD#test_rolling_upgrade
> -
>
> Key: CASSANDRA-19804
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19804
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Attachments: ci_summary.html
>
>
> {code}
> ERRORS
>
> _ ERROR at teardown of
> TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD.test_rolling_upgrade _
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node3] 'ERROR [InternalResponseStage:3] 2024-07-26 04:35:12,345
> MessagingService.java:509 - Cannot send the message (from:/127.0.0.3:7000,
> type:FETCH_LOG verb:TCM_FETCH_PEER_LOG_REQ) to /127.0.0.1:7000, as messaging
> service is shutting down', [node3] 'ERROR [InternalResponseStage:4]
> 2024-07-26 04:35:27,412 MessagingService.java:509 - Cannot send the message
> (from:/127.0.0.3:7000, type:FETCH_LOG verb:TCM_FETCH_PEER_LOG_REQ) to
> /127.0.0.1:7000, as messaging service is shutting down']
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19768) nodetool assassinate of a CMS voting member should be allowed and should remove it from the CMS group
[
https://issues.apache.org/jira/browse/CASSANDRA-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19768:
Attachment: ci_summary.html
> nodetool assassinate of a CMS voting member should be allowed and should
> remove it from the CMS group
> -
>
> Key: CASSANDRA-19768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19768
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Attachments: ci_summary.html
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> nodetool assassinate is a dangerous command but is needed when the node to be
> removed really can’t be accessed anymore (such as host failures). But when
> the node to be removed is a member of CMS, we block this action with the
> following error
> {code}
> Can not commit transformation: "INVALID"(Rejecting this plan as the node
> NodeId{id=3} is still a part of CMS.).
> {code}
> If the node in question is not up, and we call nodetool assassinate, we
> should then try to remove that node from the CMS membership group
> Steps to repo
> * Start 4 node cluster
> * nodetool cms reconfigure 3
> * targetNode =
> * stop targetNode
> * nodetool assassinate targetNode
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19768) nodetool assassinate of a CMS voting member should be allowed and should remove it from the CMS group
[
https://issues.apache.org/jira/browse/CASSANDRA-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19768:
Reviewers: Sam Tunnicliffe
> nodetool assassinate of a CMS voting member should be allowed and should
> remove it from the CMS group
> -
>
> Key: CASSANDRA-19768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19768
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> nodetool assassinate is a dangerous command but is needed when the node to be
> removed really can’t be accessed anymore (such as host failures). But when
> the node to be removed is a member of CMS, we block this action with the
> following error
> {code}
> Can not commit transformation: "INVALID"(Rejecting this plan as the node
> NodeId{id=3} is still a part of CMS.).
> {code}
> If the node in question is not up, and we call nodetool assassinate, we
> should then try to remove that node from the CMS membership group
> Steps to repo
> * Start 4 node cluster
> * nodetool cms reconfigure 3
> * targetNode =
> * stop targetNode
> * nodetool assassinate targetNode
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19768) nodetool assassinate of a CMS voting member should be allowed and should remove it from the CMS group
[
https://issues.apache.org/jira/browse/CASSANDRA-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869543#comment-17869543
]
Marcus Eriksson commented on CASSANDRA-19768:
-
PR that removes the assassinated node from the cms before doing the operation
Should note that {{nodetool assassinate}} is now mostly included for API
compatibility with earlier versions - an operator should always be able to use
{{nodetool removenode}} in real clusters now.
> nodetool assassinate of a CMS voting member should be allowed and should
> remove it from the CMS group
> -
>
> Key: CASSANDRA-19768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19768
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> nodetool assassinate is a dangerous command but is needed when the node to be
> removed really can’t be accessed anymore (such as host failures). But when
> the node to be removed is a member of CMS, we block this action with the
> following error
> {code}
> Can not commit transformation: "INVALID"(Rejecting this plan as the node
> NodeId{id=3} is still a part of CMS.).
> {code}
> If the node in question is not up, and we call nodetool assassinate, we
> should then try to remove that node from the CMS membership group
> Steps to repo
> * Start 4 node cluster
> * nodetool cms reconfigure 3
> * targetNode =
> * stop targetNode
> * nodetool assassinate targetNode
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19768) nodetool assassinate of a CMS voting member should be allowed and should remove it from the CMS group
[
https://issues.apache.org/jira/browse/CASSANDRA-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19768:
Test and Documentation Plan: ci run
Status: Patch Available (was: Open)
> nodetool assassinate of a CMS voting member should be allowed and should
> remove it from the CMS group
> -
>
> Key: CASSANDRA-19768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19768
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> nodetool assassinate is a dangerous command but is needed when the node to be
> removed really can’t be accessed anymore (such as host failures). But when
> the node to be removed is a member of CMS, we block this action with the
> following error
> {code}
> Can not commit transformation: "INVALID"(Rejecting this plan as the node
> NodeId{id=3} is still a part of CMS.).
> {code}
> If the node in question is not up, and we call nodetool assassinate, we
> should then try to remove that node from the CMS membership group
> Steps to repo
> * Start 4 node cluster
> * nodetool cms reconfigure 3
> * targetNode =
> * stop targetNode
> * nodetool assassinate targetNode
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-19768) nodetool assassinate of a CMS voting member should be allowed and should remove it from the CMS group
[
https://issues.apache.org/jira/browse/CASSANDRA-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson reassigned CASSANDRA-19768:
---
Assignee: Marcus Eriksson (was: Sam Tunnicliffe)
> nodetool assassinate of a CMS voting member should be allowed and should
> remove it from the CMS group
> -
>
> Key: CASSANDRA-19768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19768
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
>
> nodetool assassinate is a dangerous command but is needed when the node to be
> removed really can’t be accessed anymore (such as host failures). But when
> the node to be removed is a member of CMS, we block this action with the
> following error
> {code}
> Can not commit transformation: "INVALID"(Rejecting this plan as the node
> NodeId{id=3} is still a part of CMS.).
> {code}
> If the node in question is not up, and we call nodetool assassinate, we
> should then try to remove that node from the CMS membership group
> Steps to repo
> * Start 4 node cluster
> * nodetool cms reconfigure 3
> * targetNode =
> * stop targetNode
> * nodetool assassinate targetNode
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19768) nodetool assassinate of a CMS voting member should be allowed and should remove it from the CMS group
[
https://issues.apache.org/jira/browse/CASSANDRA-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19768:
Severity: Normal (was: Critical)
> nodetool assassinate of a CMS voting member should be allowed and should
> remove it from the CMS group
> -
>
> Key: CASSANDRA-19768
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19768
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
>
> nodetool assassinate is a dangerous command but is needed when the node to be
> removed really can’t be accessed anymore (such as host failures). But when
> the node to be removed is a member of CMS, we block this action with the
> following error
> {code}
> Can not commit transformation: "INVALID"(Rejecting this plan as the node
> NodeId{id=3} is still a part of CMS.).
> {code}
> If the node in question is not up, and we call nodetool assassinate, we
> should then try to remove that node from the CMS membership group
> Steps to repo
> * Start 4 node cluster
> * nodetool cms reconfigure 3
> * targetNode =
> * stop targetNode
> * nodetool assassinate targetNode
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19804) Flakey test upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD#test_rolling_upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-19804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19804:
Severity: Normal (was: Critical)
> Flakey test
> upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD#test_rolling_upgrade
> -
>
> Key: CASSANDRA-19804
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19804
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
>
> {code}
> ERRORS
>
> _ ERROR at teardown of
> TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD.test_rolling_upgrade _
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node3] 'ERROR [InternalResponseStage:3] 2024-07-26 04:35:12,345
> MessagingService.java:509 - Cannot send the message (from:/127.0.0.3:7000,
> type:FETCH_LOG verb:TCM_FETCH_PEER_LOG_REQ) to /127.0.0.1:7000, as messaging
> service is shutting down', [node3] 'ERROR [InternalResponseStage:4]
> 2024-07-26 04:35:27,412 MessagingService.java:509 - Cannot send the message
> (from:/127.0.0.3:7000, type:FETCH_LOG verb:TCM_FETCH_PEER_LOG_REQ) to
> /127.0.0.1:7000, as messaging service is shutting down']
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-19804) Flakey test upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD#test_rolling_upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-19804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson reassigned CASSANDRA-19804:
---
Assignee: Marcus Eriksson
> Flakey test
> upgrade_tests.upgrade_through_versions_test.TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD#test_rolling_upgrade
> -
>
> Key: CASSANDRA-19804
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19804
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: David Capwell
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
>
> {code}
> ERRORS
>
> _ ERROR at teardown of
> TestProtoV3Upgrade_AllVersions_EndsAt_Trunk_HEAD.test_rolling_upgrade _
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node3] 'ERROR [InternalResponseStage:3] 2024-07-26 04:35:12,345
> MessagingService.java:509 - Cannot send the message (from:/127.0.0.3:7000,
> type:FETCH_LOG verb:TCM_FETCH_PEER_LOG_REQ) to /127.0.0.1:7000, as messaging
> service is shutting down', [node3] 'ERROR [InternalResponseStage:4]
> 2024-07-26 04:35:27,412 MessagingService.java:509 - Cannot send the message
> (from:/127.0.0.3:7000, type:FETCH_LOG verb:TCM_FETCH_PEER_LOG_REQ) to
> /127.0.0.1:7000, as messaging service is shutting down']
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19755) Coordinator read latency metrics are inflated for some queries
[ https://issues.apache.org/jira/browse/CASSANDRA-19755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863400#comment-17863400 ] Marcus Eriksson commented on CASSANDRA-19755: - +1 > Coordinator read latency metrics are inflated for some queries > -- > > Key: CASSANDRA-19755 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19755 > Project: Cassandra > Issue Type: Bug > Components: Observability/Metrics >Reporter: Sam Tunnicliffe >Assignee: Sam Tunnicliffe >Priority: Normal > Fix For: 4.1.x, 5.0-rc > > Attachments: ci_summary-4.1.html, ci_summary-5.0.html, > ci_summary-trunk.html > > > When a partition read is decomposed on the coordinator into multiple single > partition read queries, the latency metric captured in StorageProxy can be > artificially increased. > This primarily affects reads where paging and aggregates are used or where an > IN clause selects multiple partition keys. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19705) Reconfigure CMS after move/bootstrap/replacement
[
https://issues.apache.org/jira/browse/CASSANDRA-19705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19705:
Fix Version/s: 5.1-alpha1
(was: 5.x)
Source Control Link:
https://github.com/apache/cassandra/commit/cbe07fd57e3d94a1f2512fced3f38e69ad4b3eb2
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
committed, thanks!
> Reconfigure CMS after move/bootstrap/replacement
>
>
> Key: CASSANDRA-19705
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19705
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Membership
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.1-alpha1
>
> Attachments: ci_summary-1.html, ci_summary.html
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The CMS placement uses SimpleStrategy/NTS to decide where it is placed to
> make it easier to safely bounce a cluster using existing tools (with CMS
> placement {{dc1: 3, dc2: 3}} we will use the placements for min_token in a
> NetworkTopologyStrategy with the same replication setting).
> We need to reconfigure this after move/bootstrap/replacement though, since
> the placements might have changed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19704) UnsupportedOperationException is thrown when no space for LCS
[
https://issues.apache.org/jira/browse/CASSANDRA-19704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17861320#comment-17861320
]
Marcus Eriksson commented on CASSANDRA-19704:
-
I don't think we can check {{<= 1}} - we'd fail the assertion
[here|https://github.com/apache/cassandra/blob/be70c892b6c474d1d32eaba1864f1bdc3444f52b/src/java/org/apache/cassandra/db/compaction/CompactionTask.java#L390].
In {{LeveledCompactionTask}} during L0 -> L1 compactions we only remove
sstables from L0 so we could still have non-expired L1 sstables in the
transaction. We could probably cancel the L1 sstables from the transaction and
compact only the expired ones though.
+1 on the {{level == 0}} patch if we want the bug fixed and we can revisit and
improve later.
> UnsupportedOperationException is thrown when no space for LCS
> -
>
> Key: CASSANDRA-19704
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19704
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Compaction/LCS
>Reporter: Zhao Yang
>Assignee: Caleb Rackliffe
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
> Attachments: ci_summary-1.html, ci_summary-2.html, ci_summary-3.html,
> ci_summary.html
>
>
> In {{CompactionTask#buildCompactionCandidatesForAvailableDiskSpace}} with
> LCS, if node has limited disk space and can't remove any sstable from L0 or
> L1 in {{{}LeveledCompactionTask#reduceScopeForLimitedSpace{}}},
> {{LeveledCompactionTask#partialCompactionsAcceptable}} will throw
> {{UnsupportedOperationException}}.
> We should handle {{LeveledCompactionTask#partialCompactionsAcceptable}} more
> gracefully with {{return level <= 1}} or simply {{true}} since
> {{reduceScopeForLimitedSpace}} only removes sstable from L0 or L1.
> Related https://issues.apache.org/jira/browse/CASSANDRA-17272
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19705) Reconfigure CMS after move/bootstrap/replacement
[
https://issues.apache.org/jira/browse/CASSANDRA-19705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19705:
Attachment: ci_summary-1.html
> Reconfigure CMS after move/bootstrap/replacement
>
>
> Key: CASSANDRA-19705
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19705
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Membership
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Attachments: ci_summary-1.html, ci_summary.html
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The CMS placement uses SimpleStrategy/NTS to decide where it is placed to
> make it easier to safely bounce a cluster using existing tools (with CMS
> placement {{dc1: 3, dc2: 3}} we will use the placements for min_token in a
> NetworkTopologyStrategy with the same replication setting).
> We need to reconfigure this after move/bootstrap/replacement though, since
> the placements might have changed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19705) Reconfigure CMS after move/bootstrap/replacement
[
https://issues.apache.org/jira/browse/CASSANDRA-19705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859716#comment-17859716
]
Marcus Eriksson commented on CASSANDRA-19705:
-
updated PR and new CI run attached
> Reconfigure CMS after move/bootstrap/replacement
>
>
> Key: CASSANDRA-19705
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19705
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Membership
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.x
>
> Attachments: ci_summary-1.html, ci_summary.html
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The CMS placement uses SimpleStrategy/NTS to decide where it is placed to
> make it easier to safely bounce a cluster using existing tools (with CMS
> placement {{dc1: 3, dc2: 3}} we will use the placements for min_token in a
> NetworkTopologyStrategy with the same replication setting).
> We need to reconfigure this after move/bootstrap/replacement though, since
> the placements might have changed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18961) Record commit timestamp - fix data loss when dropping and recreating a column
[ https://issues.apache.org/jira/browse/CASSANDRA-18961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-18961: Attachment: ci_summary.html > Record commit timestamp - fix data loss when dropping and recreating a column > - > > Key: CASSANDRA-18961 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18961 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Jacek Lewandowski >Assignee: Jacek Lewandowski >Priority: Normal > Attachments: ci_summary.html > > > Drop column transformation is replayed with the current timestamp so the > column appears to be dropped when the node starts regardless of its real drop > time. > As a solution to this problem I propose recording the timestamp of the > transformation, guaranteeing that it is always greater than a timestamp of > any previously committed transformation. Such timestamp is passed to the > execute method of the transformation so that the transformation code can make > use of it, increasing its "purity". -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18961) Record commit timestamp - fix data loss when dropping and recreating a column
[
https://issues.apache.org/jira/browse/CASSANDRA-18961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856407#comment-17856407
]
Marcus Eriksson commented on CASSANDRA-18961:
-
pushed an alternative patch
[here|https://github.com/apache/cassandra/pull/3380] which is less invasive -
it just stores the execution time in the {{AlterSchema}} transformation
> Record commit timestamp - fix data loss when dropping and recreating a column
> -
>
> Key: CASSANDRA-18961
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18961
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: Jacek Lewandowski
>Assignee: Jacek Lewandowski
>Priority: Normal
>
> Drop column transformation is replayed with the current timestamp so the
> column appears to be dropped when the node starts regardless of its real drop
> time.
> As a solution to this problem I propose recording the timestamp of the
> transformation, guaranteeing that it is always greater than a timestamp of
> any previously committed transformation. Such timestamp is passed to the
> execute method of the transformation so that the transformation code can make
> use of it, increasing its "purity".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19709) Always repair the full range when repairing system_cluster_metadata
[ https://issues.apache.org/jira/browse/CASSANDRA-19709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19709: Change Category: Operability Complexity: Low Hanging Fruit Fix Version/s: 5.1-alpha1 Reviewers: Marcus Eriksson Status: Open (was: Triage Needed) CI results in CASSANDRA-19713 > Always repair the full range when repairing system_cluster_metadata > --- > > Key: CASSANDRA-19709 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19709 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Sam Tunnicliffe >Priority: Normal > Fix For: 5.1-alpha1 > > > Since system_cluster_metadata uses a custom partitioner we need to repair the > full range whenever an operator uses -st and -et tokens to avoid breaking > existing repair automations. This is fine since the amount of data in this > keyspace should be small. > https://github.com/krummas/cassandra/commit/6ab8fcd1126f67b0117e1ee3c1fd1d4b40ac2362 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19710) Avoid ClassCastException when verifying tables with reversed partitioner
[ https://issues.apache.org/jira/browse/CASSANDRA-19710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19710: Bug Category: Parent values: Degradation(12984)Level 1 values: Other Exception(12998) Complexity: Low Hanging Fruit Discovered By: Adhoc Test Fix Version/s: 5.1-alpha1 Severity: Low Status: Open (was: Triage Needed) CI results in CASSANDRA-19713 > Avoid ClassCastException when verifying tables with reversed partitioner > > > Key: CASSANDRA-19710 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19710 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 5.1-alpha1 > > > A few TCM tables use a custom partitioner, this causes class cast exception > when running nodetool verify on them. > https://github.com/krummas/cassandra/commit/64897cb6382967f3e134752f5b9f223ff7daeb84 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19711) Ignore repair requests for system_cluster_metadata
[
https://issues.apache.org/jira/browse/CASSANDRA-19711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19711:
Bug Category: Parent values: Degradation(12984)Level 1 values: Other
Exception(12998)
Complexity: Low Hanging Fruit
Discovered By: Adhoc Test
Fix Version/s: 5.1-alpha1
Severity: Low
Status: Open (was: Triage Needed)
CI results in CASSANDRA-19713
> Ignore repair requests for system_cluster_metadata
> --
>
> Key: CASSANDRA-19711
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19711
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
> Fix For: 5.1-alpha1
>
>
> Since system_cluster_metadata is not replicated like other keyspaces we might
> break existing repair automation if a {{nodetool repair}} is run against a
> node not in the CMS. Just ignore the request if so.
> https://github.com/krummas/cassandra/commit/76437723acea35421ec5bf0412dcdee1411dcb6e
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19712) Fix gossip status after replacement
[ https://issues.apache.org/jira/browse/CASSANDRA-19712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19712: Bug Category: Parent values: Correctness(12982)Level 1 values: Transient Incorrect Response(12987) Complexity: Low Hanging Fruit Discovered By: Adhoc Test Fix Version/s: 5.1-alpha1 Severity: Low Status: Open (was: Triage Needed) CI results in CASSANDRA-19713 > Fix gossip status after replacement > --- > > Key: CASSANDRA-19712 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19712 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 5.1-alpha1 > > > Make sure gossip status is correct for replacement node. > https://github.com/krummas/cassandra/commit/2ed38a6273def17e6decbb8e74826b1995800d59 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19714) Use table-specific partitioners during Paxos repair
[
https://issues.apache.org/jira/browse/CASSANDRA-19714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855648#comment-17855648
]
Marcus Eriksson commented on CASSANDRA-19714:
-
CI results in CASSANDRA-19713
> Use table-specific partitioners during Paxos repair
> ---
>
> Key: CASSANDRA-19714
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19714
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
>Reporter: Sam Tunnicliffe
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-alpha1
>
>
> Partition keys in the \{{system.paxos}} table are derived from the key
> involved in the paxos transaction. Initially, it was safe to assume that the
> paxos table itself used the same partitioner as the tables in the
> transactions as all distributed keyspaces and tables were configured with the
> global partitioner. This is no longer true as the
> \{{system_cluster_metadata.distributed_metadata_log}} has its own custom
> partitioner.
> Likewise, \{{PaxosRepairHistory}} and the \{{system.paxos_repair_history}}
> table which makes that history durable map token ranges in the transacted
> tables to ballots. Prior to CASSANDRA-19482 it was safe to assume that these
> ranges contained tokens from the global partitioner but as this is no longer
> the case, we must use the specific partitioner for the table in question when
> working with ranges during paxos repair.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19713) Disallow denylisting keys in system_cluster_metadata
[ https://issues.apache.org/jira/browse/CASSANDRA-19713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855647#comment-17855647 ] Marcus Eriksson commented on CASSANDRA-19713: - To save a few rainforests I only ran CI on a branch including all of CASSANDRA-19709, CASSANDRA-19710, CASSANDRA-19711, CASSANDRA-19712, CASSANDRA-19713 and CASSANDRA-19714 as I hope to get these committed in a single batch > Disallow denylisting keys in system_cluster_metadata > > > Key: CASSANDRA-19713 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19713 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > > https://github.com/krummas/cassandra/commit/0435a9dbc382a428864b4b329e127882d9c18419 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19713) Disallow denylisting keys in system_cluster_metadata
[ https://issues.apache.org/jira/browse/CASSANDRA-19713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19713: Attachment: ci_summary.html > Disallow denylisting keys in system_cluster_metadata > > > Key: CASSANDRA-19713 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19713 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > > https://github.com/krummas/cassandra/commit/0435a9dbc382a428864b4b329e127882d9c18419 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19713) Disallow denylisting keys in system_cluster_metadata
[ https://issues.apache.org/jira/browse/CASSANDRA-19713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19713: Change Category: Operability Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > Disallow denylisting keys in system_cluster_metadata > > > Key: CASSANDRA-19713 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19713 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Attachments: ci_summary.html > > > https://github.com/krummas/cassandra/commit/0435a9dbc382a428864b4b329e127882d9c18419 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-19714) Use table-specific partitioners during Paxos repair
[
https://issues.apache.org/jira/browse/CASSANDRA-19714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855620#comment-17855620
]
Marcus Eriksson edited comment on CASSANDRA-19714 at 6/17/24 2:34 PM:
--
https://github.com/krummas/cassandra/commit/ed5032e3c524154f0b2f34489cd9819a9f5d8d0d
was (Author: krummas):
https://github.com/krummas/cassandra/commit/0435a9dbc382a428864b4b329e127882d9c18419
> Use table-specific partitioners during Paxos repair
> ---
>
> Key: CASSANDRA-19714
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19714
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
>Reporter: Sam Tunnicliffe
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-alpha1
>
>
> Partition keys in the \{{system.paxos}} table are derived from the key
> involved in the paxos transaction. Initially, it was safe to assume that the
> paxos table itself used the same partitioner as the tables in the
> transactions as all distributed keyspaces and tables were configured with the
> global partitioner. This is no longer true as the
> \{{system_cluster_metadata.distributed_metadata_log}} has its own custom
> partitioner.
> Likewise, \{{PaxosRepairHistory}} and the \{{system.paxos_repair_history}}
> table which makes that history durable map token ranges in the transacted
> tables to ballots. Prior to CASSANDRA-19482 it was safe to assume that these
> ranges contained tokens from the global partitioner but as this is no longer
> the case, we must use the specific partitioner for the table in question when
> working with ranges during paxos repair.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19714) Use table-specific partitioners during Paxos repair
[
https://issues.apache.org/jira/browse/CASSANDRA-19714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19714:
Change Category: Operability
Complexity: Normal
Component/s: Transactional Cluster Metadata
Fix Version/s: 5.1-alpha1
Reviewers: Marcus Eriksson
Assignee: Sam Tunnicliffe
Status: Open (was: Triage Needed)
https://github.com/krummas/cassandra/commit/0435a9dbc382a428864b4b329e127882d9c18419
> Use table-specific partitioners during Paxos repair
> ---
>
> Key: CASSANDRA-19714
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19714
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
>Reporter: Sam Tunnicliffe
>Assignee: Sam Tunnicliffe
>Priority: Normal
> Fix For: 5.1-alpha1
>
>
> Partition keys in the \{{system.paxos}} table are derived from the key
> involved in the paxos transaction. Initially, it was safe to assume that the
> paxos table itself used the same partitioner as the tables in the
> transactions as all distributed keyspaces and tables were configured with the
> global partitioner. This is no longer true as the
> \{{system_cluster_metadata.distributed_metadata_log}} has its own custom
> partitioner.
> Likewise, \{{PaxosRepairHistory}} and the \{{system.paxos_repair_history}}
> table which makes that history durable map token ranges in the transacted
> tables to ballots. Prior to CASSANDRA-19482 it was safe to assume that these
> ranges contained tokens from the global partitioner but as this is no longer
> the case, we must use the specific partitioner for the table in question when
> working with ranges during paxos repair.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19711) Ignore repair requests for system_cluster_metadata
[
https://issues.apache.org/jira/browse/CASSANDRA-19711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-19711:
Reviewers: Sam Tunnicliffe
> Ignore repair requests for system_cluster_metadata
> --
>
> Key: CASSANDRA-19711
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19711
> Project: Cassandra
> Issue Type: Bug
> Components: Transactional Cluster Metadata
>Reporter: Marcus Eriksson
>Assignee: Marcus Eriksson
>Priority: Normal
>
> Since system_cluster_metadata is not replicated like other keyspaces we might
> break existing repair automation if a {{nodetool repair}} is run against a
> node not in the CMS. Just ignore the request if so.
> https://github.com/krummas/cassandra/commit/76437723acea35421ec5bf0412dcdee1411dcb6e
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19710) Avoid ClassCastException when verifying tables with reversed partitioner
[ https://issues.apache.org/jira/browse/CASSANDRA-19710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19710: Reviewers: Sam Tunnicliffe > Avoid ClassCastException when verifying tables with reversed partitioner > > > Key: CASSANDRA-19710 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19710 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > > A few TCM tables use a custom partitioner, this causes class cast exception > when running nodetool verify on them. > https://github.com/krummas/cassandra/commit/64897cb6382967f3e134752f5b9f223ff7daeb84 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19712) Fix gossip status after replacement
[ https://issues.apache.org/jira/browse/CASSANDRA-19712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19712: Reviewers: Sam Tunnicliffe > Fix gossip status after replacement > --- > > Key: CASSANDRA-19712 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19712 > Project: Cassandra > Issue Type: Bug > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > > Make sure gossip status is correct for replacement node. > https://github.com/krummas/cassandra/commit/2ed38a6273def17e6decbb8e74826b1995800d59 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19713) Disallow denylisting keys in system_cluster_metadata
[ https://issues.apache.org/jira/browse/CASSANDRA-19713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-19713: Reviewers: Sam Tunnicliffe > Disallow denylisting keys in system_cluster_metadata > > > Key: CASSANDRA-19713 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19713 > Project: Cassandra > Issue Type: Improvement > Components: Transactional Cluster Metadata >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > > https://github.com/krummas/cassandra/commit/0435a9dbc382a428864b4b329e127882d9c18419 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19713) Disallow denylisting keys in system_cluster_metadata
Marcus Eriksson created CASSANDRA-19713: --- Summary: Disallow denylisting keys in system_cluster_metadata Key: CASSANDRA-19713 URL: https://issues.apache.org/jira/browse/CASSANDRA-19713 Project: Cassandra Issue Type: Improvement Components: Transactional Cluster Metadata Reporter: Marcus Eriksson Assignee: Marcus Eriksson https://github.com/krummas/cassandra/commit/0435a9dbc382a428864b4b329e127882d9c18419 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19712) Fix gossip status after replacement
Marcus Eriksson created CASSANDRA-19712: --- Summary: Fix gossip status after replacement Key: CASSANDRA-19712 URL: https://issues.apache.org/jira/browse/CASSANDRA-19712 Project: Cassandra Issue Type: Bug Components: Transactional Cluster Metadata Reporter: Marcus Eriksson Assignee: Marcus Eriksson Make sure gossip status is correct for replacement node. https://github.com/krummas/cassandra/commit/2ed38a6273def17e6decbb8e74826b1995800d59 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19711) Ignore repair requests for system_cluster_metadata
Marcus Eriksson created CASSANDRA-19711:
---
Summary: Ignore repair requests for system_cluster_metadata
Key: CASSANDRA-19711
URL: https://issues.apache.org/jira/browse/CASSANDRA-19711
Project: Cassandra
Issue Type: Bug
Components: Transactional Cluster Metadata
Reporter: Marcus Eriksson
Assignee: Marcus Eriksson
Since system_cluster_metadata is not replicated like other keyspaces we might
break existing repair automation if a {{nodetool repair}} is run against a node
not in the CMS. Just ignore the request if so.
https://github.com/krummas/cassandra/commit/76437723acea35421ec5bf0412dcdee1411dcb6e
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19710) Avoid ClassCastException when verifying tables with reversed partitioner
Marcus Eriksson created CASSANDRA-19710: --- Summary: Avoid ClassCastException when verifying tables with reversed partitioner Key: CASSANDRA-19710 URL: https://issues.apache.org/jira/browse/CASSANDRA-19710 Project: Cassandra Issue Type: Bug Components: Transactional Cluster Metadata Reporter: Marcus Eriksson Assignee: Marcus Eriksson A few TCM tables use a custom partitioner, this causes class cast exception when running nodetool verify on them. https://github.com/krummas/cassandra/commit/64897cb6382967f3e134752f5b9f223ff7daeb84 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
