On Thu, Jan 15, 2015 at 6:30 AM, Richard Dawe <rich.d...@messagesystems.com>
wrote:
>
> I thought it might be quorum consistency level, because of the because I
> was seeing with cqlsh. I was testing with ccm with C* 2.0.8, 3 nodes,
> vnodes enabled ("ccm create test -v 2.0.8 -n 3 --vnodes -s”). With all
> three nodes up, my schema operations were working fine. When I took down
> two nodes using “ccm node2 stop”, “ccm node3 stop”, I found that schema
> operations through “ccm node1 cqlsh” were failing like this:
>
> cqlsh> ALTER TABLE test.test3 ADD fred text;
> Unable to complete request: one or more nodes were unavailable.
>
> That’s the full output — I had enabled tracing, but only that error came
> back.
>
> After reading your reply, I went back and re-ran my tests with cqlsh,
> and it seems like the “one or more nodes were unavailable” may be due to
> cqlsh’s error handling.
>
> If I wait a bit, and re-run my schema operations, they work fine with
> only one node up. I can see in the tracing that it’s only talking to node1
> (127.0.0.1) to make the schema modifications.
>
> Is this a known issue in cqlsh? If it helps I can send the full
> command-line session log.
>
That Unavailable error may actually be from the tracing-related queries
failing (that's what I suspect, at least). Starting cqlsh with --debug
might show you a stacktrace in that case, but I'm not 100% sure.
--
Tyler Hobbs
DataStax <http://datastax.com/>
