[jira] [Commented] (CASSANDRA-14376) Limiting a clustering column with a range not allowed when using "group by"
[
https://issues.apache.org/jira/browse/CASSANDRA-14376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16520647#comment-16520647
]
Chris mildebrandt commented on CASSANDRA-14376:
---
I see now, thanks for the detailed explanation Alexander.
> Limiting a clustering column with a range not allowed when using "group by"
> ---
>
> Key: CASSANDRA-14376
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14376
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
> Environment: Cassandra 3.11.1
>Reporter: Chris mildebrandt
>Priority: Major
>
> I’m trying to use a range to limit a clustering column while at the same time
> using `group by` and running into issues. Here’s a sample table:
> {{create table if not exists samples (name text, partition int, sample int,
> city text, state text, count counter, primary key ((name, partition), sample,
> city, state)) with clustering order by (sample desc);}}
> When I filter `sample` by a range, I get an error:
> {{select city, state, sum(count) from samples where name='bob' and
> partition=1 and sample>=1 and sample<=3 group by city, state;}}
> {{{color:#ff}InvalidRequest: Error from server: code=2200 [Invalid
> query] message="Group by currently only support groups of columns following
> their declared order in the PRIMARY KEY"{color}}}
> However, it allows the query when I change from a range to an equals:
> {{select city, state, sum(count) from samples where name='bob' and
> partition=1 and sample=1 group by city, state;}}
> {{city | state | system.sum(count)}}
> {{++--}}
> {{ Austin | TX | 2}}
> {{ Denver | CO | 1}}
--
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-14376) Limiting a clustering column with a range not allowed when using "group by"
[
https://issues.apache.org/jira/browse/CASSANDRA-14376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433183#comment-16433183
]
Chris mildebrandt commented on CASSANDRA-14376:
---
Sample for reproduction:
{{create table if not exists samples (name text, partition int, sample int,
city text, state text, count counter, primary key ((name, partition), sample,
city, state)) with clustering order by (sample desc);}}
{{update samples set count=count+1 where name='bob' and partition=1 and
sample=1 and city='Denver' and state='CO';}}
{{update samples set count=count+1 where name='bob' and partition=1 and
sample=2 and city='Denver' and state='CO';}}
{{update samples set count=count+1 where name='bob' and partition=1 and
sample=3 and city='Denver' and state='CO';}}
{{update samples set count=count+1 where name='bob' and partition=1 and
sample=3 and city='Denver' and state='CO';}}
{{update samples set count=count+1 where name='bob' and partition=1 and
sample=1 and city='Austin' and state='TX';}}
{{update samples set count=count+1 where name='bob' and partition=1 and
sample=1 and city='Austin' and state='TX';}}
{{update samples set count=count+1 where name='bob' and partition=1 and
sample=2 and city='Austin' and state='TX';}}
{{update samples set count=count+1 where name='bob' and partition=1 and
sample=2 and city='Austin' and state='TX';}}
{{update samples set count=count+1 where name='bob' and partition=1 and
sample=2 and city='Austin' and state='TX';}}
{{select city, state, sum(count) from samples where name='bob' and partition=1
and sample>=1 and sample<=3 group by city, state;}}
{{select city, state, sum(count) from samples where name='bob' and partition=1
and sample=1 group by city, state;}}
> Limiting a clustering column with a range not allowed when using "group by"
> ---
>
> Key: CASSANDRA-14376
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14376
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
> Environment: Cassandra 3.11.1
>Reporter: Chris mildebrandt
>Priority: Major
>
> I’m trying to use a range to limit a clustering column while at the same time
> using `group by` and running into issues. Here’s a sample table:
> {{create table if not exists samples (name text, partition int, sample int,
> city text, state text, count counter, primary key ((name, partition), sample,
> city, state)) with clustering order by (sample desc);}}
> When I filter `sample` by a range, I get an error:
> {{select city, state, sum(count) from samples where name='bob' and
> partition=1 and sample>=1 and sample<=3 group by city, state;}}
> {{{color:#ff}InvalidRequest: Error from server: code=2200 [Invalid
> query] message="Group by currently only support groups of columns following
> their declared order in the PRIMARY KEY"{color}}}
> However, it allows the query when I change from a range to an equals:
> {{select city, state, sum(count) from samples where name='bob' and
> partition=1 and sample=1 group by city, state;}}
> {{city | state | system.sum(count)}}
> {{++--}}
> {{ Austin | TX | 2}}
> {{ Denver | CO | 1}}
--
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-14376) Limiting a clustering column with a range not allowed when using "group by"
[
https://issues.apache.org/jira/browse/CASSANDRA-14376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris mildebrandt updated CASSANDRA-14376:
--
Description:
I’m trying to use a range to limit a clustering column while at the same time
using `group by` and running into issues. Here’s a sample table:
{{create table if not exists samples (name text, partition int, sample int,
city text, state text, count counter, primary key ((name, partition), sample,
city, state)) with clustering order by (sample desc);}}
When I filter `sample` by a range, I get an error:
{{select city, state, sum(count) from samples where name='bob' and partition=1
and sample>=1 and sample<=3 group by city, state;}}
{{{color:#ff}InvalidRequest: Error from server: code=2200 [Invalid query]
message="Group by currently only support groups of columns following their
declared order in the PRIMARY KEY"{color}}}
However, it allows the query when I change from a range to an equals:
{{select city, state, sum(count) from samples where name='bob' and partition=1
and sample=1 group by city, state;}}
{{city | state | system.sum(count)}}
{{++--}}
{{ Austin | TX | 2}}
{{ Denver | CO | 1}}
was:
I’m trying to use a range to limit a clustering column while at the same time
using `group by` and running into issues. Here’s a sample table:
{{create table if not exists samples (name text, partition int, sample int,
city text, state text, count counter, primary key ((name, partition), sample,
city, state)) with clustering order by (sample desc);}}
When I filter `sample` by a range, I get an error:
{{select city, state, sum(count) from samples where name='bob' and partition=1
and sample>=1 and sample<=3 group by city, state;}}
{{{color:#FF}InvalidRequest: Error from server: code=2200 [Invalid query]
message="Group by currently only support groups of columns following their
declared order in the PRIMARY KEY"{color}}}
However, it allows the query when I change from a range to an equals:
{{select city, state, sum(count) from samples where name='bob' and partition=1
and sample=1 group by city, state;}}
{{city | state | system.sum(count)}}
{{+---+---}}
{{ Austin | TX | 2}}
{{ Denver | CO | 1}}
> Limiting a clustering column with a range not allowed when using "group by"
> ---
>
> Key: CASSANDRA-14376
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14376
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
> Environment: Cassandra 3.11.1
>Reporter: Chris mildebrandt
>Priority: Major
>
> I’m trying to use a range to limit a clustering column while at the same time
> using `group by` and running into issues. Here’s a sample table:
> {{create table if not exists samples (name text, partition int, sample int,
> city text, state text, count counter, primary key ((name, partition), sample,
> city, state)) with clustering order by (sample desc);}}
> When I filter `sample` by a range, I get an error:
> {{select city, state, sum(count) from samples where name='bob' and
> partition=1 and sample>=1 and sample<=3 group by city, state;}}
> {{{color:#ff}InvalidRequest: Error from server: code=2200 [Invalid
> query] message="Group by currently only support groups of columns following
> their declared order in the PRIMARY KEY"{color}}}
> However, it allows the query when I change from a range to an equals:
> {{select city, state, sum(count) from samples where name='bob' and
> partition=1 and sample=1 group by city, state;}}
> {{city | state | system.sum(count)}}
> {{++--}}
> {{ Austin | TX | 2}}
> {{ Denver | CO | 1}}
--
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-14376) Limiting a clustering column with a range not allowed when using "group by"
Chris mildebrandt created CASSANDRA-14376:
-
Summary: Limiting a clustering column with a range not allowed
when using "group by"
Key: CASSANDRA-14376
URL: https://issues.apache.org/jira/browse/CASSANDRA-14376
Project: Cassandra
Issue Type: Bug
Components: CQL
Environment: Cassandra 3.11.1
Reporter: Chris mildebrandt
I’m trying to use a range to limit a clustering column while at the same time
using `group by` and running into issues. Here’s a sample table:
{{create table if not exists samples (name text, partition int, sample int,
city text, state text, count counter, primary key ((name, partition), sample,
city, state)) with clustering order by (sample desc);}}
When I filter `sample` by a range, I get an error:
{{select city, state, sum(count) from samples where name='bob' and partition=1
and sample>=1 and sample<=3 group by city, state;}}
{{{color:#FF}InvalidRequest: Error from server: code=2200 [Invalid query]
message="Group by currently only support groups of columns following their
declared order in the PRIMARY KEY"{color}}}
However, it allows the query when I change from a range to an equals:
{{select city, state, sum(count) from samples where name='bob' and partition=1
and sample=1 group by city, state;}}
{{city | state | system.sum(count)}}
{{+---+---}}
{{ Austin | TX | 2}}
{{ Denver | CO | 1}}
--
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-13991) NullPointerException when querying a table with a previous state
[ https://issues.apache.org/jira/browse/CASSANDRA-13991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241206#comment-16241206 ] Chris mildebrandt commented on CASSANDRA-13991: --- Thanks for the analysis. I've opened the following issue for gocql: https://github.com/gocql/gocql/issues/1017 > NullPointerException when querying a table with a previous state > > > Key: CASSANDRA-13991 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13991 > Project: Cassandra > Issue Type: Bug > Components: CQL >Reporter: Chris mildebrandt > Attachments: CASSANDRA-13991.log > > > Performing the following steps (using the gocql library) results in an NPE: > * With a table of 12 entries, read all rows. > * Set the page size to 1 and read the first row. Save the query state. > * Read all the row again. > * Set the page size to 5 and the page state to the previous state. (This is > where the NPE occurs). > This can be reproduced with the following project: > https://github.com/eyeofthefrog/CASSANDRA-13991 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-13991) NullPointerException when querying a table with a previous state
[
https://issues.apache.org/jira/browse/CASSANDRA-13991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16237987#comment-16237987
]
Chris mildebrandt edited comment on CASSANDRA-13991 at 11/3/17 5:03 PM:
With Cassandra 2.1.19 and 2.2.11, I get this error instead:
{noformat}
ERROR 16:59:56 Unexpected exception during request
java.lang.IllegalArgumentException: Not enough bytes. Offset: 2. Length: 25194.
Buffer size: 4
at
org.apache.cassandra.db.composites.AbstractCType.checkRemaining(AbstractCType.java:362)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.db.composites.AbstractCompoundCellNameType.fromByteBuffer(AbstractCompoundCellNameType.java:98)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.db.composites.AbstractCellNameType.cellFromByteBuffer(AbstractCellNameType.java:188)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.service.pager.RangeSliceQueryPager.(RangeSliceQueryPager.java:60)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.service.pager.QueryPagers.pager(QueryPagers.java:115)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.service.pager.QueryPagers.pager(QueryPagers.java:126)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:178)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:76)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:226)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:492)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:469)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.transport.messages.ExecuteMessage.execute(ExecuteMessage.java:142)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:507)
[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:401)
[apache-cassandra-2.2.11.jar:2.2.11]
at
io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
[netty-all-4.0.44.Final.jar:4.0.44.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:357)
[netty-all-4.0.44.Final.jar:4.0.44.Final]
at
io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:35)
[netty-all-4.0.44.Final.jar:4.0.44.Final]
at
io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:348)
[netty-all-4.0.44.Final.jar:4.0.44.Final]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:473)
[na:1.7.0_151]
at
org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:164)
[apache-cassandra-2.2.11.jar:2.2.11]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
[apache-cassandra-2.2.11.jar:2.2.11]
at java.lang.Thread.run(Thread.java:748) [na:1.7.0_151]
{noformat}
was (Author: mildebrandt):
With Cassandra 2.2.11, I get this error instead:
{noformat}
ERROR 16:59:56 Unexpected exception during request
java.lang.IllegalArgumentException: Not enough bytes. Offset: 2. Length: 25194.
Buffer size: 4
at
org.apache.cassandra.db.composites.AbstractCType.checkRemaining(AbstractCType.java:362)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.db.composites.AbstractCompoundCellNameType.fromByteBuffer(AbstractCompoundCellNameType.java:98)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.db.composites.AbstractCellNameType.cellFromByteBuffer(AbstractCellNameType.java:188)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.service.pager.RangeSliceQueryPager.(RangeSliceQueryPager.java:60)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.service.pager.QueryPagers.pager(QueryPagers.java:115)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.service.pager.QueryPagers.pager(QueryPagers.java:126)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:178)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:76)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:226)
[jira] [Commented] (CASSANDRA-13991) NullPointerException when querying a table with a previous state
[
https://issues.apache.org/jira/browse/CASSANDRA-13991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16237987#comment-16237987
]
Chris mildebrandt commented on CASSANDRA-13991:
---
With Cassandra 2.2.11, I get this error instead:
{noformat}
ERROR 16:59:56 Unexpected exception during request
java.lang.IllegalArgumentException: Not enough bytes. Offset: 2. Length: 25194.
Buffer size: 4
at
org.apache.cassandra.db.composites.AbstractCType.checkRemaining(AbstractCType.java:362)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.db.composites.AbstractCompoundCellNameType.fromByteBuffer(AbstractCompoundCellNameType.java:98)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.db.composites.AbstractCellNameType.cellFromByteBuffer(AbstractCellNameType.java:188)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.service.pager.RangeSliceQueryPager.(RangeSliceQueryPager.java:60)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.service.pager.QueryPagers.pager(QueryPagers.java:115)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.service.pager.QueryPagers.pager(QueryPagers.java:126)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:178)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:76)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:226)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:492)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:469)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.transport.messages.ExecuteMessage.execute(ExecuteMessage.java:142)
~[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:507)
[apache-cassandra-2.2.11.jar:2.2.11]
at
org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:401)
[apache-cassandra-2.2.11.jar:2.2.11]
at
io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
[netty-all-4.0.44.Final.jar:4.0.44.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:357)
[netty-all-4.0.44.Final.jar:4.0.44.Final]
at
io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:35)
[netty-all-4.0.44.Final.jar:4.0.44.Final]
at
io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:348)
[netty-all-4.0.44.Final.jar:4.0.44.Final]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:473)
[na:1.7.0_151]
at
org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:164)
[apache-cassandra-2.2.11.jar:2.2.11]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
[apache-cassandra-2.2.11.jar:2.2.11]
at java.lang.Thread.run(Thread.java:748) [na:1.7.0_151]
{noformat}
> NullPointerException when querying a table with a previous state
>
>
> Key: CASSANDRA-13991
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13991
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
>Reporter: Chris mildebrandt
>Priority: Major
> Attachments: CASSANDRA-13991.log
>
>
> Performing the following steps (using the gocql library) results in an NPE:
> * With a table of 12 entries, read all rows.
> * Set the page size to 1 and read the first row. Save the query state.
> * Read all the row again.
> * Set the page size to 5 and the page state to the previous state. (This is
> where the NPE occurs).
> This can be reproduced with the following project:
> https://github.com/eyeofthefrog/CASSANDRA-13991
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13991) NullPointerException when querying a table with a previous state
[ https://issues.apache.org/jira/browse/CASSANDRA-13991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris mildebrandt updated CASSANDRA-13991: -- Attachment: CASSANDRA-13991.log > NullPointerException when querying a table with a previous state > > > Key: CASSANDRA-13991 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13991 > Project: Cassandra > Issue Type: Bug > Components: CQL >Reporter: Chris mildebrandt >Priority: Major > Attachments: CASSANDRA-13991.log > > > Performing the following steps (using the gocql library) results in an NPE: > * With a table of 12 entries, read all rows. > * Set the page size to 1 and read the first row. Save the query state. > * Read all the row again. > * Set the page size to 5 and the page state to the previous state. (This is > where the NPE occurs). > This can be reproduced with the following project: > https://github.com/eyeofthefrog/CASSANDRA-13991 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13592) Null Pointer exception at SELECT JSON statement
[
https://issues.apache.org/jira/browse/CASSANDRA-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16237969#comment-16237969
]
Chris mildebrandt commented on CASSANDRA-13592:
---
Sure, https://issues.apache.org/jira/browse/CASSANDRA-13991
Thanks
> Null Pointer exception at SELECT JSON statement
> ---
>
> Key: CASSANDRA-13592
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13592
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
> Environment: Debian Linux
>Reporter: Wyss Philipp
>Assignee: ZhaoYang
>Priority: Major
> Labels: beginner
> Fix For: 2.2.11, 3.0.15, 3.11.1, 4.0
>
> Attachments: system.log
>
>
> A Nulll pointer exception appears when the command
> {code}
> SELECT JSON * FROM examples.basic;
> ---MORE---
> message="java.lang.NullPointerException">
> Examples.basic has the following description (DESC examples.basic;):
> CREATE TABLE examples.basic (
> key frozen> PRIMARY KEY,
> wert text
> ) WITH bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.1
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99PERCENTILE';
> {code}
> The error appears after the ---MORE--- line.
> The field "wert" has a JSON formatted string.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13991) NullPointerException when querying a table with a previous state
[ https://issues.apache.org/jira/browse/CASSANDRA-13991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris mildebrandt updated CASSANDRA-13991: -- Description: Performing the following steps (using the gocql library) results in an NPE: * With a table of 12 entries, read all rows. * Set the page size to 1 and read the first row. Save the query state. * Read all the row again. * Set the page size to 5 and the page state to the previous state. (This is where the NPE occurs). This can be reproduced with the following project: https://github.com/eyeofthefrog/CASSANDRA-13991 was: Performing the following steps (using the gocql library) results in an NPE: * With a table of 12 entries, read all rows. * Set the page size to 1 and read the first row. Save the query state. * Read all the row again. * Set the page size to 5 and the page state to the previous state. (This is where the NPE occurs). > NullPointerException when querying a table with a previous state > > > Key: CASSANDRA-13991 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13991 > Project: Cassandra > Issue Type: Bug > Components: CQL >Reporter: Chris mildebrandt >Priority: Major > > Performing the following steps (using the gocql library) results in an NPE: > * With a table of 12 entries, read all rows. > * Set the page size to 1 and read the first row. Save the query state. > * Read all the row again. > * Set the page size to 5 and the page state to the previous state. (This is > where the NPE occurs). > This can be reproduced with the following project: > https://github.com/eyeofthefrog/CASSANDRA-13991 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-13991) NullPointerException when querying a table with a previous state
Chris mildebrandt created CASSANDRA-13991: - Summary: NullPointerException when querying a table with a previous state Key: CASSANDRA-13991 URL: https://issues.apache.org/jira/browse/CASSANDRA-13991 Project: Cassandra Issue Type: Bug Components: CQL Reporter: Chris mildebrandt Priority: Major Performing the following steps (using the gocql library) results in an NPE: * With a table of 12 entries, read all rows. * Set the page size to 1 and read the first row. Save the query state. * Read all the row again. * Set the page size to 5 and the page state to the previous state. (This is where the NPE occurs). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13592) Null Pointer exception at SELECT JSON statement
[
https://issues.apache.org/jira/browse/CASSANDRA-13592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16236755#comment-16236755
]
Chris mildebrandt commented on CASSANDRA-13592:
---
I'm getting almost exactly the same stacktrace using Cassandra 3.11.1:
{noformat}
java.lang.NullPointerException: null
at
org.apache.cassandra.dht.Murmur3Partitioner.getHash(Murmur3Partitioner.java:230)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.dht.Murmur3Partitioner.decorateKey(Murmur3Partitioner.java:66)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.config.CFMetaData.decorateKey(CFMetaData.java:627)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.service.pager.PartitionRangeQueryPager.(PartitionRangeQueryPager.java:44)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.db.PartitionRangeReadCommand.getPager(PartitionRangeReadCommand.java:268)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.cql3.statements.SelectStatement.getPager(SelectStatement.java:475)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:288)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:118)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:224)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:530)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:507)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.transport.messages.ExecuteMessage.execute(ExecuteMessage.java:146)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:517)
[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:410)
[apache-cassandra-3.11.1.jar:3.11.1]
at
io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
[netty-all-4.0.44.Final.jar:4.0.44.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:357)
[netty-all-4.0.44.Final.jar:4.0.44.Final]
at
io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:35)
[netty-all-4.0.44.Final.jar:4.0.44.Final]
at
io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:348)
[netty-all-4.0.44.Final.jar:4.0.44.Final]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[na:1.8.0_131]
at
org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162)
[apache-cassandra-3.11.1.jar:3.11.1]
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:109)
[apache-cassandra-3.11.1.jar:3.11.1]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_131]
{noformat}
It can be recreated with this project:
https://github.com/eyeofthefrog/CASSANDRA-13592
I think it's the same root cause, but let me know if I should open another
issue.
> Null Pointer exception at SELECT JSON statement
> ---
>
> Key: CASSANDRA-13592
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13592
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
> Environment: Debian Linux
>Reporter: Wyss Philipp
>Assignee: ZhaoYang
>Priority: Major
> Labels: beginner
> Fix For: 2.2.11, 3.0.15, 3.11.1, 4.0
>
> Attachments: system.log
>
>
> A Nulll pointer exception appears when the command
> {code}
> SELECT JSON * FROM examples.basic;
> ---MORE---
> message="java.lang.NullPointerException">
> Examples.basic has the following description (DESC examples.basic;):
> CREATE TABLE examples.basic (
> key frozen> PRIMARY KEY,
> wert text
> ) WITH bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.1
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND
[jira] [Comment Edited] (CASSANDRA-8274) Node fails to rejoin cluster on EC2 if private IP is changed
[
https://issues.apache.org/jira/browse/CASSANDRA-8274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177493#comment-16177493
]
Chris mildebrandt edited comment on CASSANDRA-8274 at 9/23/17 7:21 PM:
---
I just hit this issue today with the 3.11.0 docker image running in kubernetes.
I had 4 nodes in the cassandra cluster, two members were restarted (and their
IPs changed) and can't rejoin. There's one seed that is up and reachable from
all the other containers, and one other member that is able to join. The first
exception I see is this:
{noformat}
java.lang.RuntimeException: Cache schema version
38e97a53-563b-3074-b86f-c81efa980524 does not match current schema version
1bfdabae-743e-357e-a661-93984c26bc32
at
org.apache.cassandra.cache.AutoSavingCache.loadSaved(AutoSavingCache.java:206)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.cache.AutoSavingCache$3.call(AutoSavingCache.java:164)
[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.cache.AutoSavingCache$3.call(AutoSavingCache.java:160)
[apache-cassandra-3.11.0.jar:3.11.0]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[na:1.8.0_131]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[na:1.8.0_131]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_131]
{noformat}
Then I see the one related to this issue:
{noformat}
java.lang.RuntimeException: Unable to gossip with any seeds
at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:1413)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:550)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:801)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:666)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:612)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:393)
[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:600)
[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:689)
[apache-cassandra-3.11.0.jar:3.11.0]
{noformat}
Restarting the nodes didn't help. nodetool status is now reporting only two
nodes, and nodetool gossipinfo has three "empty" entries (along with the two
good ones not shown):
{noformat}
/100.96.3.164
generation:0
heartbeat:0
TOKENS: not present
/100.96.1.7
generation:0
heartbeat:0
TOKENS: not present
/100.96.2.170
generation:0
heartbeat:0
TOKENS: not present
{noformat}
was (Author: mildebrandt):
I just hit this issue today with the 3.11.0 docker image running in kubernetes.
I had 4 nodes in the cassandra cluster, two members were restarted (and their
IPs changed) and can't rejoin. There's one seed that is up and reachable from
all the other containers, and one other member that is able to join. The first
exception I see is this:
{noformat}
java.lang.RuntimeException: Cache schema version
38e97a53-563b-3074-b86f-c81efa980524 does not match current schema version
1bfdabae-743e-357e-a661-93984c26bc32
at
org.apache.cassandra.cache.AutoSavingCache.loadSaved(AutoSavingCache.java:206)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.cache.AutoSavingCache$3.call(AutoSavingCache.java:164)
[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.cache.AutoSavingCache$3.call(AutoSavingCache.java:160)
[apache-cassandra-3.11.0.jar:3.11.0]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[na:1.8.0_131]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[na:1.8.0_131]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_131]
{noformat}
Then I see the one related to this issue:
{noformat}
java.lang.RuntimeException: Unable to gossip with any seeds
at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:1413)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:550)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:801)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
[jira] [Comment Edited] (CASSANDRA-8274) Node fails to rejoin cluster on EC2 if private IP is changed
[
https://issues.apache.org/jira/browse/CASSANDRA-8274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177493#comment-16177493
]
Chris mildebrandt edited comment on CASSANDRA-8274 at 9/23/17 4:39 AM:
---
I just hit this issue today with the 3.11.0 docker image running in kubernetes.
I had 4 nodes in the cassandra cluster, two members were restarted (and their
IPs changed) and can't rejoin. There's one seed that is up and reachable from
all the other containers, and one other member that is able to join. The first
exception I see is this:
{noformat}
java.lang.RuntimeException: Cache schema version
38e97a53-563b-3074-b86f-c81efa980524 does not match current schema version
1bfdabae-743e-357e-a661-93984c26bc32
at
org.apache.cassandra.cache.AutoSavingCache.loadSaved(AutoSavingCache.java:206)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.cache.AutoSavingCache$3.call(AutoSavingCache.java:164)
[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.cache.AutoSavingCache$3.call(AutoSavingCache.java:160)
[apache-cassandra-3.11.0.jar:3.11.0]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[na:1.8.0_131]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[na:1.8.0_131]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_131]
{noformat}
Then I see the one related to this issue:
{noformat}
java.lang.RuntimeException: Unable to gossip with any seeds
at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:1413)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:550)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:801)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:666)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:612)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:393)
[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:600)
[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:689)
[apache-cassandra-3.11.0.jar:3.11.0]
{noformat}
Restarting the nodes didn't help. nodetool status is now reporting only two
nodes, and nodetool gossipinfo has three "empty" entries:
{noformat}
/100.96.3.164
generation:0
heartbeat:0
TOKENS: not present
/100.96.1.7
generation:0
heartbeat:0
TOKENS: not present
/100.96.2.170
generation:0
heartbeat:0
TOKENS: not present
{noformat}
was (Author: mildebrandt):
I just hit this issue today with the 3.11.0 docker image running in kubernetes.
I had 4 nodes in the cassandra cluster, two members were restarted and can't
rejoin. There's one seed that is up and reachable from all the other
containers, and one other member that is able to join. The first exception I
see is this:
{{java.lang.RuntimeException: Cache schema version
38e97a53-563b-3074-b86f-c81efa980524 does not match current schema version
1bfdabae-743e-357e-a661-93984c26bc32
at
org.apache.cassandra.cache.AutoSavingCache.loadSaved(AutoSavingCache.java:206)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.cache.AutoSavingCache$3.call(AutoSavingCache.java:164)
[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.cache.AutoSavingCache$3.call(AutoSavingCache.java:160)
[apache-cassandra-3.11.0.jar:3.11.0]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[na:1.8.0_131]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[na:1.8.0_131]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_131]}}
Then I see the one related to this issue:
{{java.lang.RuntimeException: Unable to gossip with any seeds
at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:1413)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:550)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:801)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:666)
[jira] [Commented] (CASSANDRA-8274) Node fails to rejoin cluster on EC2 if private IP is changed
[
https://issues.apache.org/jira/browse/CASSANDRA-8274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177493#comment-16177493
]
Chris mildebrandt commented on CASSANDRA-8274:
--
I just hit this issue today with the 3.11.0 docker image running in kubernetes.
I had 4 nodes in the cassandra cluster, two members were restarted and can't
rejoin. There's one seed that is up and reachable from all the other
containers, and one other member that is able to join. The first exception I
see is this:
{{java.lang.RuntimeException: Cache schema version
38e97a53-563b-3074-b86f-c81efa980524 does not match current schema version
1bfdabae-743e-357e-a661-93984c26bc32
at
org.apache.cassandra.cache.AutoSavingCache.loadSaved(AutoSavingCache.java:206)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.cache.AutoSavingCache$3.call(AutoSavingCache.java:164)
[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.cache.AutoSavingCache$3.call(AutoSavingCache.java:160)
[apache-cassandra-3.11.0.jar:3.11.0]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[na:1.8.0_131]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[na:1.8.0_131]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_131]}}
Then I see the one related to this issue:
{{java.lang.RuntimeException: Unable to gossip with any seeds
at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:1413)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:550)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:801)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:666)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:612)
~[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:393)
[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:600)
[apache-cassandra-3.11.0.jar:3.11.0]
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:689)
[apache-cassandra-3.11.0.jar:3.11.0]}}
Restarting the nodes didn't help. nodetool status is now reporting only two
nodes, and nodetool gossipinfo has three "empty" entries:
{{/100.96.3.164
generation:0
heartbeat:0
TOKENS: not present
/100.96.1.7
generation:0
heartbeat:0
TOKENS: not present
/100.96.2.170
generation:0
heartbeat:0
TOKENS: not present}}
> Node fails to rejoin cluster on EC2 if private IP is changed
>
>
> Key: CASSANDRA-8274
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8274
> Project: Cassandra
> Issue Type: Bug
> Components: Distributed Metadata
> Environment: Amazon EC2
>Reporter: Joseph Clark
>Priority: Minor
> Fix For: 3.11.x
>
>
> Nodes in Amazon AWS EC2 Classic (not a VPC) may be assigned a new private IP
> if the node is stopped and then started again. In this case we have puppet
> update the configured listen_address to the new private IP. However, once the
> cassandra service starts, it is unable to communicate with the existing
> nodes(single region) and vice versa.
> 'nodetool status' shows that each node believes that it is 'UN' and the other
> node is 'DN'.
> 'nodetool gossipinfo' on the node that remained running shows the *old*
> private IP listed as the 'INTERNAL_IP' of the node that was stopped and
> restarted.
> The situation is resolved by restarting the cassandra service on the node
> that remained running. Once it has restarted, the INTERNAL_IP is correctly
> updated to the new private IP. 'nodetool status' shows that both nodes are up
> and the cluster appears to function normally.
> This appears to me to be the root cause of
> https://issues.apache.org/jira/browse/CASSANDRA-7292. -Possibly
> https://issues.apache.org/jira/browse/CASSANDRA-8072 as well, but I am not
> convinced they are actually duplicates.-
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
