[jira] [Commented] (CASSANDRA-4486) UnavailableException when setting up a keyspace without a replication factor
[ https://issues.apache.org/jira/browse/CASSANDRA-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13612016#comment-13612016 ] Jonathan Ellis commented on CASSANDRA-4486: --- I pasted in your example as-is and got Value inserted. Elapsed time: 46 msec(s). UnavailableException when setting up a keyspace without a replication factor Key: CASSANDRA-4486 URL: https://issues.apache.org/jira/browse/CASSANDRA-4486 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.0.10 Environment: ubuntu 12.04 Reporter: Steve Arch Priority: Minor We have a cassandra cluster of 4 nodes. When I use cassandra cli to set up a keyspace without explicitely setting a replication factor, trying to add a CF fails with an UnavailableException: [default@unknown] create keyspace foo; ae639ba0-d4b8-11e1--424d3d43a8df Waiting for schema agreement... schemas agree across the cluster [default@unknown] use foo; Authenticated to keyspace: foo [default@foo] create column family User with comparator = UTF8Type; b4608180-d4b8-11e1--424d3d43a8df Waiting for schema agreement... schemas agree across the cluster [default@foo] update column family User with ... column_metadata = ... [ ... {column_name: first, validation_class: UTF8Type}, ... {column_name: last, validation_class: UTF8Type}, ... {column_name: age, validation_class: UTF8Type, index_type: KEYS} ... ]; b70562c0-d4b8-11e1--424d3d43a8df Waiting for schema agreement... schemas agree across the cluster [default@foo] set User['jsmith']['first'] = 'John'; null UnavailableException() at org.apache.cassandra.thrift.Cassandra$insert_result.read(Cassandra.java:15206) at org.apache.cassandra.thrift.Cassandra$Client.recv_insert(Cassandra.java:858) at org.apache.cassandra.thrift.Cassandra$Client.insert(Cassandra.java:830) at org.apache.cassandra.cli.CliClient.executeSet(CliClient.java:901) at org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:218) at org.apache.cassandra.cli.CliMain.processStatementInteractive(CliMain.java:220) at org.apache.cassandra.cli.CliMain.main(CliMain.java:348) Either this should work fine (and no unavailableException shoud be thrown) or an exception should be thrown when I create the keyspace because I have set it up wrong. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4486) UnavailableException when setting up a keyspace without a replication factor
[ https://issues.apache.org/jira/browse/CASSANDRA-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428175#comment-13428175 ] Dave Brosius commented on CASSANDRA-4486: - except this one is easy to detect, the other not so much. UnavailableException when setting up a keyspace without a replication factor Key: CASSANDRA-4486 URL: https://issues.apache.org/jira/browse/CASSANDRA-4486 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.0.10 Environment: ubuntu 12.04 Reporter: Steve Arch Priority: Minor We have a cassandra cluster of 4 nodes. When I use cassandra cli to set up a keyspace without explicitely setting a replication factor, trying to add a CF fails with an UnavailableException: [default@unknown] create keyspace foo; ae639ba0-d4b8-11e1--424d3d43a8df Waiting for schema agreement... schemas agree across the cluster [default@unknown] use foo; Authenticated to keyspace: foo [default@foo] create column family User with comparator = UTF8Type; b4608180-d4b8-11e1--424d3d43a8df Waiting for schema agreement... schemas agree across the cluster [default@foo] update column family User with ... column_metadata = ... [ ... {column_name: first, validation_class: UTF8Type}, ... {column_name: last, validation_class: UTF8Type}, ... {column_name: age, validation_class: UTF8Type, index_type: KEYS} ... ]; b70562c0-d4b8-11e1--424d3d43a8df Waiting for schema agreement... schemas agree across the cluster [default@foo] set User['jsmith']['first'] = 'John'; null UnavailableException() at org.apache.cassandra.thrift.Cassandra$insert_result.read(Cassandra.java:15206) at org.apache.cassandra.thrift.Cassandra$Client.recv_insert(Cassandra.java:858) at org.apache.cassandra.thrift.Cassandra$Client.insert(Cassandra.java:830) at org.apache.cassandra.cli.CliClient.executeSet(CliClient.java:901) at org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:218) at org.apache.cassandra.cli.CliMain.processStatementInteractive(CliMain.java:220) at org.apache.cassandra.cli.CliMain.main(CliMain.java:348) Either this should work fine (and no unavailableException shoud be thrown) or an exception should be thrown when I create the keyspace because I have set it up wrong. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4486) UnavailableException when setting up a keyspace without a replication factor
[ https://issues.apache.org/jira/browse/CASSANDRA-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428187#comment-13428187 ] Jonathan Ellis commented on CASSANDRA-4486: --- That's not the point, the point is that it's legitimate to set up a zero-replication keyspace (this is common when adding a new datacenter) and change it later. In the meantime, it's correct to reject writes to it. UnavailableException when setting up a keyspace without a replication factor Key: CASSANDRA-4486 URL: https://issues.apache.org/jira/browse/CASSANDRA-4486 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.0.10 Environment: ubuntu 12.04 Reporter: Steve Arch Priority: Minor We have a cassandra cluster of 4 nodes. When I use cassandra cli to set up a keyspace without explicitely setting a replication factor, trying to add a CF fails with an UnavailableException: [default@unknown] create keyspace foo; ae639ba0-d4b8-11e1--424d3d43a8df Waiting for schema agreement... schemas agree across the cluster [default@unknown] use foo; Authenticated to keyspace: foo [default@foo] create column family User with comparator = UTF8Type; b4608180-d4b8-11e1--424d3d43a8df Waiting for schema agreement... schemas agree across the cluster [default@foo] update column family User with ... column_metadata = ... [ ... {column_name: first, validation_class: UTF8Type}, ... {column_name: last, validation_class: UTF8Type}, ... {column_name: age, validation_class: UTF8Type, index_type: KEYS} ... ]; b70562c0-d4b8-11e1--424d3d43a8df Waiting for schema agreement... schemas agree across the cluster [default@foo] set User['jsmith']['first'] = 'John'; null UnavailableException() at org.apache.cassandra.thrift.Cassandra$insert_result.read(Cassandra.java:15206) at org.apache.cassandra.thrift.Cassandra$Client.recv_insert(Cassandra.java:858) at org.apache.cassandra.thrift.Cassandra$Client.insert(Cassandra.java:830) at org.apache.cassandra.cli.CliClient.executeSet(CliClient.java:901) at org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:218) at org.apache.cassandra.cli.CliMain.processStatementInteractive(CliMain.java:220) at org.apache.cassandra.cli.CliMain.main(CliMain.java:348) Either this should work fine (and no unavailableException shoud be thrown) or an exception should be thrown when I create the keyspace because I have set it up wrong. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-4486) UnavailableException when setting up a keyspace without a replication factor
[ https://issues.apache.org/jira/browse/CASSANDRA-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428378#comment-13428378 ] paul cannon commented on CASSANDRA-4486: Why would this set up a zero-replication keyspace? My reading of the code says that the default config for a bare create keyspace foo in cassandra-cli is NTS with {datacenter1:1}. And this cluster is supposed to have 4 nodes. UnavailableException when setting up a keyspace without a replication factor Key: CASSANDRA-4486 URL: https://issues.apache.org/jira/browse/CASSANDRA-4486 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.0.10 Environment: ubuntu 12.04 Reporter: Steve Arch Priority: Minor We have a cassandra cluster of 4 nodes. When I use cassandra cli to set up a keyspace without explicitely setting a replication factor, trying to add a CF fails with an UnavailableException: [default@unknown] create keyspace foo; ae639ba0-d4b8-11e1--424d3d43a8df Waiting for schema agreement... schemas agree across the cluster [default@unknown] use foo; Authenticated to keyspace: foo [default@foo] create column family User with comparator = UTF8Type; b4608180-d4b8-11e1--424d3d43a8df Waiting for schema agreement... schemas agree across the cluster [default@foo] update column family User with ... column_metadata = ... [ ... {column_name: first, validation_class: UTF8Type}, ... {column_name: last, validation_class: UTF8Type}, ... {column_name: age, validation_class: UTF8Type, index_type: KEYS} ... ]; b70562c0-d4b8-11e1--424d3d43a8df Waiting for schema agreement... schemas agree across the cluster [default@foo] set User['jsmith']['first'] = 'John'; null UnavailableException() at org.apache.cassandra.thrift.Cassandra$insert_result.read(Cassandra.java:15206) at org.apache.cassandra.thrift.Cassandra$Client.recv_insert(Cassandra.java:858) at org.apache.cassandra.thrift.Cassandra$Client.insert(Cassandra.java:830) at org.apache.cassandra.cli.CliClient.executeSet(CliClient.java:901) at org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:218) at org.apache.cassandra.cli.CliMain.processStatementInteractive(CliMain.java:220) at org.apache.cassandra.cli.CliMain.main(CliMain.java:348) Either this should work fine (and no unavailableException shoud be thrown) or an exception should be thrown when I create the keyspace because I have set it up wrong. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira