/SchemaKeyspace.java#L922-L928 ) .
From: Suresh Babu Mallampati
Reply-To:
Date: Wednesday, October 18, 2017 at 8:49 PM
To:
Subject: Re: UTF8 error
Thanks Jeffery,
will consider upgrading to 3.0.15.
issue is happening again and again and it's across the nodes. when we do the
ro
mpletely failed, and simply replace it with itself.
>
> Also 3.0.9 has a lot of bugs, and you should strongly consider upgrading
> to 3.0.15 once you get past this issue.
>
>
>
>
>
> From: Suresh Babu Mallampati
> Reply-To:
> Date: Wednesday, October 18, 2017 at 8:19 P
that server completely failed, and simply replace it with itself.
Also 3.0.9 has a lot of bugs, and you should strongly consider upgrading to
3.0.15 once you get past this issue.
From: Suresh Babu Mallampati
Reply-To:
Date: Wednesday, October 18, 2017 at 8:19 PM
To:
Subject: Re: UTF8
Thanks Michael.
we don't have any data in the Column Famility.
we are getting the error after creating the schema and CF's using the cqlsh
to connect to cluster. node is going down and not able to connect it and
getting the above error.
Thanks,
Suresh
On Wed, Oct 18, 2017 at 10:44 PM, Michael S
On 10/18/2017 09:02 PM, Suresh Babu Mallampati wrote:
> cqlsh: Connection error: ('Unable to connect to any servers',
> {'127.0.0.1': UnicodeDecodeError('utf8', '\x00\x00\x00\xf0\x8f\x0e', 3,
> 5, 'unexpected end of data')})
This does appear to be invalid UTF-8, so the error is valid. Perhaps you
Using Cassandra 3.0.9 version
I am getting the below error:
cqlsh: Connection error: ('Unable to connect to any servers', {'127.0.0.1':
UnicodeDecodeError('utf8', '\x00\x00\x00\xf0\x8f\x0e', 3, 5, 'unexpected
end of data')})
ERROR [main] 2017-10-17 11:56:17,384 o.a.c.s.CassandraDaemon - Except
