[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cassandra-commits
Subject:    [jira] [Commented] (CASSANDRA-9689) keyspace creation fails when one node in a cluster is down.
From:       "Roopesh (JIRA)" <jira () apache ! org>
Date:       2015-06-30 18:25:04
Message-ID: JIRA.12841761.1435688130000.61391.1435688704681 () Atlassian ! JIRA
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/CASSANDRA-9689?page=com.atlassian.jira.plu \
gin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608800#comment-14608800 \
] 

Roopesh commented on CASSANDRA-9689:
------------------------------------

HI Philip, 

Here it goes :

cqlsh> quit
whiterabbit@whiterabbit:~/cassandra/bin$ ccm node1 nodetool describecluster

Cluster Information:
	Name: demo2
	Snitch: org.apache.cassandra.locator.DynamicEndpointSnitch
	Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
	Schema versions:
		5271b8e1-025c-301f-937b-89f79ecc4832: [127.0.0.1, 127.0.0.3]

		UNREACHABLE: [127.0.0.2]


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  training  system

cqlsh> 


Here i could see the "training" keyspacce showing up now. So, what is the issue that \
it showed the failure message earlier ? Can you help me with that.

> 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)


[prev in list] [next in list] [prev in thread] [next in thread]