[jira] [Commented] (CASSANDRA-15158) Wait for schema agreement rather then in flight schema requests when bootstrapping
[ https://issues.apache.org/jira/browse/CASSANDRA-15158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872871#comment-16872871 ] Ian Cleasby commented on CASSANDRA-15158: - HI [~michaelsembwever] just hoping to get a bit of love for this ticket. Patches can be found in the description above initially done by Vince. Any feedback would be great. > Wait for schema agreement rather then in flight schema requests when > bootstrapping > -- > > Key: CASSANDRA-15158 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15158 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Gossip >Reporter: Vincent White >Assignee: Ian Cleasby >Priority: Normal > > Currently when a node is bootstrapping we use a set of latches > (org.apache.cassandra.service.MigrationTask#inflightTasks) to keep track of > in-flight schema pull requests, and we don't proceed with > bootstrapping/stream until all the latches are released (or we timeout > waiting for each one). One issue with this is that if we have a large schema, > or the retrieval of the schema from the other nodes was unexpectedly slow > then we have no explicit check in place to ensure we have actually received a > schema before we proceed. > While it's possible to increase "migration_task_wait_in_seconds" to force the > node to wait on each latche longer, there are cases where this doesn't help > because the callbacks for the schema pull requests have expired off the > messaging service's callback map > (org.apache.cassandra.net.MessagingService#callbacks) after > request_timeout_in_ms (default 10 seconds) before the other nodes were able > to respond to the new node. > This patch checks for schema agreement between the bootstrapping node and the > rest of the live nodes before proceeding with bootstrapping. It also adds a > check to prevent the new node from flooding existing nodes with simultaneous > schema pull requests as can happen in large clusters. > Removing the latch system should also prevent new nodes in large clusters > getting stuck for extended amounts of time as they wait > `migration_task_wait_in_seconds` on each of the latches left orphaned by the > timed out callbacks. > > ||3.11|| > |[PoC|https://github.com/apache/cassandra/compare/cassandra-3.11...vincewhite:check_for_schema]| > |[dtest|https://github.com/apache/cassandra-dtest/compare/master...vincewhite:wait_for_schema_agreement]| > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-15158) Wait for schema agreement rather then in flight schema requests when bootstrapping
[ https://issues.apache.org/jira/browse/CASSANDRA-15158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Cleasby reassigned CASSANDRA-15158: --- Assignee: Ian Cleasby > Wait for schema agreement rather then in flight schema requests when > bootstrapping > -- > > Key: CASSANDRA-15158 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15158 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Gossip >Reporter: Vincent White >Assignee: Ian Cleasby >Priority: Normal > > Currently when a node is bootstrapping we use a set of latches > (org.apache.cassandra.service.MigrationTask#inflightTasks) to keep track of > in-flight schema pull requests, and we don't proceed with > bootstrapping/stream until all the latches are released (or we timeout > waiting for each one). One issue with this is that if we have a large schema, > or the retrieval of the schema from the other nodes was unexpectedly slow > then we have no explicit check in place to ensure we have actually received a > schema before we proceed. > While it's possible to increase "migration_task_wait_in_seconds" to force the > node to wait on each latche longer, there are cases where this doesn't help > because the callbacks for the schema pull requests have expired off the > messaging service's callback map > (org.apache.cassandra.net.MessagingService#callbacks) after > request_timeout_in_ms (default 10 seconds) before the other nodes were able > to respond to the new node. > This patch checks for schema agreement between the bootstrapping node and the > rest of the live nodes before proceeding with bootstrapping. It also adds a > check to prevent the new node from flooding existing nodes with simultaneous > schema pull requests as can happen in large clusters. > Removing the latch system should also prevent new nodes in large clusters > getting stuck for extended amounts of time as they wait > `migration_task_wait_in_seconds` on each of the latches left orphaned by the > timed out callbacks. > > ||3.11|| > |[PoC|https://github.com/apache/cassandra/compare/cassandra-3.11...vincewhite:check_for_schema]| > |[dtest|https://github.com/apache/cassandra-dtest/compare/master...vincewhite:wait_for_schema_agreement]| > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15182) cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input, errors, True):1:'ascii' codec can't encode character u'\u9ed1' in position 60: ordina
[
https://issues.apache.org/jira/browse/CASSANDRA-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-15182:
---
Status: Triage Needed (was: Awaiting Feedback)
> cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input,
> errors, True):1:'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
>
> Key: CASSANDRA-15182
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15182
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: gloCalHelp.com
>Priority: Normal
>
> I use cqlsh 5.0.1 with cassandra 3.11.3 with python2.7.13 in Centos 6.9.
> when I run this cql command: bin/cqlsh hadoop4 -u dba -p ** --debug
> -e "INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3
> (clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
> VALUES
> ('黑A00888D','2019-06-2509:57:19',0,,'',,,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
> ,796.0,2205,746,'null','null','null',0,'379');"
> I get the error message as below:
> Using CQL driver: '/home/cassandra/cas3.11.3/bin/../lib/cassandra-driver-internal-only-3.11.0-bb96859b.zip/cassandra-driver-3.11.0-bb96859b/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Using 'utf-8' encoding
> Using ssl: False
> Traceback (most recent call last):
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 926, in onecmd
> self.handle_statement(st, statementtext)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 966, in handle_statement
> return self.perform_statement(cqlruleset.cql_extract_orig(tokens, srcstr))
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1000, in
> perform_statement
> success, future = self.perform_simple_statement(stmt)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1053, in
> perform_simple_statement
> self.printerr(unicode(err.__class__.__name__) + u": " +
> err.message.decode(encoding='utf-8'))
> File "/usr/local/python27/lib/python2.7/encodings/utf_8.py", line 16, in
> decode
> return codecs.utf_8_decode(input, errors, True)
> UnicodeEncodeError: 'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
> this issue seems different with the select command issue on
> https://issues.apache.org/jira/browse/CASSANDRA-10875
> and other method to add "-*- coding: utf-8 -*- " in the head of cqlsh.py ,
> can anyone hurry up to teach me?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15182) cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input, errors, True):1:'ascii' codec can't encode character u'\u9ed1' in position 60:
[
https://issues.apache.org/jira/browse/CASSANDRA-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872865#comment-16872865
]
gloCalHelp.com edited comment on CASSANDRA-15182 at 6/26/19 2:03 AM:
-
Thanks Sir Michael, because the report error position is not correct, and
I don't know how to santize the insert sql, but the shorter one with a Chinese
character can be successfully inserted as below:
INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3 (clcph,dwsj,bc) VALUES
('黑A00888D','2019-06-25 09:57:19',0);", and my LANG environment is really this:
bash-4.1$ echo $LANG
en_US.UTF-8
Is there anyone who can tell me how to make cqlsh report the correct
position of wrong sql except using --debug variable?
was (Author: glocalhelp.com):
Thanks Sir Michael, because the report error position is not correct, and
I don't know how to santize the insert sql, but the shorter one with a Chinese
character can be successfully inserted as below:
INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3 (clcph,dwsj,bc) VALUES
('黑A00888D','2019-06-25 09:57:19',0);"
Is there anyone who can tell me how to make cqlsh report the correct
position of wrong sql except using --debug variable?
> cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input,
> errors, True):1:'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
>
> Key: CASSANDRA-15182
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15182
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: gloCalHelp.com
>Priority: Normal
>
> I use cqlsh 5.0.1 with cassandra 3.11.3 with python2.7.13 in Centos 6.9.
> when I run this cql command: bin/cqlsh hadoop4 -u dba -p ** --debug
> -e "INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3
> (clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
> VALUES
> ('黑A00888D','2019-06-2509:57:19',0,,'',,,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
> ,796.0,2205,746,'null','null','null',0,'379');"
> I get the error message as below:
> Using CQL driver: '/home/cassandra/cas3.11.3/bin/../lib/cassandra-driver-internal-only-3.11.0-bb96859b.zip/cassandra-driver-3.11.0-bb96859b/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Using 'utf-8' encoding
> Using ssl: False
> Traceback (most recent call last):
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 926, in onecmd
> self.handle_statement(st, statementtext)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 966, in handle_statement
> return self.perform_statement(cqlruleset.cql_extract_orig(tokens, srcstr))
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1000, in
> perform_statement
> success, future = self.perform_simple_statement(stmt)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1053, in
> perform_simple_statement
> self.printerr(unicode(err.__class__.__name__) + u": " +
> err.message.decode(encoding='utf-8'))
> File "/usr/local/python27/lib/python2.7/encodings/utf_8.py", line 16, in
> decode
> return codecs.utf_8_decode(input, errors, True)
> UnicodeEncodeError: 'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
> this issue seems different with the select command issue on
> https://issues.apache.org/jira/browse/CASSANDRA-10875
> and other method to add "-*- coding: utf-8 -*- " in the head of cqlsh.py ,
> can anyone hurry up to teach me?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15182) cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input, errors, True):1:'ascii' codec can't encode character u'\u9ed1' in position 60: ordi
[
https://issues.apache.org/jira/browse/CASSANDRA-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872865#comment-16872865
]
gloCalHelp.com commented on CASSANDRA-15182:
Thanks Sir Michael, because the report error position is not correct, and
I don't know how to santize the insert sql, but the shorter one with a Chinese
character can be successfully inserted as below:
INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3 (clcph,dwsj,bc) VALUES
('黑A00888D','2019-06-25 09:57:19',0);"
Is there anyone who can tell me how to make cqlsh report the correct
position of wrong sql except using --debug variable?
> cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input,
> errors, True):1:'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
>
> Key: CASSANDRA-15182
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15182
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: gloCalHelp.com
>Priority: Normal
>
> I use cqlsh 5.0.1 with cassandra 3.11.3 with python2.7.13 in Centos 6.9.
> when I run this cql command: bin/cqlsh hadoop4 -u dba -p ** --debug
> -e "INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3
> (clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
> VALUES
> ('黑A00888D','2019-06-2509:57:19',0,,'',,,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
> ,796.0,2205,746,'null','null','null',0,'379');"
> I get the error message as below:
> Using CQL driver: '/home/cassandra/cas3.11.3/bin/../lib/cassandra-driver-internal-only-3.11.0-bb96859b.zip/cassandra-driver-3.11.0-bb96859b/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Using 'utf-8' encoding
> Using ssl: False
> Traceback (most recent call last):
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 926, in onecmd
> self.handle_statement(st, statementtext)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 966, in handle_statement
> return self.perform_statement(cqlruleset.cql_extract_orig(tokens, srcstr))
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1000, in
> perform_statement
> success, future = self.perform_simple_statement(stmt)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1053, in
> perform_simple_statement
> self.printerr(unicode(err.__class__.__name__) + u": " +
> err.message.decode(encoding='utf-8'))
> File "/usr/local/python27/lib/python2.7/encodings/utf_8.py", line 16, in
> decode
> return codecs.utf_8_decode(input, errors, True)
> UnicodeEncodeError: 'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
> this issue seems different with the select command issue on
> https://issues.apache.org/jira/browse/CASSANDRA-10875
> and other method to add "-*- coding: utf-8 -*- " in the head of cqlsh.py ,
> can anyone hurry up to teach me?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15175) Evaluate 200 node, compression=on, encryption=all
[ https://issues.apache.org/jira/browse/CASSANDRA-15175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Lynch updated CASSANDRA-15175: - Attachment: trunk_vs_30x_LQ_64kcRPS_14kcWPS.png > Evaluate 200 node, compression=on, encryption=all > - > > Key: CASSANDRA-15175 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15175 > Project: Cassandra > Issue Type: Sub-task > Components: Test/benchmark >Reporter: Joseph Lynch >Assignee: Joseph Lynch >Priority: Normal > Attachments: 30x_14400cRPS-14400cWPS.svg, > 30x_LQ_21600cRPS-14400cWPS.svg, ShortbufferExceptions.png, > odd_netty_jdk_tls_cpu_usage.png, trunk_14400cRPS-14400cWPS.svg, > trunk_187000cRPS-14400cWPS.svg, trunk_187kcRPS_14kcWPS.png, > trunk_22000cRPS-14400cWPS-jdk.svg, trunk_22000cRPS-14400cWPS-openssl.svg, > trunk_220kcRPS_14kcWPS.png, trunk_252kcRPS-14kcWPS.png, > trunk_93500cRPS-14400cWPS.svg, trunk_LQ_14400cRPS-14400cWPS.svg, > trunk_LQ_21600cRPS-14400cWPS.svg, trunk_vs_30x_125kcRPS_14kcWPS.png, > trunk_vs_30x_14kRPS_14kcWPS_load.png, trunk_vs_30x_14kcRPS_14kcWPS.png, > trunk_vs_30x_14kcRPS_14kcWPS_schedstat_delays.png, > trunk_vs_30x_156kcRPS_14kcWPS.png, trunk_vs_30x_24kcRPS_14kcWPS.png, > trunk_vs_30x_24kcRPS_14kcWPS_load.png, trunk_vs_30x_31kcRPS_14kcWPS.png, > trunk_vs_30x_62kcRPS_14kcWPS.png, trunk_vs_30x_93kcRPS_14kcWPS.png, > trunk_vs_30x_LQ_14kcRPS_14kcWPS.png, trunk_vs_30x_LQ_21kcRPS_14kcWPS.png, > trunk_vs_30x_LQ_64kcRPS_14kcWPS.png, trunk_vs_30x_summary.png > > > Tracks evaluating a 192 node cluster with compression and encryption on. > Test setup at (reproduced below) > [https://docs.google.com/spreadsheets/d/1Vq_wC2q-rcG7UWim-t2leZZ4GgcuAjSREMFbG0QGy20/edit#gid=1336583053] > > |Test Setup| | > |Baseline|3.0.19 > @d7d00036| > |Candiate|trunk > @abb0e177| > | | | > |Workload| | > |Write size|4kb random| > |Read size|4kb random| > |Per Node Data|110GiB| > |Generator|ndbench| > |Key Distribution|Uniform| > |SSTable Compr|Off| > |Internode TLS|On (jdk)| > |Internode Compr|On| > |Compaction|LCS (320 MiB)| > |Repair|Off| > | | | > |Hardware| | > |Instance Type|i3.xlarge| > |Deployment|96 us-east-1, 96 eu-west-1| > |Region node count|96| > | | | > |OS Settings| | > |IO scheduler|kyber| > |Net qdisc|tc-fq| > |readahead|32kb| > |Java Version|OpenJDK 1.8.0_202 (Zulu)| > | | | -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15176) Fix PagingState deserialization when the state was serialized using protocol version different from current session's
[
https://issues.apache.org/jira/browse/CASSANDRA-15176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872606#comment-16872606
]
Blake Eggleston commented on CASSANDRA-15176:
-
+1
> Fix PagingState deserialization when the state was serialized using protocol
> version different from current session's
> -
>
> Key: CASSANDRA-15176
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15176
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Client
>Reporter: Aleksey Yeschenko
>Assignee: Aleksey Yeschenko
>Priority: Normal
>
> 3.0 and native protocol V4 introduced a change to how {{PagingState}} is
> serialized. Unfortunately that can break requests during upgrades: since
> paging states are opaque, it's possible for a client to receive a paging
> state encoded as V3 on a 2.1 node, and then send it to a 3.0 node on a V4
> session. The version of the current session will be used to deserialize the
> paging state, instead of the actual version used to serialize it, and the
> request will fail.
> This is obviously sub-optimal, but also avoidable. This JIRA fixes one half
> of the problem: 3.0 failing to deserialize 'mislabeled' paging states. We can
> do this by inspecting the byte buffer to verify if it's been indeed
> serialized with the protocol version used by the session, and if not, use the
> other method of deserialization.
> It should be noted that we list this as a 'known limitation' somewhere, but
> really this is an upgrade-blocking bug for some users of C*.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15182) cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input, errors, True):1:'ascii' codec can't encode character u'\u9ed1' in position 60: ordina
[
https://issues.apache.org/jira/browse/CASSANDRA-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-15182:
---
Status: Awaiting Feedback (was: Triage Needed)
> cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input,
> errors, True):1:'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
>
> Key: CASSANDRA-15182
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15182
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: gloCalHelp.com
>Priority: Normal
>
> I use cqlsh 5.0.1 with cassandra 3.11.3 with python2.7.13 in Centos 6.9.
> when I run this cql command: bin/cqlsh hadoop4 -u dba -p ** --debug
> -e "INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3
> (clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
> VALUES
> ('黑A00888D','2019-06-2509:57:19',0,,'',,,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
> ,796.0,2205,746,'null','null','null',0,'379');"
> I get the error message as below:
> Using CQL driver: '/home/cassandra/cas3.11.3/bin/../lib/cassandra-driver-internal-only-3.11.0-bb96859b.zip/cassandra-driver-3.11.0-bb96859b/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Using 'utf-8' encoding
> Using ssl: False
> Traceback (most recent call last):
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 926, in onecmd
> self.handle_statement(st, statementtext)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 966, in handle_statement
> return self.perform_statement(cqlruleset.cql_extract_orig(tokens, srcstr))
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1000, in
> perform_statement
> success, future = self.perform_simple_statement(stmt)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1053, in
> perform_simple_statement
> self.printerr(unicode(err.__class__.__name__) + u": " +
> err.message.decode(encoding='utf-8'))
> File "/usr/local/python27/lib/python2.7/encodings/utf_8.py", line 16, in
> decode
> return codecs.utf_8_decode(input, errors, True)
> UnicodeEncodeError: 'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
> this issue seems different with the select command issue on
> https://issues.apache.org/jira/browse/CASSANDRA-10875
> and other method to add "-*- coding: utf-8 -*- " in the head of cqlsh.py ,
> can anyone hurry up to teach me?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15182) cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input, errors, True):1:'ascii' codec can't encode character u'\u9ed1' in position 60: ordi
[
https://issues.apache.org/jira/browse/CASSANDRA-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872444#comment-16872444
]
Michael Shuler commented on CASSANDRA-15182:
(Edited description to remove auth.. (OP should change that))
What is the local {{$LANG}} environment?
Could you post a sanitized and/or simplified schema that reproduces this
problem?
{noformat}
(master)mshuler@hana:~/git/ccm$ echo $LANG
en_US.UTF-8
(master)mshuler@hana:~/git/ccm$ ./ccm create test
--install-dir=/home/mshuler/git/cassandra
Current cluster is now: test
(master)mshuler@hana:~/git/ccm$ ./ccm populate -n 1
(master)mshuler@hana:~/git/ccm$ ./ccm start
(master)mshuler@hana:~/git/ccm$ ./ccm node1 cqlsh
Connected to test at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 3.11.5-SNAPSHOT | CQL spec 3.4.4 | Native protocol v4]
Use HELP for help.
cqlsh> CREATE KEYSPACE test WITH replication = {'class': 'SimpleStrategy',
'replication_factor': 1};
cqlsh> CREATE TABLE test.scratch (a text, b text, PRIMARY KEY (a));
cqlsh> INSERT INTO test.scratch (a, b) VALUES ('黑A00888D', 'something');
cqlsh> SELECT * FROM test.scratch;
a | b
---+---
黑A00888D | something
(1 rows)
{noformat}
I seem to be able to INSERT and SELECT that character with my local
LANG=en_US.UTF-8 env. I believe python-2.7 was not available until RHEL/CentOS
7, so I suspect the local environment and python install may need a little
configuration? Just a guess.
> cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input,
> errors, True):1:'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
>
> Key: CASSANDRA-15182
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15182
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: gloCalHelp.com
>Priority: Normal
>
> I use cqlsh 5.0.1 with cassandra 3.11.3 with python2.7.13 in Centos 6.9.
> when I run this cql command: bin/cqlsh hadoop4 -u dba -p ** --debug
> -e "INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3
> (clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
> VALUES
> ('黑A00888D','2019-06-2509:57:19',0,,'',,,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
> ,796.0,2205,746,'null','null','null',0,'379');"
> I get the error message as below:
> Using CQL driver: '/home/cassandra/cas3.11.3/bin/../lib/cassandra-driver-internal-only-3.11.0-bb96859b.zip/cassandra-driver-3.11.0-bb96859b/cassandra/__init__.py'>
> Using connect timeout: 5 seconds
> Using 'utf-8' encoding
> Using ssl: False
> Traceback (most recent call last):
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 926, in onecmd
> self.handle_statement(st, statementtext)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 966, in handle_statement
> return self.perform_statement(cqlruleset.cql_extract_orig(tokens, srcstr))
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1000, in
> perform_statement
> success, future = self.perform_simple_statement(stmt)
> File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1053, in
> perform_simple_statement
> self.printerr(unicode(err.__class__.__name__) + u": " +
> err.message.decode(encoding='utf-8'))
> File "/usr/local/python27/lib/python2.7/encodings/utf_8.py", line 16, in
> decode
> return codecs.utf_8_decode(input, errors, True)
> UnicodeEncodeError: 'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
> this issue seems different with the select command issue on
> https://issues.apache.org/jira/browse/CASSANDRA-10875
> and other method to add "-*- coding: utf-8 -*- " in the head of cqlsh.py ,
> can anyone hurry up to teach me?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15182) cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input, errors, True):1:'ascii' codec can't encode character u'\u9ed1' in position 60: ordina
[
https://issues.apache.org/jira/browse/CASSANDRA-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-15182:
---
Description:
I use cqlsh 5.0.1 with cassandra 3.11.3 with python2.7.13 in Centos 6.9.
when I run this cql command: bin/cqlsh hadoop4 -u dba -p ** --debug -e
"INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3
(clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
VALUES
('黑A00888D','2019-06-2509:57:19',0,,'',,,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
,796.0,2205,746,'null','null','null',0,'379');"
I get the error message as below:
Using CQL driver:
Using connect timeout: 5 seconds
Using 'utf-8' encoding
Using ssl: False
Traceback (most recent call last):
File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 926, in onecmd
self.handle_statement(st, statementtext)
File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 966, in handle_statement
return self.perform_statement(cqlruleset.cql_extract_orig(tokens, srcstr))
File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1000, in perform_statement
success, future = self.perform_simple_statement(stmt)
File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1053, in
perform_simple_statement
self.printerr(unicode(err.__class__.__name__) + u": " +
err.message.decode(encoding='utf-8'))
File "/usr/local/python27/lib/python2.7/encodings/utf_8.py", line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeEncodeError: 'ascii' codec can't encode character u'\u9ed1' in position
60: ordinal not in range(128)
this issue seems different with the select command issue on
https://issues.apache.org/jira/browse/CASSANDRA-10875
and other method to add "-*- coding: utf-8 -*- " in the head of cqlsh.py , can
anyone hurry up to teach me?
was:
I use cqlsh 5.0.1 with cassandra 3.11.3 with python2.7.13 in Centos 6.9.
when I run this cql command: bin/cqlsh hadoop4 -u dba -p LinJiaXin858 --debug
-e "INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3
(clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
VALUES
('黑A00888D','2019-06-2509:57:19',0,,'',,,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
,796.0,2205,746,'null','null','null',0,'379');"
I get the error message as below:
Using CQL driver:
Using connect timeout: 5 seconds
Using 'utf-8' encoding
Using ssl: False
Traceback (most recent call last):
File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 926, in onecmd
self.handle_statement(st, statementtext)
File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 966, in handle_statement
return self.perform_statement(cqlruleset.cql_extract_orig(tokens, srcstr))
File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1000, in perform_statement
success, future = self.perform_simple_statement(stmt)
File "/home/cassandra/cas3.11.3/bin/cqlsh.py", line 1053, in
perform_simple_statement
self.printerr(unicode(err.__class__.__name__) + u": " +
err.message.decode(encoding='utf-8'))
File "/usr/local/python27/lib/python2.7/encodings/utf_8.py", line 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeEncodeError: 'ascii' codec can't encode character u'\u9ed1' in position
60: ordinal not in range(128)
this issue seems different with the select command issue on
https://issues.apache.org/jira/browse/CASSANDRA-10875
and other method to add "-*- coding: utf-8 -*- " in the head of cqlsh.py , can
anyone hurry up to teach me?
> cqlsh utf_8.py, line 16, in decode return codecs.utf_8_decode(input,
> errors, True):1:'ascii' codec can't encode character u'\u9ed1' in
> position 60: ordinal not in range(128)
>
>
> Key: CASSANDRA-15182
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15182
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: gloCalHelp.com
>Priority: Normal
>
> I use cqlsh 5.0.1 with cassandra 3.11.3 with python2.7.13 in Centos 6.9.
> when I run this cql command: bin/cqlsh hadoop4 -u dba -p ** --debug
> -e "INSERT INTO HYGL_JCSJ.hyjg_ods_yy_gps_novar3
> (clcph,dwsj,bc,blbs,cjbzh,ckryid,clid,clmc,ddfx,ddrq,fwj,gd,gdjd,gdwd,jsdlc,jszjl,jxzjl,sjid,sjsfzh,sjxm,sssd,xlmc)
> VALUES
> ('黑A00888D','2019-06-2509:57:19',0,,'',,,'379-7038',1434,'2019-06-25',275,0,126723690,45726990
> ,796.0,2205,746,'null','null','null',0,'379');"
> I get the error message as below:
> Using CQL driver: '/home/cassandra/cas3.11.3/bin/../lib/cassandra-driver-internal-only-3.11.0-bb96859b.zip/cassandra-driver-3.11.0-bb96859b/cassandra/__init__.py'>
> Using connect
[jira] [Updated] (CASSANDRA-15183) Not Return Any Error When Insert A Lacking Decimal Value
[ https://issues.apache.org/jira/browse/CASSANDRA-15183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Shuler updated CASSANDRA-15183: --- Status: Awaiting Feedback (was: Triage Needed) There is no attachment on this JIRA, nor a usable description of how to reproduce the problem. Needs more info, or close as incomplete. > Not Return Any Error When Insert A Lacking Decimal Value > > > Key: CASSANDRA-15183 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15183 > Project: Cassandra > Issue Type: Bug > Components: CQL/Syntax >Reporter: gloCalHelp.com >Priority: Normal > > when using cqlsh as the first command in the attachment, no any error message > return or report in syste.log or debug.log. > !NotReturnAnyErrorWhenInsertALackingDecimalValue.GIF! > Not Return Any Error When Insert A Lacking Decimal Value. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15183) Not Return Any Error When Insert A Lacking Decimal Value
gloCalHelp.com created CASSANDRA-15183: -- Summary: Not Return Any Error When Insert A Lacking Decimal Value Key: CASSANDRA-15183 URL: https://issues.apache.org/jira/browse/CASSANDRA-15183 Project: Cassandra Issue Type: Bug Components: CQL/Syntax Reporter: gloCalHelp.com when using cqlsh as the first command in the attachment, no any error message return or report in syste.log or debug.log. !NotReturnAnyErrorWhenInsertALackingDecimalValue.GIF! Not Return Any Error When Insert A Lacking Decimal Value. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13363) Fix racy read command serialization
[
https://issues.apache.org/jira/browse/CASSANDRA-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872252#comment-16872252
]
Zain Malik commented on CASSANDRA-13363:
Hi,
we are facing similar issue in cassandra 3.0.16 where this racy condition is
supposed to be fixed. In our case it is happening during bootstrap time
{noformat}
ERROR 19:38:22 [Stream #f1c709f0-9418-11e9-8599-931b65954728] Streaming error
occurred
java.lang.IndexOutOfBoundsException: Index: 2, Size: 2
at java.util.ArrayList.rangeCheck(ArrayList.java:657) ~[na:1.8.0_162]
at java.util.ArrayList.get(ArrayList.java:433) ~[na:1.8.0_162]
at
org.apache.cassandra.db.ClusteringPrefix$Serializer.deserializeValuesWithoutSize(ClusteringPrefix.java:346)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.db.RangeTombstone$Bound$Serializer.deserializeValues(RangeTombstone.java:212)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.db.RangeTombstone$Bound$Serializer.deserialize(RangeTombstone.java:202)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.db.rows.UnfilteredSerializer.deserializeOne(UnfilteredSerializer.java:407)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.db.rows.UnfilteredSerializer.deserialize(UnfilteredSerializer.java:373)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.io.sstable.SSTableSimpleIterator$CurrentFormatIterator.computeNext(SSTableSimpleIterator.java:87)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.io.sstable.SSTableSimpleIterator$CurrentFormatIterator.computeNext(SSTableSimpleIterator.java:65)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.streaming.StreamReader$StreamDeserializer.hasNext(StreamReader.java:263)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.db.transform.BaseRows.hasNext(BaseRows.java:129)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.db.ColumnIndex$Builder.build(ColumnIndex.java:111)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.db.ColumnIndex.writeAndBuildIndex(ColumnIndex.java:52)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.io.sstable.format.big.BigTableWriter.append(BigTableWriter.java:149)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.io.sstable.SimpleSSTableMultiWriter.append(SimpleSSTableMultiWriter.java:45)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.streaming.StreamReader.writePartition(StreamReader.java:172)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.streaming.compress.CompressedStreamReader.read(CompressedStreamReader.java:107)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.streaming.messages.IncomingFileMessage$1.deserialize(IncomingFileMessage.java:54)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.streaming.messages.IncomingFileMessage$1.deserialize(IncomingFileMessage.java:43)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:59)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.streaming.ConnectionHandler$IncomingMessageHandler.run(ConnectionHandler.java:294)
~[apache-cassandra-3.0.16.jar:3.0.16]
at
org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:79)
[apache-cassandra-3.0.16.jar:3.0.16]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_162]
{noformat}
This causes streaming errors and as a consequence the node stays in JOINING
state.
> Fix racy read command serialization
> ---
>
> Key: CASSANDRA-13363
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13363
> Project: Cassandra
> Issue Type: Bug
> Environment: CentOS 6, Cassandra 3.10
>Reporter: Artem Rokhin
>Assignee: Aleksey Yeschenko
>Priority: Normal
> Labels: pull-request-available
> Fix For: 3.0.15, 3.11.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Constantly see this error in the log without any additional information or a
> stack trace.
> {code}
> Exception in thread Thread[MessagingService-Incoming-/10.0.1.26,5,main]
> {code}
> {code}
> java.lang.ArrayIndexOutOfBoundsException: null
> {code}
> Logger: org.apache.cassandra.service.CassandraDaemon
> Thrdead: MessagingService-Incoming-/10.0.1.12
> Method: uncaughtException
> File: CassandraDaemon.java
> Line: 229
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (CASSANDRA-15128) Cassandra does not support openjdk version "1.8.0_202"
[
https://issues.apache.org/jira/browse/CASSANDRA-15128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872128#comment-16872128
]
Mikko Ala-Fossi edited comment on CASSANDRA-15128 at 6/25/19 7:56 AM:
--
Seems to be fixed in jamm 0.3.3, not verified.
[https://github.com/jbellis/jamm/blob/v0.3.3/src/org/github/jamm/MemoryLayoutSpecification.java#L197]
[https://github.com/apache/cassandra/blob/trunk/build.xml#L114]
was (Author: malafossi):
Seems to be fixed in jamm 0.3.3, not verified.
[https://github.com/jbellis/jamm/blob/v0.3.3/src/org/github/jamm/MemoryLayoutSpecification.java#L197]
> Cassandra does not support openjdk version "1.8.0_202"
> --
>
> Key: CASSANDRA-15128
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15128
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Panneerselvam
>Priority: Normal
>
> I am trying to setup Apache Cassandra DB 3.11.4 version in my Windows 8
> system and getting below error while starting the Cassandra.bat file.
> Software installed:
> * Cassandra 3.11.4
> * Java 1.8
> * Python 2.7
> It started working after installing HotSpot jdk 1.8 .
> Are we not supporting openjdk1.8 or only the issue with the particular
> version (1.8.0_202).
>
>
> {code:java}
> Exception (java.lang.ExceptionInInitializerError) encountered during startup:
> null
> java.lang.ExceptionInInitializerError
> at java.lang.J9VMInternals.ensureError(J9VMInternals.java:146)
> at
> java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:135)
> at
> org.apache.cassandra.utils.ObjectSizes.sizeOfReferenceArray(ObjectSizes.java:79)
> at
> org.apache.cassandra.utils.ObjectSizes.sizeOfArray(ObjectSizes.java:89)
> at
> org.apache.cassandra.utils.ObjectSizes.sizeOnHeapExcludingData(ObjectSizes.java:112)
> at
> org.apache.cassandra.db.AbstractBufferClusteringPrefix.unsharedHeapSizeExcludingData(AbstractBufferClusteringPrefix.java:70)
> at
> org.apache.cassandra.db.rows.BTreeRow.unsharedHeapSizeExcludingData(BTreeRow.java:450)
> at
> org.apache.cassandra.db.partitions.AtomicBTreePartition$RowUpdater.apply(AtomicBTreePartition.java:336)
> at
> org.apache.cassandra.db.partitions.AtomicBTreePartition$RowUpdater.apply(AtomicBTreePartition.java:295)
> at
> org.apache.cassandra.utils.btree.BTree.buildInternal(BTree.java:139)
> at org.apache.cassandra.utils.btree.BTree.build(BTree.java:121)
> at org.apache.cassandra.utils.btree.BTree.update(BTree.java:178)
> at
> org.apache.cassandra.db.partitions.AtomicBTreePartition.addAllWithSizeDelta(AtomicBTreePartition.java:156)
> at org.apache.cassandra.db.Memtable.put(Memtable.java:282)
> at
> org.apache.cassandra.db.ColumnFamilyStore.apply(ColumnFamilyStore.java:1352)
> at org.apache.cassandra.db.Keyspace.applyInternal(Keyspace.java:626)
> at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:470)
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:227)
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:232)
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:241)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeInternalWithoutCondition(ModificationStatement.java:587)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeInternal(ModificationStatement.java:581)
> at
> org.apache.cassandra.cql3.QueryProcessor.executeOnceInternal(QueryProcessor.java:365)
> at
> org.apache.cassandra.db.SystemKeyspace.persistLocalMetadata(SystemKeyspace.java:520)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:221)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:620)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:732)
> Caused by: java.lang.NumberFormatException: For input string: "openj9-0"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.parseInt(Integer.java:615)
> at
> org.github.jamm.MemoryLayoutSpecification.getEffectiveMemoryLayoutSpecification(MemoryLayoutSpecification.java:190)
> at
> org.github.jamm.MemoryLayoutSpecification.(MemoryLayoutSpecification.java:31)
> {code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15128) Cassandra does not support openjdk version "1.8.0_202"
[
https://issues.apache.org/jira/browse/CASSANDRA-15128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872128#comment-16872128
]
Mikko Ala-Fossi commented on CASSANDRA-15128:
-
Seems to be fixed in jamm 0.3.3, not verified.
[https://github.com/jbellis/jamm/blob/v0.3.3/src/org/github/jamm/MemoryLayoutSpecification.java#L197]
> Cassandra does not support openjdk version "1.8.0_202"
> --
>
> Key: CASSANDRA-15128
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15128
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Panneerselvam
>Priority: Normal
>
> I am trying to setup Apache Cassandra DB 3.11.4 version in my Windows 8
> system and getting below error while starting the Cassandra.bat file.
> Software installed:
> * Cassandra 3.11.4
> * Java 1.8
> * Python 2.7
> It started working after installing HotSpot jdk 1.8 .
> Are we not supporting openjdk1.8 or only the issue with the particular
> version (1.8.0_202).
>
>
> {code:java}
> Exception (java.lang.ExceptionInInitializerError) encountered during startup:
> null
> java.lang.ExceptionInInitializerError
> at java.lang.J9VMInternals.ensureError(J9VMInternals.java:146)
> at
> java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:135)
> at
> org.apache.cassandra.utils.ObjectSizes.sizeOfReferenceArray(ObjectSizes.java:79)
> at
> org.apache.cassandra.utils.ObjectSizes.sizeOfArray(ObjectSizes.java:89)
> at
> org.apache.cassandra.utils.ObjectSizes.sizeOnHeapExcludingData(ObjectSizes.java:112)
> at
> org.apache.cassandra.db.AbstractBufferClusteringPrefix.unsharedHeapSizeExcludingData(AbstractBufferClusteringPrefix.java:70)
> at
> org.apache.cassandra.db.rows.BTreeRow.unsharedHeapSizeExcludingData(BTreeRow.java:450)
> at
> org.apache.cassandra.db.partitions.AtomicBTreePartition$RowUpdater.apply(AtomicBTreePartition.java:336)
> at
> org.apache.cassandra.db.partitions.AtomicBTreePartition$RowUpdater.apply(AtomicBTreePartition.java:295)
> at
> org.apache.cassandra.utils.btree.BTree.buildInternal(BTree.java:139)
> at org.apache.cassandra.utils.btree.BTree.build(BTree.java:121)
> at org.apache.cassandra.utils.btree.BTree.update(BTree.java:178)
> at
> org.apache.cassandra.db.partitions.AtomicBTreePartition.addAllWithSizeDelta(AtomicBTreePartition.java:156)
> at org.apache.cassandra.db.Memtable.put(Memtable.java:282)
> at
> org.apache.cassandra.db.ColumnFamilyStore.apply(ColumnFamilyStore.java:1352)
> at org.apache.cassandra.db.Keyspace.applyInternal(Keyspace.java:626)
> at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:470)
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:227)
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:232)
> at org.apache.cassandra.db.Mutation.apply(Mutation.java:241)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeInternalWithoutCondition(ModificationStatement.java:587)
> at
> org.apache.cassandra.cql3.statements.ModificationStatement.executeInternal(ModificationStatement.java:581)
> at
> org.apache.cassandra.cql3.QueryProcessor.executeOnceInternal(QueryProcessor.java:365)
> at
> org.apache.cassandra.db.SystemKeyspace.persistLocalMetadata(SystemKeyspace.java:520)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:221)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:620)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:732)
> Caused by: java.lang.NumberFormatException: For input string: "openj9-0"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.parseInt(Integer.java:615)
> at
> org.github.jamm.MemoryLayoutSpecification.getEffectiveMemoryLayoutSpecification(MemoryLayoutSpecification.java:190)
> at
> org.github.jamm.MemoryLayoutSpecification.(MemoryLayoutSpecification.java:31)
> {code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
