[jira] [Issue Comment Deleted] (CASSANDRA-14594) No validation for repeated fields in cqlsh and misbehaviour in data display
[ https://issues.apache.org/jira/browse/CASSANDRA-14594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chakravarthi Manepalli updated CASSANDRA-14594: --- Comment: was deleted (was: Hi harini, can you please let me know regarding the status of my bug report?) > No validation for repeated fields in cqlsh and misbehaviour in data display > --- > > Key: CASSANDRA-14594 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14594 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Tools > Environment: Operating System: Ubuntu 14.04(64 bit) (Image : > cqlshbug.png) > Operating System: ubuntu 16.04 (64 bit) (Image: > cqlsh_select_repeated_fields.png) > Apache cassandra version : 3.11.1 >Reporter: Chakravarthi Manepalli >Priority: Normal > Attachments: cqlsh bug.png, cqlsh_select_repeated_fields.png > > > In a table, if the fields(columns) are repeated in select call, the > displaying information is not correct. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15079) Secondary Index not returning complete data
[ https://issues.apache.org/jira/browse/CASSANDRA-15079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026570#comment-17026570 ] Chakravarthi Manepalli commented on CASSANDRA-15079: [~ifesdjeen], I do not have any backup states. I will try to recreate it from scratch. It may take more time to reproduce this issue. But I will keep you posted. Please let me know if you need any particular information about any configurations/strategies/logs/sstable (.db files) so that I will keep track of them or will enable those properties and will provide them here for better debugging. > Secondary Index not returning complete data > --- > > Key: CASSANDRA-15079 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15079 > Project: Cassandra > Issue Type: Bug > Components: Feature/2i Index >Reporter: Chakravarthi Manepalli >Priority: High > Labels: performance > Attachments: missing_data_cassandra.png > > > The result response when we query using a secondary index does not give > complete data. Some of the rows are missing. After dropping the index and > creating it again, the query worked fine. > Observation: The missed data entry is last edited 20 days ago. > I suspect may be the data which is old is not getting indexed properly > through secondary indexes. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15079) Secondary Index not returning complete data
[ https://issues.apache.org/jira/browse/CASSANDRA-15079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026439#comment-17026439 ] Chakravarthi Manepalli commented on CASSANDRA-15079: [~nirmalsinghkps], The compaction strategy is size tiered. FYI, the table specs have already been mentioned in the screenshot provided. [~cscotta], I will try to reproduce the issue now. So, it might take a month to update on it, given that the stale data over 20 days is not being updated properly. Thanks, Chakri > Secondary Index not returning complete data > --- > > Key: CASSANDRA-15079 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15079 > Project: Cassandra > Issue Type: Bug > Components: Feature/2i Index >Reporter: Chakravarthi Manepalli >Priority: High > Labels: performance > Attachments: missing_data_cassandra.png > > > The result response when we query using a secondary index does not give > complete data. Some of the rows are missing. After dropping the index and > creating it again, the query worked fine. > Observation: The missed data entry is last edited 20 days ago. > I suspect may be the data which is old is not getting indexed properly > through secondary indexes. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13556) Corrupted SSTables
[
https://issues.apache.org/jira/browse/CASSANDRA-13556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16900912#comment-16900912
]
Chakravarthi Manepalli commented on CASSANDRA-13556:
I have observed the same issue in one of our setups. There were no removal or
addition of columns in a recent period. I have observed the stack error in
debug log.
WARN [ReadStage-1] 2019-08-06 16:34:29,093
AbstractLocalAwareExecutorService.java:167 - Uncaught exception on thread
Thread[ReadStage-1,5,main]: {}
java.lang.RuntimeException:
org.apache.cassandra.io.sstable.CorruptSSTableException: Corrupted:
/media/db_store/data/server_data/known_ap_ssid_list-d2cde2f0adf211e99625cd7f2acaf155/mc-5-big-Data.db
at
org.apache.cassandra.service.StorageProxy$DroppableRunnable.run(StorageProxy.java:2598)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
~[na:1.8.0_152]
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.AbstractLocalAwareExecutorService$LocalSessionFutureTask.run(AbstractLocalAwareExecutorService.java:134)
[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_152]
Caused by: org.apache.cassandra.io.sstable.CorruptSSTableException: Corrupted:
/media/db_store/data/server_data/known_ap_ssid_list-d2cde2f0adf211e99625cd7f2acaf155/mc-5-big-Data.db
at
org.apache.cassandra.db.columniterator.AbstractSSTableIterator$Reader.hasNext(AbstractSSTableIterator.java:391)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.db.columniterator.AbstractSSTableIterator.hasNext(AbstractSSTableIterator.java:258)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.db.rows.LazilyInitializedUnfilteredRowIterator.computeNext(LazilyInitializedUnfilteredRowIterator.java:100)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.db.rows.UnfilteredRowIteratorWithLowerBound.computeNext(UnfilteredRowIteratorWithLowerBound.java:116)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.db.rows.UnfilteredRowIteratorWithLowerBound.computeNext(UnfilteredRowIteratorWithLowerBound.java:47)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.utils.MergeIterator$Candidate.advance(MergeIterator.java:374)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.utils.MergeIterator$ManyToOne.advance(MergeIterator.java:186)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.utils.MergeIterator$ManyToOne.computeNext(MergeIterator.java:155)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:499)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:359)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.db.transform.BaseRows.hasNext(BaseRows.java:133)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:136)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:92)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer.serialize(UnfilteredRowIteratorSerializer.java:79)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.db.partitions.UnfilteredPartitionIterators$Serializer.serialize(UnfilteredPartitionIterators.java:308)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.db.ReadResponse$LocalDataResponse.build(ReadResponse.java:167)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.db.ReadResponse$LocalDataResponse.(ReadResponse.java:160)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
org.apache.cassandra.db.ReadResponse$LocalDataResponse.(ReadResponse.java:156)
~[apache-cassandra-3.11.1.jar:3.11.1]
at
[jira] [Commented] (CASSANDRA-12005) Out of memory error in MessagingService
[ https://issues.apache.org/jira/browse/CASSANDRA-12005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864029#comment-16864029 ] Chakravarthi Manepalli commented on CASSANDRA-12005: I have faced a similar issue, heap overflows after 15-30 min time from the node restart. Setup environment - single node running in localhost with 64GB RAM and 8GB HEAP memory nodetool info: ID : 35c11cc6-f881-4685-b211-654c4a21bf59 Gossip active : true Thrift active : false Native Transport active: true Load : 4.57 MiB Generation No : 1560507197 Uptime (seconds) : 250 Heap Memory (MB) : 301.67 / 8112.00 Off Heap Memory (MB) : 0.01 Data Center : datacenter1 Rack : rack1 Exceptions : 0 Key Cache : entries 128, size 16.5 KiB, capacity 100 MiB, 375 hits, 510 requests, 0.735 recent hit rate, 14400 save period in seconds Row Cache : entries 0, size 0 bytes, capacity 0 bytes, 0 hits, 0 requests, NaN recent hit rate, 0 save period in seconds Counter Cache : entries 0, size 0 bytes, capacity 50 MiB, 0 hits, 0 requests, NaN recent hit rate, 7200 save period in seconds Chunk Cache : entries 19, size 1.19 MiB, capacity 480 MiB, 495 misses, 1126 requests, 0.560 recent hit rate, 48.843 microseconds miss latency Percent Repaired : 100.0% Token : (invoke with -T/--tokens to see all 256 tokens) The node shows running in service status but unable to take cqlsh or access nodetool. ERROR [Native-Transport-Requests-1] 2019-06-14 14:41:35,747 JVMStabilityInspector.java:74 - OutOfMemory error letting the JVM handle the error: java.lang.OutOfMemoryError: Java heap space at org.apache.cassandra.db.Clustering.make(Clustering.java:81) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.db.CBuilder$ArrayBackedBuilder.buildWith(CBuilder.java:210) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.db.MultiCBuilder$MultiClusteringBuilder.build(MultiCBuilder.java:416) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.cql3.restrictions.ClusteringColumnRestrictions.valuesAsClustering(ClusteringColumnRestrictions.java:113) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.cql3.restrictions.StatementRestrictions.getClusteringColumns(StatementRestrictions.java:770) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.cql3.statements.SelectStatement.getRequestedRows(SelectStatement.java:765) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.cql3.statements.SelectStatement.makeClusteringIndexFilter(SelectStatement.java:628) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.cql3.statements.SelectStatement.getSliceCommands(SelectStatement.java:519) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.cql3.statements.SelectStatement.getQuery(SelectStatement.java:306) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:282) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:117) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:224) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:255) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:240) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.transport.messages.QueryMessage.execute(QueryMessage.java:116) ~[apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:517) [apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:410) [apache-cassandra-3.11.3.jar:3.11.3] 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_212] at org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:162) [apache-cassandra-3.11.3.jar:3.11.3] at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:109) [apache-cassandra-3.11.3.jar:3.11.3] at java.lang.Thread.run(Thread.java:748) [na:1.8.0_212] WARN [epollEventLoopGroup-2-5] 2019-06-14 14:41:35,748 Slf4JLogger.java:151
[jira] [Updated] (CASSANDRA-15070) coredump in cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-15070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chakravarthi Manepalli updated CASSANDRA-15070: --- Description: Cqlsh crashes with core dump when given ctrl+| or ctrl+\ or ctrl+4. Moreover, it becomes unresponsive if ctrl+s is given in Ubuntu 16.04(normal in 14.04). It is observed in Apache Cassandra 3.11 and DSE 6.7.2 was: Cqlsh crashes with coredump when given ctrl+| or ctrl+\ or ctrl+4. Moreover it becomes unresponsive if ctrl+s is given. It is observed in apache cassandra 3.11 and dse 6.7.2 > coredump in cqlsh > - > > Key: CASSANDRA-15070 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15070 > Project: Cassandra > Issue Type: Bug > Components: Tool/cqlsh >Reporter: Chakravarthi Manepalli >Priority: Normal > Labels: easyfix > > Cqlsh crashes with core dump when given ctrl+| or ctrl+\ or ctrl+4. > Moreover, it becomes unresponsive if ctrl+s is given in Ubuntu 16.04(normal > in 14.04). > It is observed in Apache Cassandra 3.11 and DSE 6.7.2 -- 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-15070) coredump in cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-15070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chakravarthi Manepalli updated CASSANDRA-15070: --- Description: Cqlsh crashes with core dump when given ctrl+| or ctrl+\ or ctrl+4(same in 16.04 and 14.04). Moreover, it becomes unresponsive if ctrl+s is given in Ubuntu 16.04(normal in 14.04). It is observed in Apache Cassandra 3.11 and DSE 6.7.2 was: Cqlsh crashes with core dump when given ctrl+| or ctrl+\ or ctrl+4. Moreover, it becomes unresponsive if ctrl+s is given in Ubuntu 16.04(normal in 14.04). It is observed in Apache Cassandra 3.11 and DSE 6.7.2 > coredump in cqlsh > - > > Key: CASSANDRA-15070 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15070 > Project: Cassandra > Issue Type: Bug > Components: Tool/cqlsh >Reporter: Chakravarthi Manepalli >Priority: Normal > Labels: easyfix > > Cqlsh crashes with core dump when given ctrl+| or ctrl+\ or ctrl+4(same in > 16.04 and 14.04). > Moreover, it becomes unresponsive if ctrl+s is given in Ubuntu 16.04(normal > in 14.04). > It is observed in Apache Cassandra 3.11 and DSE 6.7.2 -- 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-15079) Secondary Index not returning complete data
[ https://issues.apache.org/jira/browse/CASSANDRA-15079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chakravarthi Manepalli updated CASSANDRA-15079: --- Description: The result response when we query using a secondary index does not give complete data. Some of the rows are missing. After dropping the index and creating it again, the query worked fine. Observation: The missed data entry is last edited 20 days ago. I suspect may be the data which is old is not getting indexed properly through secondary indexes. was: The result response when we query using a secondary index does not give complete data. Some of the rows are missing. Observation: The missed data entry is last edited 20 days ago. I suspect may be the data which is old is not getting indexed properly through secondary indexes. > Secondary Index not returning complete data > --- > > Key: CASSANDRA-15079 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15079 > Project: Cassandra > Issue Type: Bug > Components: Feature/2i Index >Reporter: Chakravarthi Manepalli >Priority: High > Labels: performance > Attachments: missing_data_cassandra.png > > > The result response when we query using a secondary index does not give > complete data. Some of the rows are missing. After dropping the index and > creating it again, the query worked fine. > Observation: The missed data entry is last edited 20 days ago. > I suspect may be the data which is old is not getting indexed properly > through secondary indexes. -- 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-15079) Secondary Index not returning complete data
[ https://issues.apache.org/jira/browse/CASSANDRA-15079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chakravarthi Manepalli updated CASSANDRA-15079: --- Since Version: 3.11.3 (was: 3.11.4) > Secondary Index not returning complete data > --- > > Key: CASSANDRA-15079 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15079 > Project: Cassandra > Issue Type: Bug > Components: Feature/2i Index >Reporter: Chakravarthi Manepalli >Priority: High > Labels: performance > Attachments: missing_data_cassandra.png > > > The result response when we query using a secondary index does not give > complete data. Some of the rows are missing. > Observation: The missed data entry is last edited 20 days ago. > I suspect may be the data which is old is not getting indexed properly > through secondary indexes. -- 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-15079) Secondary Index not returning complete data
[ https://issues.apache.org/jira/browse/CASSANDRA-15079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chakravarthi Manepalli updated CASSANDRA-15079: --- Summary: Secondary Index not returning complete data (was: Secondary Index not returning data) > Secondary Index not returning complete data > --- > > Key: CASSANDRA-15079 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15079 > Project: Cassandra > Issue Type: Bug > Components: Feature/2i Index >Reporter: Chakravarthi Manepalli >Priority: High > Labels: performance > Attachments: missing_data_cassandra.png > > > The result response when we query using a secondary index does not give > complete data. Some of the rows are missing. > Observation: The missed data entry is last edited 20 days ago. > I suspect may be the data which is old is not getting indexed properly > through secondary indexes. -- 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-15079) Secondary Index not returning data
[ https://issues.apache.org/jira/browse/CASSANDRA-15079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16810633#comment-16810633 ] Chakravarthi Manepalli commented on CASSANDRA-15079: Hi Cassandra Team, Currently we are trying to reproduce this issue. We were setting up a server to reproduce this issue. We will let you know if any results found. > Secondary Index not returning data > -- > > Key: CASSANDRA-15079 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15079 > Project: Cassandra > Issue Type: Bug > Components: Feature/2i Index >Reporter: Chakravarthi Manepalli >Priority: High > Labels: performance > Attachments: missing_data_cassandra.png > > > The result response when we query using a secondary index does not give > complete data. Some of the rows are missing. > Observation: The missed data entry is last edited 20 days ago. > I suspect may be the data which is old is not getting indexed properly > through secondary indexes. -- 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-15079) Secondary Index not returning data
Chakravarthi Manepalli created CASSANDRA-15079: -- Summary: Secondary Index not returning data Key: CASSANDRA-15079 URL: https://issues.apache.org/jira/browse/CASSANDRA-15079 Project: Cassandra Issue Type: Bug Components: Feature/2i Index Reporter: Chakravarthi Manepalli Attachments: missing_data_cassandra.png The result response when we query using a secondary index does not give complete data. Some of the rows are missing. Observation: The missed data entry is last edited 20 days ago. I suspect may be the data which is old is not getting indexed properly through secondary indexes. -- 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-15070) coredump in cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-15070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chakravarthi Manepalli updated CASSANDRA-15070: --- Severity: Low Discovered By: User Report Bug Category: Parent values: Availability(12983)Level 1 values: Response Crash(12991) Status: Open (was: Triage Needed) > coredump in cqlsh > - > > Key: CASSANDRA-15070 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15070 > Project: Cassandra > Issue Type: Bug > Components: Tool/cqlsh >Reporter: Chakravarthi Manepalli >Priority: Normal > Labels: easyfix > > Cqlsh crashes with coredump when given ctrl+| or ctrl+\ or ctrl+4. > Moreover it becomes unresponsive if ctrl+s is given. > It is observed in apache cassandra 3.11 and dse 6.7.2 -- 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-15070) coredump in cqlsh
Chakravarthi Manepalli created CASSANDRA-15070: -- Summary: coredump in cqlsh Key: CASSANDRA-15070 URL: https://issues.apache.org/jira/browse/CASSANDRA-15070 Project: Cassandra Issue Type: Bug Components: Tool/cqlsh Reporter: Chakravarthi Manepalli Cqlsh crashes with coredump when given ctrl+| or ctrl+\ or ctrl+4. Moreover it becomes unresponsive if ctrl+s is given. It is observed in apache cassandra 3.11 and dse 6.7.2 -- 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-14594) No validation for repeated fields in cqlsh and misbehaviour in data display
[ https://issues.apache.org/jira/browse/CASSANDRA-14594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597129#comment-16597129 ] Chakravarthi Manepalli commented on CASSANDRA-14594: hi [~blerer], can you please look into this issue? > No validation for repeated fields in cqlsh and misbehaviour in data display > --- > > Key: CASSANDRA-14594 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14594 > Project: Cassandra > Issue Type: Bug > Components: Tools > Environment: Operating System: Ubuntu 14.04(64 bit) (Image : > cqlshbug.png) > Operating System: ubuntu 16.04 (64 bit) (Image: > cqlsh_select_repeated_fields.png) > Apache cassandra version : 3.11.1 >Reporter: Chakravarthi Manepalli >Priority: Critical > Labels: easyfix, newbie > Attachments: cqlsh bug.png, cqlsh_select_repeated_fields.png > > > In a table, if the fields(columns) are repeated in select call, the > displaying information is not correct. -- 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-14594) No validation for repeated fields in cqlsh and misbehaviour in data display
[ https://issues.apache.org/jira/browse/CASSANDRA-14594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chakravarthi Manepalli updated CASSANDRA-14594: --- Tester: (was: Harini Vaidhyanathan) > No validation for repeated fields in cqlsh and misbehaviour in data display > --- > > Key: CASSANDRA-14594 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14594 > Project: Cassandra > Issue Type: Bug > Components: Tools > Environment: Operating System: Ubuntu 14.04(64 bit) (Image : > cqlshbug.png) > Operating System: ubuntu 16.04 (64 bit) (Image: > cqlsh_select_repeated_fields.png) > Apache cassandra version : 3.11.1 >Reporter: Chakravarthi Manepalli >Priority: Critical > Labels: easyfix, newbie > Attachments: cqlsh bug.png, cqlsh_select_repeated_fields.png > > > In a table, if the fields(columns) are repeated in select call, the > displaying information is not correct. -- 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-14594) No validation for repeated fields in cqlsh and misbehaviour in data display
[ https://issues.apache.org/jira/browse/CASSANDRA-14594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chakravarthi Manepalli updated CASSANDRA-14594: --- Tester: Harini Vaidhyanathan Status: Awaiting Feedback (was: Open) Hi harini, can you please let me know regarding the status of my bug report? > No validation for repeated fields in cqlsh and misbehaviour in data display > --- > > Key: CASSANDRA-14594 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14594 > Project: Cassandra > Issue Type: Bug > Components: Tools > Environment: Operating System: Ubuntu 14.04(64 bit) (Image : > cqlshbug.png) > Operating System: ubuntu 16.04 (64 bit) (Image: > cqlsh_select_repeated_fields.png) > Apache cassandra version : 3.11.1 >Reporter: Chakravarthi Manepalli >Priority: Critical > Labels: easyfix, newbie > Attachments: cqlsh bug.png, cqlsh_select_repeated_fields.png > > > In a table, if the fields(columns) are repeated in select call, the > displaying information is not correct. -- 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-11429) DROP TABLE IF EXISTS fails against table with similar name
[
https://issues.apache.org/jira/browse/CASSANDRA-11429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571478#comment-16571478
]
Chakravarthi Manepalli commented on CASSANDRA-11429:
I am creating the tables concurrently, and i faced the similar issue but in the
reverse manner. I have got the entry in system_schema keyspace about the index,
but the index is not getting created.
Then, I stopped the node and cleared data folder and started cassandra again
and loaded the schema loader and I faced the same issue again. !column family
mismatch.png!
> DROP TABLE IF EXISTS fails against table with similar name
> --
>
> Key: CASSANDRA-11429
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11429
> Project: Cassandra
> Issue Type: Bug
> Components: Core
>Reporter: Sotirios Delimanolis
>Priority: Major
> Attachments: column family mismatch.png
>
>
> We had a table named {{our_keyspace.native_address_book_uploads_cache}} (note
> the uploads*) which we dropped. We then created a new table named
> {{our_keyspace.native_address_book_upload_cache}} (note the upload*).
> We have a patching component that applies commands to prepare the schema
> using the C# driver. When we deploy, it tries to execute
> {noformat}
> DROP TABLE IF NOT EXISTS our_keyspace.native_address_book_uploads_cache;
> {noformat}
> This fails with
> {noformat}
> Caught an exception Cassandra.ServerErrorException:
> java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ConfigurationException: Column family ID
> mismatch (found c712a590-f194-11e5-891d-2d7ca98597ba; expected
> b8b40ed0-f194-11e5-b481-d944f7ad0ce3)
> {noformat}
> showing the Cassandra Java exception through the C# driver. Note the
> {{found}} cf_id of {{c712a590-f194-11e5-891d-2d7ca98597ba}}.
> I can reproduce this with {{cqlsh}}.
> {noformat}
> selimanolis$ cqlsh
> Connected to Default Cluster at hostname:9042.
> [cqlsh 5.0.1 | Cassandra 2.1.13-SNAPSHOT | CQL spec 3.2.1 | Native protocol
> v3]
> Use HELP for help.
> cqlsh> SELECT cf_id from system.schema_columnfamilies where keyspace_name =
> 'our_keyspace' and columnfamily_name ='native_address_book_uploads_cache';
> keyspace_name | columnfamily_name | bloom_filter_fp_chance | caching | cf_id
> | column_aliases | comment | compaction_strategy_class |
> compaction_strategy_options | comparator | compression_parameters |
> default_time_to_live | default_validator | dropped_columns | gc_grace_seconds
> | index_interval | is_dense | key_aliases | key_validator |
> local_read_repair_chance | max_compaction_threshold | max_index_interval |
> memtable_flush_period_in_ms | min_compaction_threshold | min_index_interval |
> read_repair_chance | speculative_retry | subcomparator | type | value_alias
> ---+---++-+---++-+---+-+++--+---+-+--++--+-+---+--+--++-+--+++---+---+--+-
> (0 rows)
> cqlsh> SELECT cf_id from system.schema_columnfamilies where keyspace_name =
> 'our_keyspace' and columnfamily_name ='native_address_book_upload_cache';
> cf_id
> --
> c712a590-f194-11e5-891d-2d7ca98597ba
> (1 rows)
> cqlsh> drop TABLE IF EXISTS our_keyspace.native_address_book_uploads_cache;
> InvalidRequest: code=2200 [Invalid query] message="No keyspace has been
> specified. USE a keyspace, or explicitly specify keyspace.tablename"
> cqlsh> drop TABLE IF EXISTS our_keyspace.native_address_book_uploads_cache;
> ServerError: message="java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ConfigurationException: Column family ID
> mismatch (found c712a590-f194-11e5-891d-2d7ca98597ba; expected
> b8b40ed0-f194-11e5-b481-d944f7ad0ce3)">
> cqlsh>
> {noformat}
> The table doesn't exist. A table that has a similar name does. You'll notice
> that the new table has same {{cf_id}} found in the error message above. Why
> does Cassandra confuse the two?
> Our expectation is for the {{DROP TABLE IF EXISTS}} to silently succeed.
> Similarly, we expect a {{DROP TABLE}} to fail because the table doesn't
> exist. That's not what happens if you see below
> {noformat}
> cqlsh> DROP TABLE
[jira] [Updated] (CASSANDRA-11429) DROP TABLE IF EXISTS fails against table with similar name
[
https://issues.apache.org/jira/browse/CASSANDRA-11429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chakravarthi Manepalli updated CASSANDRA-11429:
---
Attachment: column family mismatch.png
> DROP TABLE IF EXISTS fails against table with similar name
> --
>
> Key: CASSANDRA-11429
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11429
> Project: Cassandra
> Issue Type: Bug
> Components: Core
>Reporter: Sotirios Delimanolis
>Priority: Major
> Attachments: column family mismatch.png
>
>
> We had a table named {{our_keyspace.native_address_book_uploads_cache}} (note
> the uploads*) which we dropped. We then created a new table named
> {{our_keyspace.native_address_book_upload_cache}} (note the upload*).
> We have a patching component that applies commands to prepare the schema
> using the C# driver. When we deploy, it tries to execute
> {noformat}
> DROP TABLE IF NOT EXISTS our_keyspace.native_address_book_uploads_cache;
> {noformat}
> This fails with
> {noformat}
> Caught an exception Cassandra.ServerErrorException:
> java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ConfigurationException: Column family ID
> mismatch (found c712a590-f194-11e5-891d-2d7ca98597ba; expected
> b8b40ed0-f194-11e5-b481-d944f7ad0ce3)
> {noformat}
> showing the Cassandra Java exception through the C# driver. Note the
> {{found}} cf_id of {{c712a590-f194-11e5-891d-2d7ca98597ba}}.
> I can reproduce this with {{cqlsh}}.
> {noformat}
> selimanolis$ cqlsh
> Connected to Default Cluster at hostname:9042.
> [cqlsh 5.0.1 | Cassandra 2.1.13-SNAPSHOT | CQL spec 3.2.1 | Native protocol
> v3]
> Use HELP for help.
> cqlsh> SELECT cf_id from system.schema_columnfamilies where keyspace_name =
> 'our_keyspace' and columnfamily_name ='native_address_book_uploads_cache';
> keyspace_name | columnfamily_name | bloom_filter_fp_chance | caching | cf_id
> | column_aliases | comment | compaction_strategy_class |
> compaction_strategy_options | comparator | compression_parameters |
> default_time_to_live | default_validator | dropped_columns | gc_grace_seconds
> | index_interval | is_dense | key_aliases | key_validator |
> local_read_repair_chance | max_compaction_threshold | max_index_interval |
> memtable_flush_period_in_ms | min_compaction_threshold | min_index_interval |
> read_repair_chance | speculative_retry | subcomparator | type | value_alias
> ---+---++-+---++-+---+-+++--+---+-+--++--+-+---+--+--++-+--+++---+---+--+-
> (0 rows)
> cqlsh> SELECT cf_id from system.schema_columnfamilies where keyspace_name =
> 'our_keyspace' and columnfamily_name ='native_address_book_upload_cache';
> cf_id
> --
> c712a590-f194-11e5-891d-2d7ca98597ba
> (1 rows)
> cqlsh> drop TABLE IF EXISTS our_keyspace.native_address_book_uploads_cache;
> InvalidRequest: code=2200 [Invalid query] message="No keyspace has been
> specified. USE a keyspace, or explicitly specify keyspace.tablename"
> cqlsh> drop TABLE IF EXISTS our_keyspace.native_address_book_uploads_cache;
> ServerError: message="java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ConfigurationException: Column family ID
> mismatch (found c712a590-f194-11e5-891d-2d7ca98597ba; expected
> b8b40ed0-f194-11e5-b481-d944f7ad0ce3)">
> cqlsh>
> {noformat}
> The table doesn't exist. A table that has a similar name does. You'll notice
> that the new table has same {{cf_id}} found in the error message above. Why
> does Cassandra confuse the two?
> Our expectation is for the {{DROP TABLE IF EXISTS}} to silently succeed.
> Similarly, we expect a {{DROP TABLE}} to fail because the table doesn't
> exist. That's not what happens if you see below
> {noformat}
> cqlsh> DROP TABLE our_keyspace.native_address_book_uploads_cache;
> ServerError: message="java.lang.RuntimeException: java.util.concurrent.ExecutionException:
> java.lang.RuntimeException:
> org.apache.cassandra.exceptions.ConfigurationException: Column family ID
> mismatch (found c712a590-f194-11e5-891d-2d7ca98597ba; expected
> b8b40ed0-f194-11e5-b481-d944f7ad0ce3)">
> cqlsh> DROP TABLE
[jira] [Created] (CASSANDRA-14594) No validation for repeated fields in cqlsh and misbehaviour in data display
Chakravarthi Manepalli created CASSANDRA-14594: -- Summary: No validation for repeated fields in cqlsh and misbehaviour in data display Key: CASSANDRA-14594 URL: https://issues.apache.org/jira/browse/CASSANDRA-14594 Project: Cassandra Issue Type: Bug Components: Tools Environment: Operating System: Ubuntu 14.04(64 bit) (Image : cqlshbug.png) Operating System: ubuntu 16.04 (64 bit) (Image: cqlsh_select_repeated_fields.png) Apache cassandra version : 3.11.1 Reporter: Chakravarthi Manepalli Attachments: cqlsh bug.png, cqlsh_select_repeated_fields.png In a table, if the fields(columns) are repeated in select call, the displaying information is not correct. -- 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
