Thanks for the heads up - I'll take a look at the driver.
On Tue, Nov 19, 2013 at 9:57 AM, Sylvain Lebresne <sylv...@datastax.com> wrote: > 256 is clearly not a valid CL code. It's of course always possible that the > client sends something perfectly valid and the server interprets it badly > for some reason, but it's a lot more likely a priori that the driver just > sends something wrong. In any case, since as far as I know no-one has seen > that with any other driver, you'd probably want to track that down with the > gocql authors. > > -- > Sylvain > > > On Tue, Nov 19, 2013 at 2:13 AM, Ben Hood <0x6e6...@gmail.com> wrote: >> >> I'm not sure that this is entirely causal, but the error I was getting >> occurred when the batch size I was accumulating was greater than 130K, >> so by cutting the batch size down, I made the issue go away for now. >> Having a such a large batch size is probably not such a good idea, but >> I'm not really sure it that really the cause of this issue. >> >> On Tue, Nov 19, 2013 at 12:56 AM, Ben Hood <0x6e6...@gmail.com> wrote: >> > Hi, >> > >> > Using 2.0.2 with the gocql driver, I'm getting this intermittent error: >> > >> > "Unknown code 256 for a consistency level" >> > >> > Is this something that the server could be returning, or is this maybe >> > only a client side issue? >> > >> > Cheers, >> > >> > Ben > >
