Re: UTF8 error
If you can get into one of the nodes, SELECT table_name from
system_schema.tables¹ and see if any of the data looks corrupt (here¹s the
block of code executing, it¹s loading all of the tables by name -
https://github.com/apache/cassandra/blob/cassandra-3.0.9/src/java/org/apache
/cassandra/schema/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
rolling bounce also this issue is happening.
Thanks,
Suresh.
On Wed, Oct 18, 2017 at 11:33 PM, Jeffrey Jirsa wrote:
> Is it only one node, or all of them? The stack says it¹s in loading all of the
> other schema data from disk, so if it¹s only one instance in the cluster, you
> could probably recover by removing the schema, it¹ll boot and pull schema from
> the rest of the cluster. Alternatively, you could pretend like 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 error
>
> 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 Shuler
> wrote:
>> 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
>> could provide a method to reproduce, or you could just clean up that
>> data if you know the primary key(s)?
>>
>> Python agrees:
>>>>> >>> print('\x00\x00\x00\xf0\x8f\x0e'.decode('utf-8'))
>> Traceback (most recent call last):
>> File "", line 1, in
>> File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
>> return codecs.utf_8_decode(input, errors, True)
>> UnicodeDecodeError: 'utf8' codec can't decode bytes in position 3-4:
>> unexpected end of data
>>
>> From:
>> https://software.hixie.ch/utilities/cgi/unicode-decoder/utf8-decoder
>>
>>
>> Decoder output:
>>
>> Byte number 1 is decimal 0, hex 0x00, octal \000, binary
>>
>> U+
>> = NULL
>>
>>
>> Byte number 2 is decimal 0, hex 0x00, octal \000, binary
>>
>> U+
>> = NULL
>>
>>
>> Byte number 3 is decimal 0, hex 0x00, octal \000, binary
>>
>> U+
>> = NULL
>>
>>
>> Byte number 4 is decimal 240, hex 0xF0, octal \360, binary
>> This is the first byte of a 4 byte sequence.
>>
>> Byte number 5 is decimal 143, hex 0x8F, octal \217, binary 1000
>> This is continuation byte 1, expecting 2 more.
>>
>> Byte number 6 is decimal 14, hex 0x0E, octal \016, binary 1110
>> Previous UTF-8 multibyte sequence incomplete, earlier bytes dropped.
>>
>> U+000E
>> = SHIFT OUT
>> * known as LOCKING-SHIFT ONE in 8-bit environments
>>
>>
>> --
>> Kind regards,
>> Michael
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
>> For additional commands, e-mail: user-h...@cassandra.apache.org
>>
>
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 rolling bounce also this issue is happening.
Thanks,
Suresh.
On Wed, Oct 18, 2017 at 11:33 PM, Jeffrey Jirsa wrote:
> Is it only one node, or all of them? The stack says it’s in loading all of
> the other schema data from disk, so if it’s only one instance in the
> cluster, you could probably recover by removing the schema, it’ll boot and
> pull schema from the rest of the cluster. Alternatively, you could pretend
> like 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 error
>
> 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 Shuler
> wrote:
>
>> 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
>> could provide a method to reproduce, or you could just clean up that
>> data if you know the primary key(s)?
>>
>> Python agrees:
>> >>> print('\x00\x00\x00\xf0\x8f\x0e'.decode('utf-8'))
>> Traceback (most recent call last):
>> File "", line 1, in
>> File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
>> return codecs.utf_8_decode(input, errors, True)
>> UnicodeDecodeError: 'utf8' codec can't decode bytes in position 3-4:
>> unexpected end of data
>>
>> From:
>> https://software.hixie.ch/utilities/cgi/unicode-decoder/utf8-decoder
>>
>>
>> Decoder output:
>>
>> Byte number 1 is decimal 0, hex 0x00, octal \000, binary
>>
>> U+
>> = NULL
>>
>>
>> Byte number 2 is decimal 0, hex 0x00, octal \000, binary
>>
>> U+
>> = NULL
>>
>>
>> Byte number 3 is decimal 0, hex 0x00, octal \000, binary
>>
>> U+
>> = NULL
>>
>>
>> Byte number 4 is decimal 240, hex 0xF0, octal \360, binary
>> This is the first byte of a 4 byte sequence.
>>
>> Byte number 5 is decimal 143, hex 0x8F, octal \217, binary 1000
>> This is continuation byte 1, expecting 2 more.
>>
>> Byte number 6 is decimal 14, hex 0x0E, octal \016, binary 1110
>> Previous UTF-8 multibyte sequence incomplete, earlier bytes dropped.
>>
>> U+000E
>> = SHIFT OUT
>> * known as LOCKING-SHIFT ONE in 8-bit environments
>>
>>
>> --
>> Kind regards,
>> Michael
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
>> For additional commands, e-mail: user-h...@cassandra.apache.org
>>
>>
>
Re: UTF8 error
Is it only one node, or all of them? The stack says it¹s in loading all of
the other schema data from disk, so if it¹s only one instance in the
cluster, you could probably recover by removing the schema, it¹ll boot and
pull schema from the rest of the cluster. Alternatively, you could pretend
like 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 error
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 Shuler
wrote:
> 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
> could provide a method to reproduce, or you could just clean up that
> data if you know the primary key(s)?
>
> Python agrees:
>>>> >>> print('\x00\x00\x00\xf0\x8f\x0e'.decode('utf-8'))
> Traceback (most recent call last):
> File "", line 1, in
> File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
> return codecs.utf_8_decode(input, errors, True)
> UnicodeDecodeError: 'utf8' codec can't decode bytes in position 3-4:
> unexpected end of data
>
> From:
> https://software.hixie.ch/utilities/cgi/unicode-decoder/utf8-decoder
>
>
> Decoder output:
>
> Byte number 1 is decimal 0, hex 0x00, octal \000, binary
>
> U+
> = NULL
>
>
> Byte number 2 is decimal 0, hex 0x00, octal \000, binary
>
> U+
> = NULL
>
>
> Byte number 3 is decimal 0, hex 0x00, octal \000, binary
>
> U+
> = NULL
>
>
> Byte number 4 is decimal 240, hex 0xF0, octal \360, binary
> This is the first byte of a 4 byte sequence.
>
> Byte number 5 is decimal 143, hex 0x8F, octal \217, binary 1000
> This is continuation byte 1, expecting 2 more.
>
> Byte number 6 is decimal 14, hex 0x0E, octal \016, binary 1110
> Previous UTF-8 multibyte sequence incomplete, earlier bytes dropped.
>
> U+000E
> = SHIFT OUT
> * known as LOCKING-SHIFT ONE in 8-bit environments
>
>
> --
> Kind regards,
> Michael
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
Re: UTF8 error
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 Shuler
wrote:
> 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
> could provide a method to reproduce, or you could just clean up that
> data if you know the primary key(s)?
>
> Python agrees:
> >>> print('\x00\x00\x00\xf0\x8f\x0e'.decode('utf-8'))
> Traceback (most recent call last):
> File "", line 1, in
> File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
> return codecs.utf_8_decode(input, errors, True)
> UnicodeDecodeError: 'utf8' codec can't decode bytes in position 3-4:
> unexpected end of data
>
> From:
> https://software.hixie.ch/utilities/cgi/unicode-decoder/utf8-decoder
>
>
> Decoder output:
>
> Byte number 1 is decimal 0, hex 0x00, octal \000, binary
>
> U+
> = NULL
>
>
> Byte number 2 is decimal 0, hex 0x00, octal \000, binary
>
> U+
> = NULL
>
>
> Byte number 3 is decimal 0, hex 0x00, octal \000, binary
>
> U+
> = NULL
>
>
> Byte number 4 is decimal 240, hex 0xF0, octal \360, binary
> This is the first byte of a 4 byte sequence.
>
> Byte number 5 is decimal 143, hex 0x8F, octal \217, binary 1000
> This is continuation byte 1, expecting 2 more.
>
> Byte number 6 is decimal 14, hex 0x0E, octal \016, binary 1110
> Previous UTF-8 multibyte sequence incomplete, earlier bytes dropped.
>
> U+000E
> = SHIFT OUT
> * known as LOCKING-SHIFT ONE in 8-bit environments
>
>
> --
> Kind regards,
> Michael
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
>
Re: UTF8 error
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
could provide a method to reproduce, or you could just clean up that
data if you know the primary key(s)?
Python agrees:
>>> print('\x00\x00\x00\xf0\x8f\x0e'.decode('utf-8'))
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeDecodeError: 'utf8' codec can't decode bytes in position 3-4:
unexpected end of data
From:
https://software.hixie.ch/utilities/cgi/unicode-decoder/utf8-decoder
Decoder output:
Byte number 1 is decimal 0, hex 0x00, octal \000, binary
U+
= NULL
Byte number 2 is decimal 0, hex 0x00, octal \000, binary
U+
= NULL
Byte number 3 is decimal 0, hex 0x00, octal \000, binary
U+
= NULL
Byte number 4 is decimal 240, hex 0xF0, octal \360, binary
This is the first byte of a 4 byte sequence.
Byte number 5 is decimal 143, hex 0x8F, octal \217, binary 1000
This is continuation byte 1, expecting 2 more.
Byte number 6 is decimal 14, hex 0x0E, octal \016, binary 1110
Previous UTF-8 multibyte sequence incomplete, earlier bytes dropped.
U+000E
= SHIFT OUT
* known as LOCKING-SHIFT ONE in 8-bit environments
--
Kind regards,
Michael
-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org
UTF8 error
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 - Exception
encountered during startup
org.apache.cassandra.serializers.MarshalException: Invalid UTF-8 bytes
00f08f0e
at
org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:45)
at
org.apache.cassandra.serializers.AbstractTextSerializer.deserialize(AbstractTextSerializer.java:28)
at
org.apache.cassandra.db.marshal.AbstractType.compose(AbstractType.java:113)
at
org.apache.cassandra.cql3.UntypedResultSet$Row.getString(UntypedResultSet.java:267)
at
org.apache.cassandra.schema.SchemaKeyspace.fetchTables(SchemaKeyspace.java:928)
at
org.apache.cassandra.schema.SchemaKeyspace.fetchKeyspace(SchemaKeyspace.java:891)
at
org.apache.cassandra.schema.SchemaKeyspace.fetchKeyspacesWithout(SchemaKeyspace.java:868)
at
org.apache.cassandra.schema.SchemaKeyspace.fetchNonSystemKeyspaces(SchemaKeyspace.java:856)
at org.apache.cassandra.config.Schema.loadFromDisk(Schema.java:136)
at org.apache.cassandra.config.Schema.loadFromDisk(Schema.java:126)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:239)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:568)
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:696)
Thanks,
Suresh.
