[jira] [Commented] (CASSANDRA-12816) Rebuild failing while adding new datacenter
[
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658407#comment-15658407
]
Jai Bheemsen Rao Dhanwada commented on CASSANDRA-12816:
---
agree, but this limits someone to have all the keyspaces expanded to all the
regions.
if I have a use-case of having a keyspaces belonging different regions, I can't
make use of it.
> Rebuild failing while adding new datacenter
> ---
>
> Key: CASSANDRA-12816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12816
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Critical
>
> Hello All,
> I have single datacenter with 3 C* nodes and we are trying to expand the
> cluster to another region/DC. I am seeing the below error while doing a
> "nodetool rebuild -- name_of_existing_data_center" .
> {code:java}
> [user@machine ~]$ nodetool rebuild DC1
> nodetool: Unable to find sufficient sources for streaming range
> (-402178150752044282,-396707578307430827] in keyspace system_distributed
> See 'nodetool help' or 'nodetool help '.
> [user@machine ~]$
> {code}
> {code:java}
> user@cqlsh> SELECT * from system_schema.keyspaces where
> keyspace_name='system_distributed';
> keyspace_name | durable_writes | replication
> ---++-
> system_distributed | True | {'class':
> 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor': '3'}
> (1 rows)
> {code}
> To overcome this I have updated system_distributed keyspace to DC1:3 and
> DC2:3 with NetworkTopologyStrategy
> C* Version - 3.0.8
> Is this a bug that is introduced in 3.0.8 version of cassandra? as I haven't
> seen this issue with the older versions?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12816) Rebuild failing while adding new datacenter
[
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658149#comment-15658149
]
Jeremiah Jordan commented on CASSANDRA-12816:
-
bq. keyspace is present in us-west-2 but not in us-east.
Because of this you can't rebuild from us-east, as us-east doesn't have the
data necessary to rebuild correctly.
> Rebuild failing while adding new datacenter
> ---
>
> Key: CASSANDRA-12816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12816
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Critical
>
> Hello All,
> I have single datacenter with 3 C* nodes and we are trying to expand the
> cluster to another region/DC. I am seeing the below error while doing a
> "nodetool rebuild -- name_of_existing_data_center" .
> {code:java}
> [user@machine ~]$ nodetool rebuild DC1
> nodetool: Unable to find sufficient sources for streaming range
> (-402178150752044282,-396707578307430827] in keyspace system_distributed
> See 'nodetool help' or 'nodetool help '.
> [user@machine ~]$
> {code}
> {code:java}
> user@cqlsh> SELECT * from system_schema.keyspaces where
> keyspace_name='system_distributed';
> keyspace_name | durable_writes | replication
> ---++-
> system_distributed | True | {'class':
> 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor': '3'}
> (1 rows)
> {code}
> To overcome this I have updated system_distributed keyspace to DC1:3 and
> DC2:3 with NetworkTopologyStrategy
> C* Version - 3.0.8
> Is this a bug that is introduced in 3.0.8 version of cassandra? as I haven't
> seen this issue with the older versions?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12816) Rebuild failing while adding new datacenter
[
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605848#comment-15605848
]
Jeremiah Jordan commented on CASSANDRA-12816:
-
[~jaid] It is expected behavior, you should always switch all non LocalStrategy
keyspaces to NetworkTopologyStrategy.
> Rebuild failing while adding new datacenter
> ---
>
> Key: CASSANDRA-12816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12816
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Critical
>
> Hello All,
> I have single datacenter with 3 C* nodes and we are trying to expand the
> cluster to another region/DC. I am seeing the below error while doing a
> "nodetool rebuild -- name_of_existing_data_center" .
> {code:java}
> [user@machine ~]$ nodetool rebuild DC1
> nodetool: Unable to find sufficient sources for streaming range
> (-402178150752044282,-396707578307430827] in keyspace system_distributed
> See 'nodetool help' or 'nodetool help '.
> [user@machine ~]$
> {code}
> {code:java}
> user@cqlsh> SELECT * from system_schema.keyspaces where
> keyspace_name='system_distributed';
> keyspace_name | durable_writes | replication
> ---++-
> system_distributed | True | {'class':
> 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor': '3'}
> (1 rows)
> {code}
> To overcome this I have updated system_distributed keyspace to DC1:3 and
> DC2:3 with NetworkTopologyStrategy
> C* Version - 3.0.8
> Is this a bug that is introduced in 3.0.8 version of cassandra? as I haven't
> seen this issue with the older versions?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12816) Rebuild failing while adding new datacenter
[
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605806#comment-15605806
]
Jai Bheemsen Rao Dhanwada commented on CASSANDRA-12816:
---
[~jjordan] Agree, the work around is to add
-Dcassandra.consistent.rangemovement=false, but can you please help me
understand, is this a bug or expected behavior?
if this is the expected behavior, what is the action needed when expanding the
cluster to new DC? do I need to always use NetworkTopologyStrategy for all
non-LocalStrategy keyspaces like (system_distributed, systems_traces)?
> Rebuild failing while adding new datacenter
> ---
>
> Key: CASSANDRA-12816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12816
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Critical
>
> Hello All,
> I have single datacenter with 3 C* nodes and we are trying to expand the
> cluster to another region/DC. I am seeing the below error while doing a
> "nodetool rebuild -- name_of_existing_data_center" .
> {code:java}
> [user@machine ~]$ nodetool rebuild DC1
> nodetool: Unable to find sufficient sources for streaming range
> (-402178150752044282,-396707578307430827] in keyspace system_distributed
> See 'nodetool help' or 'nodetool help '.
> [user@machine ~]$
> {code}
> {code:java}
> user@cqlsh> SELECT * from system_schema.keyspaces where
> keyspace_name='system_distributed';
> keyspace_name | durable_writes | replication
> ---++-
> system_distributed | True | {'class':
> 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor': '3'}
> (1 rows)
> {code}
> To overcome this I have updated system_distributed keyspace to DC1:3 and
> DC2:3 with NetworkTopologyStrategy
> C* Version - 3.0.8
> Is this a bug that is introduced in 3.0.8 version of cassandra? as I haven't
> seen this issue with the older versions?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12816) Rebuild failing while adding new datacenter
[
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605631#comment-15605631
]
Jeremy Hanna commented on CASSANDRA-12816:
--
When [~jjordan] says "it will work", it won't fail. It will work like it did
before. That is, in the scenario where you set auto bootstrap to false when
you add the new datacenter nodes - since SimpleStrategy ignores datacenter
information, some of the new nodes will take ownership for some of the ranges
for the SimpleStrategy keyspace data. So a rebuild from the source datacenter
won't get the data that the new datacenter nodes own. So you won't have all of
the data from the SimpleStrategy keyspaces when everything is done. You can
make sure you don't replicate to the new datacenter in your NTS keyspace config
and do auto bootstrap = true and actually get the data when the new nodes take
ownership of those ranges. However, then you're still left with having to
migrate SimpleStrategy keyspaces to NetworkTopologyStrategy with two
datacenters anyway because you really don't want SimpleStrategy with more than
one datacenter.
This is why you always, *always* change to NetworkTopologyStrategy on all
non-LocalStrategy keyspaces before adding a second datacenter.
> Rebuild failing while adding new datacenter
> ---
>
> Key: CASSANDRA-12816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12816
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Critical
>
> Hello All,
> I have single datacenter with 3 C* nodes and we are trying to expand the
> cluster to another region/DC. I am seeing the below error while doing a
> "nodetool rebuild -- name_of_existing_data_center" .
> {code:java}
> [user@machine ~]$ nodetool rebuild DC1
> nodetool: Unable to find sufficient sources for streaming range
> (-402178150752044282,-396707578307430827] in keyspace system_distributed
> See 'nodetool help' or 'nodetool help '.
> [user@machine ~]$
> {code}
> {code:java}
> user@cqlsh> SELECT * from system_schema.keyspaces where
> keyspace_name='system_distributed';
> keyspace_name | durable_writes | replication
> ---++-
> system_distributed | True | {'class':
> 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor': '3'}
> (1 rows)
> {code}
> To overcome this I have updated system_distributed keyspace to DC1:3 and
> DC2:3 with NetworkTopologyStrategy
> C* Version - 3.0.8
> Is this a bug that is introduced in 3.0.8 version of cassandra? as I haven't
> seen this issue with the older versions?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12816) Rebuild failing while adding new datacenter
[
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605596#comment-15605596
]
Jeremiah Jordan commented on CASSANDRA-12816:
-
If you set:
{code}
-Dcassandra.consistent.rangemovement=false
{code}
Then it will work.
> Rebuild failing while adding new datacenter
> ---
>
> Key: CASSANDRA-12816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12816
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Critical
>
> Hello All,
> I have single datacenter with 3 C* nodes and we are trying to expand the
> cluster to another region/DC. I am seeing the below error while doing a
> "nodetool rebuild -- name_of_existing_data_center" .
> {code:java}
> [user@machine ~]$ nodetool rebuild DC1
> nodetool: Unable to find sufficient sources for streaming range
> (-402178150752044282,-396707578307430827] in keyspace system_distributed
> See 'nodetool help' or 'nodetool help '.
> [user@machine ~]$
> {code}
> {code:java}
> user@cqlsh> SELECT * from system_schema.keyspaces where
> keyspace_name='system_distributed';
> keyspace_name | durable_writes | replication
> ---++-
> system_distributed | True | {'class':
> 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor': '3'}
> (1 rows)
> {code}
> To overcome this I have updated system_distributed keyspace to DC1:3 and
> DC2:3 with NetworkTopologyStrategy
> C* Version - 3.0.8
> Is this a bug that is introduced in 3.0.8 version of cassandra? as I haven't
> seen this issue with the older versions?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12816) Rebuild failing while adding new datacenter
[
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15605525#comment-15605525
]
sai k potturi commented on CASSANDRA-12816:
---
[~jeromatron] : we did'nt happen to see the issue in any of our previous
versions of Cassandra. We for the first time observed it in 2.1.15. It was not
an issue in 2.1.12 nor 2.1.14. Just wanted to make sure it was not a bug.
> Rebuild failing while adding new datacenter
> ---
>
> Key: CASSANDRA-12816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12816
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Critical
>
> Hello All,
> I have single datacenter with 3 C* nodes and we are trying to expand the
> cluster to another region/DC. I am seeing the below error while doing a
> "nodetool rebuild -- name_of_existing_data_center" .
> {code:java}
> [user@machine ~]$ nodetool rebuild DC1
> nodetool: Unable to find sufficient sources for streaming range
> (-402178150752044282,-396707578307430827] in keyspace system_distributed
> See 'nodetool help' or 'nodetool help '.
> [user@machine ~]$
> {code}
> {code:java}
> user@cqlsh> SELECT * from system_schema.keyspaces where
> keyspace_name='system_distributed';
> keyspace_name | durable_writes | replication
> ---++-
> system_distributed | True | {'class':
> 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor': '3'}
> (1 rows)
> {code}
> To overcome this I have updated system_distributed keyspace to DC1:3 and
> DC2:3 with NetworkTopologyStrategy
> C* Version - 3.0.8
> Is this a bug that is introduced in 3.0.8 version of cassandra? as I haven't
> seen this issue with the older versions?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12816) Rebuild failing while adding new datacenter
[
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603565#comment-15603565
]
Jai Bheemsen Rao Dhanwada commented on CASSANDRA-12816:
---
This isn't correct. For example I have 10 Keyspaces in a cluster and I want to
have 5 Keyspaces in DC-1 and other 5 keyspaces in DC-1 and DC-2, in this is the
rebuild fails and I can't replicate the data to the newly added DC.
> Rebuild failing while adding new datacenter
> ---
>
> Key: CASSANDRA-12816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12816
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Critical
>
> Hello All,
> I have single datacenter with 3 C* nodes and we are trying to expand the
> cluster to another region/DC. I am seeing the below error while doing a
> "nodetool rebuild -- name_of_existing_data_center" .
> {code:java}
> [user@machine ~]$ nodetool rebuild DC1
> nodetool: Unable to find sufficient sources for streaming range
> (-402178150752044282,-396707578307430827] in keyspace system_distributed
> See 'nodetool help' or 'nodetool help '.
> [user@machine ~]$
> {code}
> {code:java}
> user@cqlsh> SELECT * from system_schema.keyspaces where
> keyspace_name='system_distributed';
> keyspace_name | durable_writes | replication
> ---++-
> system_distributed | True | {'class':
> 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor': '3'}
> (1 rows)
> {code}
> To overcome this I have updated system_distributed keyspace to DC1:3 and
> DC2:3 with NetworkTopologyStrategy
> C* Version - 3.0.8
> Is this a bug that is introduced in 3.0.8 version of cassandra? as I haven't
> seen this issue with the older versions?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12816) Rebuild failing while adding new datacenter
[
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603437#comment-15603437
]
Jeremy Hanna commented on CASSANDRA-12816:
--
If you change it to NetworkTopologyStrategy, the strategy is datacenter aware.
You are then able to specify the datacenter where the replicas will be stored.
If you aren't using SimpleStrategy and you bootstrap other nodes in another
datacenter, then try to rebuild, it will likely try to put data for those
keyspaces in the new datacenter. The rebuild operation requires a source
datacenter argument, so I wonder if it's failing because the source datacenter
in this case doesn't have all of the data according to the replication
strategies for those keyspaces. So I would always change to NTS before trying
rebuild.
> Rebuild failing while adding new datacenter
> ---
>
> Key: CASSANDRA-12816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12816
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Critical
>
> Hello All,
> I have single datacenter with 3 C* nodes and we are trying to expand the
> cluster to another region/DC. I am seeing the below error while doing a
> "nodetool rebuild -- name_of_existing_data_center" .
> {code:java}
> [user@machine ~]$ nodetool rebuild DC1
> nodetool: Unable to find sufficient sources for streaming range
> (-402178150752044282,-396707578307430827] in keyspace system_distributed
> See 'nodetool help' or 'nodetool help '.
> [user@machine ~]$
> {code}
> {code:java}
> user@cqlsh> SELECT * from system_schema.keyspaces where
> keyspace_name='system_distributed';
> keyspace_name | durable_writes | replication
> ---++-
> system_distributed | True | {'class':
> 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor': '3'}
> (1 rows)
> {code}
> To overcome this I have updated system_distributed keyspace to DC1:3 and
> DC2:3 with NetworkTopologyStrategy
> C* Version - 3.0.8
> Is this a bug that is introduced in 3.0.8 version of cassandra? as I haven't
> seen this issue with the older versions?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12816) Rebuild failing while adding new datacenter
[
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603306#comment-15603306
]
Jai Bheemsen Rao Dhanwada commented on CASSANDRA-12816:
---
system_traces and system_distributed are using SimpleStrategy, If I change it
to the NetworkTopologyStrategy, the rebuild operation works. any idea what are
the implications of changing them to NetworkTopologyStrategy?
> Rebuild failing while adding new datacenter
> ---
>
> Key: CASSANDRA-12816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12816
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Critical
>
> Hello All,
> I have single datacenter with 3 C* nodes and we are trying to expand the
> cluster to another region/DC. I am seeing the below error while doing a
> "nodetool rebuild -- name_of_existing_data_center" .
> {code:java}
> [user@machine ~]$ nodetool rebuild DC1
> nodetool: Unable to find sufficient sources for streaming range
> (-402178150752044282,-396707578307430827] in keyspace system_distributed
> See 'nodetool help' or 'nodetool help '.
> [user@machine ~]$
> {code}
> {code:java}
> user@cqlsh> SELECT * from system_schema.keyspaces where
> keyspace_name='system_distributed';
> keyspace_name | durable_writes | replication
> ---++-
> system_distributed | True | {'class':
> 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor': '3'}
> (1 rows)
> {code}
> To overcome this I have updated system_distributed keyspace to DC1:3 and
> DC2:3 with NetworkTopologyStrategy
> C* Version - 3.0.8
> Is this a bug that is introduced in 3.0.8 version of cassandra? as I haven't
> seen this issue with the older versions?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12816) Rebuild failing while adding new datacenter
[
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603275#comment-15603275
]
Jeremy Hanna commented on CASSANDRA-12816:
--
If it is using the LocalStrategy, don't change it. In fact I don't think you
can change it. If it's not using the local strategy, set it to
NetworkTopologyStrategy.
> Rebuild failing while adding new datacenter
> ---
>
> Key: CASSANDRA-12816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12816
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Critical
>
> Hello All,
> I have single datacenter with 3 C* nodes and we are trying to expand the
> cluster to another region/DC. I am seeing the below error while doing a
> "nodetool rebuild -- name_of_existing_data_center" .
> {code:java}
> [user@machine ~]$ nodetool rebuild DC1
> nodetool: Unable to find sufficient sources for streaming range
> (-402178150752044282,-396707578307430827] in keyspace system_distributed
> See 'nodetool help' or 'nodetool help '.
> [user@machine ~]$
> {code}
> {code:java}
> user@cqlsh> SELECT * from system_schema.keyspaces where
> keyspace_name='system_distributed';
> keyspace_name | durable_writes | replication
> ---++-
> system_distributed | True | {'class':
> 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor': '3'}
> (1 rows)
> {code}
> To overcome this I have updated system_distributed keyspace to DC1:3 and
> DC2:3 with NetworkTopologyStrategy
> C* Version - 3.0.8
> Is this a bug that is introduced in 3.0.8 version of cassandra? as I haven't
> seen this issue with the older versions?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12816) Rebuild failing while adding new datacenter
[
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603265#comment-15603265
]
Jai Bheemsen Rao Dhanwada commented on CASSANDRA-12816:
---
[~jeromatron] correct, but I am concerned about altering system level keyspaces
(system, systems_traces, system_distributed).
Do you know what is the impact (if any) of making system keyspaces to
NetworkTopologyStrategy ?
> Rebuild failing while adding new datacenter
> ---
>
> Key: CASSANDRA-12816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12816
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Critical
>
> Hello All,
> I have single datacenter with 3 C* nodes and we are trying to expand the
> cluster to another region/DC. I am seeing the below error while doing a
> "nodetool rebuild -- name_of_existing_data_center" .
> {code:java}
> [user@machine ~]$ nodetool rebuild DC1
> nodetool: Unable to find sufficient sources for streaming range
> (-402178150752044282,-396707578307430827] in keyspace system_distributed
> See 'nodetool help' or 'nodetool help '.
> [user@machine ~]$
> {code}
> {code:java}
> user@cqlsh> SELECT * from system_schema.keyspaces where
> keyspace_name='system_distributed';
> keyspace_name | durable_writes | replication
> ---++-
> system_distributed | True | {'class':
> 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor': '3'}
> (1 rows)
> {code}
> To overcome this I have updated system_distributed keyspace to DC1:3 and
> DC2:3 with NetworkTopologyStrategy
> C* Version - 3.0.8
> Is this a bug that is introduced in 3.0.8 version of cassandra? as I haven't
> seen this issue with the older versions?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12816) Rebuild failing while adding new datacenter
[
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603246#comment-15603246
]
Jeremy Hanna commented on CASSANDRA-12816:
--
fwiw, when going to multiple datacenters it is always advisable to make all
keyspaces NetworkTopologyStrategy to avoid confusion about where replicas are
stored. SimpleStrategy ignores datacenters.
> Rebuild failing while adding new datacenter
> ---
>
> Key: CASSANDRA-12816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12816
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Critical
>
> Hello All,
> I have single datacenter with 3 C* nodes and we are trying to expand the
> cluster to another region/DC. I am seeing the below error while doing a
> "nodetool rebuild -- name_of_existing_data_center" .
> {code:java}
> [user@machine ~]$ nodetool rebuild DC1
> nodetool: Unable to find sufficient sources for streaming range
> (-402178150752044282,-396707578307430827] in keyspace system_distributed
> See 'nodetool help' or 'nodetool help '.
> [user@machine ~]$
> {code}
> {code:java}
> user@cqlsh> SELECT * from system_schema.keyspaces where
> keyspace_name='system_distributed';
> keyspace_name | durable_writes | replication
> ---++-
> system_distributed | True | {'class':
> 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor': '3'}
> (1 rows)
> {code}
> To overcome this I have updated system_distributed keyspace to DC1:3 and
> DC2:3 with NetworkTopologyStrategy
> C* Version - 3.0.8
> Is this a bug that is introduced in 3.0.8 version of cassandra? as I haven't
> seen this issue with the older versions?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-12816) Rebuild failing while adding new datacenter
[
https://issues.apache.org/jira/browse/CASSANDRA-12816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603224#comment-15603224
]
sai k potturi commented on CASSANDRA-12816:
---
We've observed this in the older versions like 2.1.15 and 2.1.16 too.
If we happen to change the replication factor and strategy to
'network-topology', rebuild is successful. Will altering the replication
factor for system_traces have any effect on major upgrades?
> Rebuild failing while adding new datacenter
> ---
>
> Key: CASSANDRA-12816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12816
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jai Bheemsen Rao Dhanwada
>Priority: Critical
>
> Hello All,
> I have single datacenter with 3 C* nodes and we are trying to expand the
> cluster to another region/DC. I am seeing the below error while doing a
> "nodetool rebuild -- name_of_existing_data_center" .
> {code:java}
> [user@machine ~]$ nodetool rebuild DC1
> nodetool: Unable to find sufficient sources for streaming range
> (-402178150752044282,-396707578307430827] in keyspace system_distributed
> See 'nodetool help' or 'nodetool help '.
> [user@machine ~]$
> {code}
> {code:java}
> user@cqlsh> SELECT * from system_schema.keyspaces where
> keyspace_name='system_distributed';
> keyspace_name | durable_writes | replication
> ---++-
> system_distributed | True | {'class':
> 'org.apache.cassandra.locator.SimpleStrategy', 'replication_factor': '3'}
> (1 rows)
> {code}
> To overcome this I have updated system_distributed keyspace to DC1:3 and
> DC2:3 with NetworkTopologyStrategy
> C* Version - 3.0.8
> Is this a bug that is introduced in 3.0.8 version of cassandra? as I haven't
> seen this issue with the older versions?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
