peng xiao created CASSANDRA-11815:
-------------------------------------

             Summary: com.datastax.driver.core.exceptions.UnavailableException: 
Not enough replica available for query at consistency ONE (1 required but only 
0 alive)
                 Key: CASSANDRA-11815
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11815
             Project: Cassandra
          Issue Type: Bug
            Reporter: peng xiao
            Priority: Critical


Hi,
We are trying to to add a new Data Center as per the following link.
http://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_add_dc_to_cluster_t.html

The problem is that when I run the following command in the original cluster:

ALTER KEYSPACE carrierdata WITH replication = {'class': 
'NetworkTopologyStrategy', 'DC1':3,'DC2':3};

We will get the following error:

2016-05-17 19:38:32.920 ERROR 28583 --- 
[daed440b-2f19-48a5-8bad-77f7169bc32e-string] [io-11235-exec-4] 
c.e.c.s.s.filter.GlobalExceptionHandler  : 
com.datastax.driver.core.exceptions.UnavailableException: Not enough replica 
available for query at consistency ONE (1 required but only 0 alive)
        at 
com.datastax.driver.core.exceptions.UnavailableException.copy(UnavailableException.java:79)
        at 
com.datastax.driver.core.DefaultResultSetFuture.extractCauseFromExecutionException(DefaultResultSetFuture.java:269)
        at 
com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:183)
        at 
com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:52)
        at 
com.datastax.driver.mapping.MethodMapper.invoke(MethodMapper.java:148)
        at 
com.datastax.driver.mapping.AccessorInvocationHandler.invoke(AccessorInvocationHandler.java:65)
        at com.sun.proxy.$Proxy139.getAccounts(Unknown Source)
        at 
com.enniu.cloud.services.data.ecommerce.dao.cassandra.ECommerceDaoCassandraImpl.getECommerceSummaries(ECommerceDaoCassandraImpl.java:310)

Could you please advise?

Thanks,
Peng Xiao



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to