cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-9689) keyspace creation fails when one node in a cluster is down.
Date Tue, 30 Jun 2015 18:18:05 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-9689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Philip Thompson updated CASSANDRA-9689:
---------------------------------------
    Description: 
Here is the snapshot of the overall issue :

whiterabbit@whiterabbit:~/cassandra/bin$ ccm create 'demo2' -v binary:2.1.7 -n 3 -s -d 
Current cluster is now: demo2
whiterabbit@whiterabbit:~/cassandra/bin$ ccm list
  demo_1node
 *demo2
whiterabbit@whiterabbit:~/cassandra/bin$ ccm status
Cluster: 'demo2'
----------------
node1: UP
node3: UP
node2: UP
whiterabbit@whiterabbit:~/cassandra/bin$ ccm node2 nodetool version

ReleaseVersion: 2.1.7

whiterabbit@whiterabbit:~/cassandra/bin$ ccm node2 stop
whiterabbit@whiterabbit:~/cassandra/bin$ ccm status
Cluster: 'demo2'
----------------
node1: UP
node3: UP
node2: DOWN
whiterabbit@whiterabbit:~/cassandra/bin$ ccm node1 cqlsh
Connected to demo2 at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 2.1.7 | CQL spec 3.2.0 | Native protocol v3]
Use HELP for help.
cqlsh> describe keyspaces;

system_traces  system

cqlsh> create keyspace training with replication={'class':'SimpleStrategy','replication_factor':1};
OperationTimedOut: errors={}, last_host=127.0.0.1
cqlsh> create keyspace training with replication={'class':'SimpleStrategy','replication_factor':1};
AlreadyExists: Keyspace 'training' already exists
cqlsh> describe keyspaces;

system_traces  system

cqlsh> 


> keyspace creation fails when one node in a cluster is down.
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-9689
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9689
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Roopesh
>             Fix For: 2.1.x
>
>
> Here is the snapshot of the overall issue :
> whiterabbit@whiterabbit:~/cassandra/bin$ ccm create 'demo2' -v binary:2.1.7 -n 3 -s -d

> Current cluster is now: demo2
> whiterabbit@whiterabbit:~/cassandra/bin$ ccm list
>   demo_1node
>  *demo2
> whiterabbit@whiterabbit:~/cassandra/bin$ ccm status
> Cluster: 'demo2'
> ----------------
> node1: UP
> node3: UP
> node2: UP
> whiterabbit@whiterabbit:~/cassandra/bin$ ccm node2 nodetool version
> ReleaseVersion: 2.1.7
> whiterabbit@whiterabbit:~/cassandra/bin$ ccm node2 stop
> whiterabbit@whiterabbit:~/cassandra/bin$ ccm status
> Cluster: 'demo2'
> ----------------
> node1: UP
> node3: UP
> node2: DOWN
> whiterabbit@whiterabbit:~/cassandra/bin$ ccm node1 cqlsh
> Connected to demo2 at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 2.1.7 | CQL spec 3.2.0 | Native protocol v3]
> Use HELP for help.
> cqlsh> describe keyspaces;
> system_traces  system
> cqlsh> create keyspace training with replication={'class':'SimpleStrategy','replication_factor':1};
> OperationTimedOut: errors={}, last_host=127.0.0.1
> cqlsh> create keyspace training with replication={'class':'SimpleStrategy','replication_factor':1};
> AlreadyExists: Keyspace 'training' already exists
> cqlsh> describe keyspaces;
> system_traces  system
> cqlsh> 



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

Mime
View raw message