[jira] [Created] (CASSANDRA-13563) Startup flag -p not provide process Id file
Sachith Prasanna Dickwella created CASSANDRA-13563: -- Summary: Startup flag -p not provide process Id file Key: CASSANDRA-13563 URL: https://issues.apache.org/jira/browse/CASSANDRA-13563 Project: Cassandra Issue Type: Bug Components: Lifecycle Environment: Windows 10 Pro 64bit, JDK 8 Update 112, Core i7/16 GB RAM Laptop Reporter: Sachith Prasanna Dickwella Priority: Minor Fix For: 3.11.x 'cassandra -p filename' command not creates a 'filename' with process id and tried with different locations to the file with absolute paths and relative paths and yet not fixed. My user account has administrator privileges it might not be permission issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13072) Cassandra failed to run on Linux-aarch64
[ https://issues.apache.org/jira/browse/CASSANDRA-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030762#comment-16030762 ] Benjamin Lerer commented on CASSANDRA-13072: I think we have to be a bit pragmatic. If upgrading JNA do not cause any problem in our test environment and that is allow some people to start C* on Linux-aarch64, without having to change the jar manually themselves, I do not see a good reason of not doing it. I am not telling that we are from now on supporting Linux-aarch64. It is just that in the case of this ticket the risk associated to the change is pretty low and the benefit is high for some people. > Cassandra failed to run on Linux-aarch64 > > > Key: CASSANDRA-13072 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13072 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: Hardware: ARM aarch64 > OS: Ubuntu 16.04.1 LTS >Reporter: Jun He >Assignee: Benjamin Lerer > Labels: incompatible > Attachments: compat_report.html > > > Steps to reproduce: > 1. Download cassandra latest source > 2. Build it with "ant" > 3. Run with "./bin/cassandra". Daemon is crashed with following error message: > {quote} > INFO 05:30:21 Initializing system.schema_functions > INFO 05:30:21 Initializing system.schema_aggregates > ERROR 05:30:22 Exception in thread Thread[MemtableFlushWriter:1,5,main] > java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native > at > org.apache.cassandra.utils.memory.MemoryUtil.allocate(MemoryUtil.java:97) > ~[main/:na] > at org.apache.cassandra.io.util.Memory.(Memory.java:74) > ~[main/:na] > at org.apache.cassandra.io.util.SafeMemory.(SafeMemory.java:32) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.(CompressionMetadata.java:316) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.open(CompressionMetadata.java:330) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressedSequentialWriter.(CompressedSequentialWriter.java:76) > ~[main/:na] > at > org.apache.cassandra.io.util.SequentialWriter.open(SequentialWriter.java:163) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigTableWriter.(BigTableWriter.java:73) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigFormat$WriterFactory.open(BigFormat.java:93) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.SSTableWriter.create(SSTableWriter.java:96) > ~[main/:na] > at > org.apache.cassandra.io.sstable.SimpleSSTableMultiWriter.create(SimpleSSTableMultiWriter.java:114) > ~[main/:na] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.createSSTableMultiWriter(AbstractCompactionStrategy.java:519) > ~[main/:na] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.createSSTableMultiWriter(CompactionStrategyManager.java:497) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore.createSSTableMultiWriter(ColumnFamilyStore.java:480) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.createFlushWriter(Memtable.java:439) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.writeSortedContents(Memtable.java:371) > ~[main/:na] > at org.apache.cassandra.db.Memtable.flush(Memtable.java:332) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1054) > ~[main/:na] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > ~[na:1.8.0_111] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > ~[na:1.8.0_111] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_111] > {quote} > Analyze: > This issue is caused by bundled jna-4.0.0.jar which doesn't come with aarch64 > native support. Replace lib/jna-4.0.0.jar with jna-4.2.0.jar from > http://central.maven.org/maven2/net/java/dev/jna/jna/4.2.0/ can fix this > problem. > Attached is the binary compatibility report of jna.jar between 4.0 and 4.2. > The result is good (97.4%). So is there possibility to upgrade jna to 4.2.0 > in upstream? Should there be any kind of tests to execute, please kindly > point me. Thanks a lot. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030763#comment-16030763 ] Stefania commented on CASSANDRA-13559: -- Here are the patches for 3.0 and 3.11: [patch for 3.0|https://github.com/stef1927/cassandra/tree/13559-3.0] [patch for 3.11|https://github.com/stef1927/cassandra/tree/13559-3.11] Since we don't need it for 4.0, I decided to keep the initial patch suggested by [~jay.zhuang], I merely added some comments and the entry into CHANGES.txt. I'm running the tests for 3.0 on our internal CI hosts. I will post a comment when the results are available. Regarding the upgrade from 3.0.13 to 3.0.14, I don't think there is much we can do without a bump in the messaging version. I would tend to think we should release 3.0.14 with the patch asap. I also wonder why we did not notice this at all in our [upgrade tests|http://cassci.datastax.com/job/cassandra-3.0_dtest_upgrade/lastCompletedBuild/testReport/]. For 3.11 we definitely need the patch since we haven't released it yet; whilst for 4.0 we don't need it because the messaging version has been bumped and hence the schema version will not be compared. Regarding the `NoSuchFieldError` in the ticket description, it doesn't make much sense to me and I cannot reproduce it. The node starts without problems, perhaps a build issue? > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030763#comment-16030763 ] Stefania edited comment on CASSANDRA-13559 at 5/31/17 7:23 AM: --- Here are the patches for 3.0 and 3.11: [patch for 3.0|https://github.com/stef1927/cassandra/tree/13559-3.0] [patch for 3.11|https://github.com/stef1927/cassandra/tree/13559-3.11] Since we don't need it for 4.0, I decided to keep the initial patch suggested by [~jay.zhuang], I merely added some comments and the entry into CHANGES.txt. I'm running the tests for 3.0 on our internal CI hosts. I will post a comment when the results are available. Regarding the upgrade from 3.0.13 to 3.0.14, I don't think there is much we can do without a bump in the messaging version. I would tend to think we should release 3.0.14 with the patch asap. I also wonder why we did not notice this at all in our [upgrade tests|http://cassci.datastax.com/job/cassandra-3.0_dtest_upgrade/lastCompletedBuild/testReport/]. For 3.11 we definitely need the patch since we haven't released it yet; whilst for 4.0 we don't need it because the messaging version has been bumped and hence the schema version will not be compared. Regarding the {{NoSuchFieldError}} in the ticket description, it doesn't make much sense to me and I cannot reproduce it. The node starts without problems, perhaps a build issue? was (Author: stefania): Here are the patches for 3.0 and 3.11: [patch for 3.0|https://github.com/stef1927/cassandra/tree/13559-3.0] [patch for 3.11|https://github.com/stef1927/cassandra/tree/13559-3.11] Since we don't need it for 4.0, I decided to keep the initial patch suggested by [~jay.zhuang], I merely added some comments and the entry into CHANGES.txt. I'm running the tests for 3.0 on our internal CI hosts. I will post a comment when the results are available. Regarding the upgrade from 3.0.13 to 3.0.14, I don't think there is much we can do without a bump in the messaging version. I would tend to think we should release 3.0.14 with the patch asap. I also wonder why we did not notice this at all in our [upgrade tests|http://cassci.datastax.com/job/cassandra-3.0_dtest_upgrade/lastCompletedBuild/testReport/]. For 3.11 we definitely need the patch since we haven't released it yet; whilst for 4.0 we don't need it because the messaging version has been bumped and hence the schema version will not be compared. Regarding the `NoSuchFieldError` in the ticket description, it doesn't make much sense to me and I cannot reproduce it. The node starts without problems, perhaps a build issue? > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.
[jira] [Comment Edited] (CASSANDRA-13072) Cassandra failed to run on Linux-aarch64
[ https://issues.apache.org/jira/browse/CASSANDRA-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030762#comment-16030762 ] Benjamin Lerer edited comment on CASSANDRA-13072 at 5/31/17 7:23 AM: - I think we have to be a bit pragmatic. If upgrading JNA do not cause any problem in our test environment and that it allows some people to start C* on Linux-aarch64, without having to change the jar manually themselves, I do not see a good reason of not doing it. I am not telling that we are, from now on, supporting Linux-aarch64. It is just that in the case of this ticket the risk associated to the change is pretty low and the benefit is high for some people. was (Author: blerer): I think we have to be a bit pragmatic. If upgrading JNA do not cause any problem in our test environment and that is allow some people to start C* on Linux-aarch64, without having to change the jar manually themselves, I do not see a good reason of not doing it. I am not telling that we are from now on supporting Linux-aarch64. It is just that in the case of this ticket the risk associated to the change is pretty low and the benefit is high for some people. > Cassandra failed to run on Linux-aarch64 > > > Key: CASSANDRA-13072 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13072 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: Hardware: ARM aarch64 > OS: Ubuntu 16.04.1 LTS >Reporter: Jun He >Assignee: Benjamin Lerer > Labels: incompatible > Attachments: compat_report.html > > > Steps to reproduce: > 1. Download cassandra latest source > 2. Build it with "ant" > 3. Run with "./bin/cassandra". Daemon is crashed with following error message: > {quote} > INFO 05:30:21 Initializing system.schema_functions > INFO 05:30:21 Initializing system.schema_aggregates > ERROR 05:30:22 Exception in thread Thread[MemtableFlushWriter:1,5,main] > java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native > at > org.apache.cassandra.utils.memory.MemoryUtil.allocate(MemoryUtil.java:97) > ~[main/:na] > at org.apache.cassandra.io.util.Memory.(Memory.java:74) > ~[main/:na] > at org.apache.cassandra.io.util.SafeMemory.(SafeMemory.java:32) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.(CompressionMetadata.java:316) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.open(CompressionMetadata.java:330) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressedSequentialWriter.(CompressedSequentialWriter.java:76) > ~[main/:na] > at > org.apache.cassandra.io.util.SequentialWriter.open(SequentialWriter.java:163) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigTableWriter.(BigTableWriter.java:73) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigFormat$WriterFactory.open(BigFormat.java:93) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.SSTableWriter.create(SSTableWriter.java:96) > ~[main/:na] > at > org.apache.cassandra.io.sstable.SimpleSSTableMultiWriter.create(SimpleSSTableMultiWriter.java:114) > ~[main/:na] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.createSSTableMultiWriter(AbstractCompactionStrategy.java:519) > ~[main/:na] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.createSSTableMultiWriter(CompactionStrategyManager.java:497) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore.createSSTableMultiWriter(ColumnFamilyStore.java:480) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.createFlushWriter(Memtable.java:439) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.writeSortedContents(Memtable.java:371) > ~[main/:na] > at org.apache.cassandra.db.Memtable.flush(Memtable.java:332) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1054) > ~[main/:na] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > ~[na:1.8.0_111] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > ~[na:1.8.0_111] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_111] > {quote} > Analyze: > This issue is caused by bundled jna-4.0.0.jar which doesn't come with aarch64 > native support. Replace lib/jna-4.0.0.jar with jna-4.2.0.jar from > http://central.maven.org/maven2/net/java/dev/jna/jna/4.2.0/ can fix this > problem. > Attached is the binary compatibility report of jna.jar between 4.0 and 4.2. > The result is good (97.4%). So is there possibilit
[jira] [Updated] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefania updated CASSANDRA-13559: - Status: Patch Available (was: In Progress) > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-13564) Mismatch Documentation on MATERIALIZE VIEW
Nick Hryhoriev created CASSANDRA-13564: -- Summary: Mismatch Documentation on MATERIALIZE VIEW Key: CASSANDRA-13564 URL: https://issues.apache.org/jira/browse/CASSANDRA-13564 Project: Cassandra Issue Type: Improvement Components: Documentation and Website Environment: 3.10 Reporter: Nick Hryhoriev During create MATERIALIZED VIEW with out cluster key. I've got exception "No columns are defined for Materialized View other than primary key" Does it expected behave? Because i can't find nothing about this in Documentation. But this check exist in code. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13564) Mismatch Documentation on MATERIALIZE VIEW
[ https://issues.apache.org/jira/browse/CASSANDRA-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Hryhoriev updated CASSANDRA-13564: --- Labels: doc-impacting (was: ) > Mismatch Documentation on MATERIALIZE VIEW > -- > > Key: CASSANDRA-13564 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13564 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website > Environment: 3.10 >Reporter: Nick Hryhoriev > Labels: doc-impacting > > During create MATERIALIZED VIEW with out cluster key. > I've got exception "No columns are defined for Materialized View other than > primary key" > Does it expected behave? Because i can't find nothing about this in > Documentation. But this check exist in code. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-8272) 2ndary indexes can return stale data
[ https://issues.apache.org/jira/browse/CASSANDRA-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030870#comment-16030870 ] Sylvain Lebresne commented on CASSANDRA-8272: - bq. So, if the query limit requires n rows, we should return not more than {{n}} rows satisfying the filter, and *all* the rows not satisfying the index but being pointed by a deleted index entry. No, I don't think we have to return *all* the rows not satisfying the index. I believe only returning those that are *before* the {{n}} th "valid" entry is enough. I don't think it's different from how we handle tombstones here: we don't return all tombstones, just the ones before the {{n}} th live results. Note that both with those new "invalid" entries and with tombstones, it's possible that post-resolution on the coordinator we end up being short on results. That is, a "valid" result from A is canceled by a tombstone/"invalid" result of B and vice-versa and we end up with less results than requested. But that's where the short-read protection from {{DataResolver}} kicks in. > 2ndary indexes can return stale data > > > Key: CASSANDRA-8272 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8272 > Project: Cassandra > Issue Type: Bug >Reporter: Sylvain Lebresne >Assignee: Andrés de la Peña > Fix For: 3.0.x > > > When replica return 2ndary index results, it's possible for a single replica > to return a stale result and that result will be sent back to the user, > potentially failing the CL contract. > For instance, consider 3 replicas A, B and C, and the following situation: > {noformat} > CREATE TABLE test (k int PRIMARY KEY, v text); > CREATE INDEX ON test(v); > INSERT INTO test(k, v) VALUES (0, 'foo'); > {noformat} > with every replica up to date. Now, suppose that the following queries are > done at {{QUORUM}}: > {noformat} > UPDATE test SET v = 'bar' WHERE k = 0; > SELECT * FROM test WHERE v = 'foo'; > {noformat} > then, if A and B acknowledge the insert but C respond to the read before > having applied the insert, then the now stale result will be returned (since > C will return it and A or B will return nothing). > A potential solution would be that when we read a tombstone in the index (and > provided we make the index inherit the gcGrace of it's parent CF), instead of > skipping that tombstone, we'd insert in the result a corresponding range > tombstone. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13149) AssertionError prepending to a list
[ https://issues.apache.org/jira/browse/CASSANDRA-13149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030903#comment-16030903 ] Sylvain Lebresne commented on CASSANDRA-13149: -- Your analysis does make sense. The concern with creating one instance per operation however is that one of the goal here is to avoid ever generating the same UUID twice, especially among competing operations. Basically, if someone do 2 concurrent prepend on a given list, we can't guarantee which one will end up first in the list, but we do want to ensure both elements ends up in the list, not that one gets thrown away because both operation happen to generate the same UUID. Overall, there appears to be 2 problems: 1) the broken reliance on {{System#currentTimeMillis}} being monotonic and 2) the fact that the way we use the {{time}} is not thread-safe between operations. For 1), we can do something like we do in {{UUIDGen}}, basically by having {{getNext}} handle the case of {{millis > current.millis}} by ignoring {{millis}} and using {{current.millis}} instead (so if {{System#currentTimeMillis}} goes back in time, rely on the last time saved until the time catches up to that last saved value; we probably want to change how we handle the case where {{current.nanos == 0}} though, by decreasing {{millis}} rather than bailing out and generating the same time as that's wrong). For 2), I suspect the simplest approach could be to change {{getNext()}} to be able to general {{n}} values atomically instead of one. Each operation would then grab as many value it needs upfront and use them. A minor benefit being that if 2 concurrent prepend are done concurrently, all of the value from each update would end up "together", which feels nicer (gives some sense of isolation; we may even want to make this work for append too). > AssertionError prepending to a list > --- > > Key: CASSANDRA-13149 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13149 > Project: Cassandra > Issue Type: Bug > Components: CQL > Environment: 3.0.8 >Reporter: Steven Warren > > Prepending to a list produces the following AssertionError randomly. Changing > the update to append (and sort in the client) works around the issue. > {code} > java.lang.AssertionError: null > at > org.apache.cassandra.cql3.Lists$PrecisionTime.getNext(Lists.java:275) > ~[apache-cassandra-3.0.8.jar:3.0.8] > at org.apache.cassandra.cql3.Lists$Prepender.execute(Lists.java:430) > ~[apache-cassandra-3.0.8.jar:3.0.8] > at > org.apache.cassandra.cql3.statements.UpdateStatement.addUpdateForKey(UpdateStatement.java:94) > ~[apache-cassandra-3.0.8.jar:3.0.8] > at > org.apache.cassandra.cql3.statements.ModificationStatement.addUpdates(ModificationStatement.java:682) > ~[apache-cassandra-3.0.8.jar:3.0.8] > at > org.apache.cassandra.cql3.statements.ModificationStatement.getMutations(ModificationStatement.java:613) > ~[apache-cassandra-3.0.8.jar:3.0.8] > at > org.apache.cassandra.cql3.statements.ModificationStatement.executeWithoutCondition(ModificationStatement.java:420) > ~[apache-cassandra-3.0.8.jar:3.0.8] > at > org.apache.cassandra.cql3.statements.ModificationStatement.execute(ModificationStatement.java:408) > ~[apache-cassandra-3.0.8.jar:3.0.8] > at > org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:206) > ~[apache-cassandra-3.0.8.jar:3.0.8] > at > org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:487) > ~[apache-cassandra-3.0.8.jar:3.0.8] > at > org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:464) > ~[apache-cassandra-3.0.8.jar:3.0.8] > at > org.apache.cassandra.transport.messages.ExecuteMessage.execute(ExecuteMessage.java:130) > ~[apache-cassandra-3.0.8.jar:3.0.8] > at > org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:507) > [apache-cassandra-3.0.8.jar:3.0.8] > at > org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:401) > [apache-cassandra-3.0.8.jar:3.0.8] > at > io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105) > [netty-all-4.0.23.Final.jar:4.0.23.Final] > at > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:333) > [netty-all-4.0.23.Final.jar:4.0.23.Final] > at > io.netty.channel.AbstractChannelHandlerContext.access$700(AbstractChannelHandlerContext.java:32) > [netty-all-4.0.23.Final.jar:4.0.23.Final] > at > io.netty.channel.AbstractChannelHandlerContext$8.run(AbstractChannelHandlerContext.java:324) > [netty-all-4.0.23.Final.jar:4.0.23.Final] > at > java.util.concurrent.Executors$RunnableAdapter.ca
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030905#comment-16030905 ] Stefania commented on CASSANDRA-13559: -- The test results look good, no failures for the unit tests and 5 known failures for the dtests. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Stupp updated CASSANDRA-13559: - Reviewer: Robert Stupp > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030935#comment-16030935 ] Robert Stupp commented on CASSANDRA-13559: -- +1, assuming tests look good. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Stupp updated CASSANDRA-13559: - Status: Ready to Commit (was: Patch Available) > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030973#comment-16030973 ] Stefano Ortolani commented on CASSANDRA-13559: -- [~Stefania], could you please elaborate a bit further on the .13-.14 upgrade path? I am running .13 in production and I am quite concerned what to expect during the next round of upgrades. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13444) Fast and garbage-free Streaming Histogram
[ https://issues.apache.org/jira/browse/CASSANDRA-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031102#comment-16031102 ] Fuud commented on CASSANDRA-13444: -- [~jasobrown] Anything else preventing PR from merge? > Fast and garbage-free Streaming Histogram > - > > Key: CASSANDRA-13444 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13444 > Project: Cassandra > Issue Type: Improvement > Components: Compaction >Reporter: Fuud >Assignee: Fuud > Fix For: 4.x > > Attachments: results.csv, results.xlsx > > > StreamingHistogram is cause of high cpu usage and GC pressure. > It was improved at CASSANDRA-13038 by introducing intermediate buffer to try > accumulate different values into the big map before merging them into smaller > one. > But there was not enought for TTL's distributed within large time. Rounding > (also introduced at 13038) can help but it reduce histogram precision > specially in case where TTL's does not distributed uniformly. > There are several improvements that can help to reduce cpu and gc usage. Them > all included in the pool-request as separate revisions thus you can test them > independently. > Improvements list: > # Use Map.computeIfAbsent instead of get->checkIfNull->put chain. In this way > "add-or-accumulate" operation takes one map operation instead of two. But > this method (default-defined in interface Map) is overriden in HashMap but > not in TreeMap. Thus I changed spool type to HashMap. > # As we round incoming values to _roundSeconds_ we can also round value on > merge. It will enlarge hit rate for bin operations. > # Because we inserted only integers into Histogram and rounding values to > integers we can use *int* type everywhere. > # Histogram takes huge amount of time merging values. In merge method largest > amount of time taken by finding nearest points. It can be eliminated by > holding additional TreeSet with differences, sorted from smalest to greatest. > # Because we know max size of _bin_ and _differences_ maps we can replace > them with sorted arrays. Search can be done with _Arrays.binarySearch_ and > insertion/deletions can be done by _System.arraycopy_. Also it helps to merge > some operations into one. > # Because spool map is also limited we can replace it with open address > primitive map. It's finaly reduce allocation rate to zero. > You can see gain given by each step in the attached file. First number is > time for one benchmark invocation and second - is allocation rate in Mb per > operation. > Dependends of payload time is reduced up to 90%. > Overall gain: > |.|.|Payload/SpoolSize|.|.|.|% from original > |.|.|.|original|.|optimized| > |.|.|secondInMonth/0|.|.|.| > |time ms/op|.|.|10747,684|.|5545,063|51,6 > |allocation Mb/op|.|.|2441,38858|.|0,002105713|0 > |.|.|.|.|.|.| > |.|.|secondInMonth/1000|.|.|.| > |time ms/op|.|.|8988,578|.|5791,179|64,4 > |allocation Mb/op|.|.|2440,951141|.|0,017715454|0 > |.|.|.|.|.|.| > |.|.|secondInMonth/1|.|.|.| > |time ms/op|.|.|10711,671|.|5765,243|53,8 > |allocation Mb/op|.|.|2437,022537|.|0,264083862|0 > |.|.|.|.|.|.| > |.|.|secondInMonth/10|.|.|.| > |time ms/op|.|.|13001,841|.|5638,069|43,4 > |allocation Mb/op|.|.|2396,947113|.|2,003662109|0,1 > |.|.|.|.|.|.| > |.|.|secondInDay/0|.|.|.| > |time ms/op|.|.|10381,833|.|5497,804|53 > |allocation Mb/op|.|.|2441,166107|.|0,002105713|0 > |.|.|.|.|.|.| > |.|.|secondInDay/1000|.|.|.| > |time ms/op|.|.|8522,157|.|5929,871|69,6 > |allocation Mb/op|.|.|1973,112381|.|0,017715454|0 > |.|.|.|.|.|.| > |.|.|secondInDay/1|.|.|.| > |time ms/op|.|.|10234,978|.|5480,077|53,5 > |allocation Mb/op|.|.|2306,057404|.|0,262969971|0 > |.|.|.|.|.|.| > |.|.|secondInDay/10|.|.|.| > |time ms/op|.|.|2971,178|.|139,079|4,7 > |allocation Mb/op|.|.|172,1276245|.|2,001721191|1,2 > |.|.|.|.|.|.| > |.|.|secondIn3Hour/0|.|.|.| > |time ms/op|.|.|10663,123|.|5605,672|52,6 > |allocation Mb/op|.|.|2439,456818|.|0,002105713|0 > |.|.|.|.|.|.| > |.|.|secondIn3Hour/1000|.|.|.| > |time ms/op|.|.|9029,788|.|5838,618|64,7 > |allocation Mb/op|.|.|2331,839249|.|0,180664063|0 > |.|.|.|.|.|.| > |.|.|secondIn3Hour/1|.|.|.| > |time ms/op|.|.|4862,409|.|89,001|1,8 > |allocation Mb/op|.|.|965,4871887|.|0,251711652|0 > |.|.|.|.|.|.| > |.|.|secondIn3Hour/10|.|.|.| > |time ms/op|.|.|1484,454|.|95,044|6,4 > |allocation Mb/op|.|.|153,2464722|.|2,001712809|1,3 > |.|.|.|.|.|.| > |.|.|secondInMin/0|.|.|.| > |time ms/op|.|.|875,118|.|424,11|48,5 > |allocation Mb/op|.|.|610,3554993|.|0,001776123|0 > |.|.|.|.|.|.| > |.|.|secondInMin/1000|.|.|.| > |time ms/op|.|.|568,7|.|84,208|14,8 > |allocation Mb/op|.|.|0,007598114|.|0,01810023|238,2 > |.|.|.|.|.|.| > |.|.|secondInMin/1|.|.|.| > |time ms/op|.|.|573,595|.|83,862|14,6 > |allocation Mb/op|.|.|0,00759735
[jira] [Commented] (CASSANDRA-13540) QUORUM CL is used for new superuser
[ https://issues.apache.org/jira/browse/CASSANDRA-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031101#comment-16031101 ] Sam Tunnicliffe commented on CASSANDRA-13540: - [~denno] are you sure that's a response to a request using your new superuser credentials as {{org.apache.cassandra.auth.PasswordAuthenticator}} should definitely only issue queries at {{QUORUM}} for the {{cassandra}} user Are there any corresponding errors in the server log when you attempt to log in with the new user? Are you still able to use the default superuser credentials? If rf=2, then at least 1 node must be partitioned from the one you're logging into, what happens when there are no nodes being reported {{DOWN}}? > QUORUM CL is used for new superuser > --- > > Key: CASSANDRA-13540 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13540 > Project: Cassandra > Issue Type: Bug > Components: Distributed Metadata >Reporter: Dennis Noordzij > > After bootstrapping Cassandra, we're creating a new superuser, and setting RF > of system_auth keyspace to 2, NetworkTopologyStrategy. Then a nodetool repair > on the system_auth KS. > Documentation says > {quote} > The system_auth keyspace uses a QUORUM consistency level when checking > authentication for the default cassandra user. For all other users created, > superuser or otherwise, a LOCAL_ONE consistency level is used for > authenticating. > {quote} > But for my new superuser, new node members are rejected because QUORUM CL > can't be achieved: > {code} > May 19th 2017, 17:40:14.462 Connection error: ('Unable to connect to any > servers', {'xx.xx.xx.xx': AuthenticationFailed('Failed to authenticate to > xx.xx.xx.xx: Error from server: code=0100 [Bad credentials] > message="org.apache.cassandra.exceptions.UnavailableException: Cannot achieve > consistency level QUORUM"',)}) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13072) Cassandra failed to run on Linux-aarch64
[ https://issues.apache.org/jira/browse/CASSANDRA-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031109#comment-16031109 ] Jeff Jirsa commented on CASSANDRA-13072: The problem is that to enable a new platform you put at risk hundreds or thousands of existing users that may be running 2.2, if there's some unreported bug or hidden incompatibility in jna. Even if there's no bug, you're causing users to re-validate their deployment which is nontrivial (our testing isn't good enough for users with thousands of nodes to be sure that they won't have issues we didn't catch, this is a real step for most production deployments). The pragmatic approach is not changing a library in 2.2, since it's been this way (unsupported) for 2 years since its release > Cassandra failed to run on Linux-aarch64 > > > Key: CASSANDRA-13072 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13072 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: Hardware: ARM aarch64 > OS: Ubuntu 16.04.1 LTS >Reporter: Jun He >Assignee: Benjamin Lerer > Labels: incompatible > Attachments: compat_report.html > > > Steps to reproduce: > 1. Download cassandra latest source > 2. Build it with "ant" > 3. Run with "./bin/cassandra". Daemon is crashed with following error message: > {quote} > INFO 05:30:21 Initializing system.schema_functions > INFO 05:30:21 Initializing system.schema_aggregates > ERROR 05:30:22 Exception in thread Thread[MemtableFlushWriter:1,5,main] > java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native > at > org.apache.cassandra.utils.memory.MemoryUtil.allocate(MemoryUtil.java:97) > ~[main/:na] > at org.apache.cassandra.io.util.Memory.(Memory.java:74) > ~[main/:na] > at org.apache.cassandra.io.util.SafeMemory.(SafeMemory.java:32) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.(CompressionMetadata.java:316) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.open(CompressionMetadata.java:330) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressedSequentialWriter.(CompressedSequentialWriter.java:76) > ~[main/:na] > at > org.apache.cassandra.io.util.SequentialWriter.open(SequentialWriter.java:163) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigTableWriter.(BigTableWriter.java:73) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigFormat$WriterFactory.open(BigFormat.java:93) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.SSTableWriter.create(SSTableWriter.java:96) > ~[main/:na] > at > org.apache.cassandra.io.sstable.SimpleSSTableMultiWriter.create(SimpleSSTableMultiWriter.java:114) > ~[main/:na] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.createSSTableMultiWriter(AbstractCompactionStrategy.java:519) > ~[main/:na] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.createSSTableMultiWriter(CompactionStrategyManager.java:497) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore.createSSTableMultiWriter(ColumnFamilyStore.java:480) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.createFlushWriter(Memtable.java:439) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.writeSortedContents(Memtable.java:371) > ~[main/:na] > at org.apache.cassandra.db.Memtable.flush(Memtable.java:332) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1054) > ~[main/:na] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > ~[na:1.8.0_111] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > ~[na:1.8.0_111] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_111] > {quote} > Analyze: > This issue is caused by bundled jna-4.0.0.jar which doesn't come with aarch64 > native support. Replace lib/jna-4.0.0.jar with jna-4.2.0.jar from > http://central.maven.org/maven2/net/java/dev/jna/jna/4.2.0/ can fix this > problem. > Attached is the binary compatibility report of jna.jar between 4.0 and 4.2. > The result is good (97.4%). So is there possibility to upgrade jna to 4.2.0 > in upstream? Should there be any kind of tests to execute, please kindly > point me. Thanks a lot. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[09/10] cassandra git commit: Merge branch cassandra-3.0 into cassandra-3.11
Merge branch cassandra-3.0 into cassandra-3.11 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/54ff6193 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/54ff6193 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/54ff6193 Branch: refs/heads/trunk Commit: 54ff61931c04640a0358a9eaac332331f2009b29 Parents: 5a860a7 a2f742c Author: Benjamin Lerer Authored: Wed May 31 14:44:24 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 14:44:42 2017 +0200 -- CHANGES.txt| 2 + build.xml | 2 +- lib/jna-4.0.0.jar | Bin 914639 -> 0 bytes lib/jna-4.4.0.jar | Bin 0 -> 1091208 bytes lib/licenses/jna-4.0.0.txt | 202 lib/licenses/jna-4.4.0.txt | 202 6 files changed, 205 insertions(+), 203 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/54ff6193/CHANGES.txt -- diff --cc CHANGES.txt index c006b50,164470f..26a8018 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -69,33 -32,14 +69,35 @@@ Merged from 3.0 * Propagate row deletions in 2i tables on upgrade (CASSANDRA-13320) * Slice.isEmpty() returns false for some empty slices (CASSANDRA-13305) * Add formatted row output to assertEmpty in CQL Tester (CASSANDRA-13238) - * Legacy caching options can prevent 3.0 upgrade (CASSANDRA-13384) + * Prevent data loss on upgrade 2.1 - 3.0 by adding component separator to LogRecord absolute path (CASSANDRA-13294) + * Improve testing on macOS by eliminating sigar logging (CASSANDRA-13233) + * Cqlsh copy-from should error out when csv contains invalid data for collections (CASSANDRA-13071) + * Fix "multiple versions of ant detected..." when running ant test (CASSANDRA-13232) + * Coalescing strategy sleeps too much (CASSANDRA-13090) + * Faster StreamingHistogram (CASSANDRA-13038) + * Legacy deserializer can create unexpected boundary range tombstones (CASSANDRA-13237) + * Remove unnecessary assertion from AntiCompactionTest (CASSANDRA-13070) + * Fix cqlsh COPY for dates before 1900 (CASSANDRA-13185) + * Use keyspace replication settings on system.size_estimates table (CASSANDRA-9639) + * Add vm.max_map_count StartupCheck (CASSANDRA-13008) + * Hint related logging should include the IP address of the destination in addition to + host ID (CASSANDRA-13205) + * Reloading logback.xml does not work (CASSANDRA-13173) + * Lightweight transactions temporarily fail after upgrade from 2.1 to 3.0 (CASSANDRA-13109) + * Duplicate rows after upgrading from 2.1.16 to 3.0.10/3.9 (CASSANDRA-13125) + * Fix UPDATE queries with empty IN restrictions (CASSANDRA-13152) + * Fix handling of partition with partition-level deletion plus + live rows in sstabledump (CASSANDRA-13177) + * Provide user workaround when system_schema.columns does not contain entries + for a table that's in system_schema.tables (CASSANDRA-13180) * Nodetool upgradesstables/scrub/compact ignores system tables (CASSANDRA-13410) - * Fix NPE issue in StorageService (CASSANDRA-13060) + * Fix schema version calculation for rolling upgrades (CASSANDRA-13441) Merged from 2.2: + * upgrade JNA version to 4.4.0 (CASSANDRA-13072) + * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) + * Fix JVM metric names (CASSANDRA-13103) * Honor truststore-password parameter in cassandra-stress (CASSANDRA-12773) * Discard in-flight shadow round responses (CASSANDRA-12653) * Don't anti-compact repaired data to avoid inconsistencies (CASSANDRA-13153) http://git-wip-us.apache.org/repos/asf/cassandra/blob/54ff6193/build.xml -- - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[03/10] cassandra git commit: upgrade JNA version to 4.4.0
upgrade JNA version to 4.4.0 patch by Benjamin Lerer; reviewed by Aleksey Yeschenko for CASSANDRA-13072 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/3c81aa82 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/3c81aa82 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/3c81aa82 Branch: refs/heads/cassandra-3.11 Commit: 3c81aa825de1855a1cfd8de49d946e478d6bb085 Parents: dd6aa99 Author: Benjamin Lerer Authored: Wed May 31 14:37:10 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 14:37:10 2017 +0200 -- CHANGES.txt| 1 + build.xml | 2 +- lib/jna-4.0.0.jar | Bin 914639 -> 0 bytes lib/jna-4.4.0.jar | Bin 0 -> 1091208 bytes lib/licenses/jna-4.0.0.txt | 202 lib/licenses/jna-4.4.0.txt | 202 6 files changed, 204 insertions(+), 203 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index ef2e12c..4f3fba8 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 2.2.10 + * upgrade JNA version to 4.4.0 (CASSANDRA-13072) * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/build.xml -- diff --git a/build.xml b/build.xml index dc5aecb..c50d85b 100644 --- a/build.xml +++ b/build.xml @@ -382,7 +382,7 @@ - + http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/lib/jna-4.0.0.jar -- diff --git a/lib/jna-4.0.0.jar b/lib/jna-4.0.0.jar deleted file mode 100644 index 9038048..000 Binary files a/lib/jna-4.0.0.jar and /dev/null differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/lib/jna-4.4.0.jar -- diff --git a/lib/jna-4.4.0.jar b/lib/jna-4.4.0.jar new file mode 100644 index 000..521bd92 Binary files /dev/null and b/lib/jna-4.4.0.jar differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/lib/licenses/jna-4.0.0.txt -- diff --git a/lib/licenses/jna-4.0.0.txt b/lib/licenses/jna-4.0.0.txt deleted file mode 100644 index 7a4a3ea..000 --- a/lib/licenses/jna-4.0.0.txt +++ /dev/null @@ -1,202 +0,0 @@ - - Apache License - Version 2.0, January 2004 -http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived fro
[04/10] cassandra git commit: upgrade JNA version to 4.4.0
upgrade JNA version to 4.4.0 patch by Benjamin Lerer; reviewed by Aleksey Yeschenko for CASSANDRA-13072 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/3c81aa82 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/3c81aa82 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/3c81aa82 Branch: refs/heads/trunk Commit: 3c81aa825de1855a1cfd8de49d946e478d6bb085 Parents: dd6aa99 Author: Benjamin Lerer Authored: Wed May 31 14:37:10 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 14:37:10 2017 +0200 -- CHANGES.txt| 1 + build.xml | 2 +- lib/jna-4.0.0.jar | Bin 914639 -> 0 bytes lib/jna-4.4.0.jar | Bin 0 -> 1091208 bytes lib/licenses/jna-4.0.0.txt | 202 lib/licenses/jna-4.4.0.txt | 202 6 files changed, 204 insertions(+), 203 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index ef2e12c..4f3fba8 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 2.2.10 + * upgrade JNA version to 4.4.0 (CASSANDRA-13072) * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/build.xml -- diff --git a/build.xml b/build.xml index dc5aecb..c50d85b 100644 --- a/build.xml +++ b/build.xml @@ -382,7 +382,7 @@ - + http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/lib/jna-4.0.0.jar -- diff --git a/lib/jna-4.0.0.jar b/lib/jna-4.0.0.jar deleted file mode 100644 index 9038048..000 Binary files a/lib/jna-4.0.0.jar and /dev/null differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/lib/jna-4.4.0.jar -- diff --git a/lib/jna-4.4.0.jar b/lib/jna-4.4.0.jar new file mode 100644 index 000..521bd92 Binary files /dev/null and b/lib/jna-4.4.0.jar differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/lib/licenses/jna-4.0.0.txt -- diff --git a/lib/licenses/jna-4.0.0.txt b/lib/licenses/jna-4.0.0.txt deleted file mode 100644 index 7a4a3ea..000 --- a/lib/licenses/jna-4.0.0.txt +++ /dev/null @@ -1,202 +0,0 @@ - - Apache License - Version 2.0, January 2004 -http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived from) the Wo
[05/10] cassandra git commit: Merge branch cassandra-2.2 into cassandra-3.0
Merge branch cassandra-2.2 into cassandra-3.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/a2f742cd Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/a2f742cd Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/a2f742cd Branch: refs/heads/cassandra-3.11 Commit: a2f742cd633ddd650b65f841c50ee96ee1da0ef5 Parents: 8ffdd26 3c81aa8 Author: Benjamin Lerer Authored: Wed May 31 14:42:17 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 14:42:17 2017 +0200 -- CHANGES.txt| 2 + build.xml | 2 +- lib/jna-4.0.0.jar | Bin 914639 -> 0 bytes lib/jna-4.4.0.jar | Bin 0 -> 1091208 bytes lib/licenses/jna-4.0.0.txt | 202 lib/licenses/jna-4.4.0.txt | 202 6 files changed, 205 insertions(+), 203 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/a2f742cd/CHANGES.txt -- diff --cc CHANGES.txt index 18dca09,4f3fba8..164470f --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,43 -1,9 +1,45 @@@ -2.2.10 +3.0.14 + * Interned ColumnIdentifiers should use minimal ByteBuffers (CASSANDRA-13533) + * ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade (CASSANDRA-13525) + * Fix repair process violating start/end token limits for small ranges (CASSANDRA-13052) + * Add storage port options to sstableloader (CASSANDRA-13518) + * Properly handle quoted index names in cqlsh DESCRIBE output (CASSANDRA-12847) + * Avoid reading static row twice from old format sstables (CASSANDRA-13236) + * Fix NPE in StorageService.excise() (CASSANDRA-13163) + * Expire OutboundTcpConnection messages by a single Thread (CASSANDRA-13265) + * Fail repair if insufficient responses received (CASSANDRA-13397) + * Fix SSTableLoader fail when the loaded table contains dropped columns (CASSANDRA-13276) + * Avoid name clashes in CassandraIndexTest (CASSANDRA-13427) + * Handling partially written hint files (CASSANDRA-12728) + * Interrupt replaying hints on decommission (CASSANDRA-13308) + * Fix schema version calculation for rolling upgrades (CASSANDRA-13441) + +3.0.13 + * Make reading of range tombstones more reliable (CASSANDRA-12811) + * Fix startup problems due to schema tables not completely flushed (CASSANDRA-12213) + * Fix view builder bug that can filter out data on restart (CASSANDRA-13405) + * Fix 2i page size calculation when there are no regular columns (CASSANDRA-13400) + * Fix the conversion of 2.X expired rows without regular column data (CASSANDRA-13395) + * Fix hint delivery when using ext+internal IPs with prefer_local enabled (CASSANDRA-13020) + * Fix possible NPE on upgrade to 3.0/3.X in case of IO errors (CASSANDRA-13389) + * Legacy deserializer can create empty range tombstones (CASSANDRA-13341) + * Use the Kernel32 library to retrieve the PID on Windows and fix startup checks (CASSANDRA-1) + * Fix code to not exchange schema across major versions (CASSANDRA-13274) + * Dropping column results in "corrupt" SSTable (CASSANDRA-13337) + * Bugs handling range tombstones in the sstable iterators (CASSANDRA-13340) + * Fix CONTAINS filtering for null collections (CASSANDRA-13246) + * Applying: Use a unique metric reservoir per test run when using Cassandra-wide metrics residing in MBeans (CASSANDRA-13216) + * Propagate row deletions in 2i tables on upgrade (CASSANDRA-13320) + * Slice.isEmpty() returns false for some empty slices (CASSANDRA-13305) + * Add formatted row output to assertEmpty in CQL Tester (CASSANDRA-13238) + * Legacy caching options can prevent 3.0 upgrade (CASSANDRA-13384) + * Nodetool upgradesstables/scrub/compact ignores system tables (CASSANDRA-13410) + * Fix NPE issue in StorageService (CASSANDRA-13060) +Merged from 2.2: + * upgrade JNA version to 4.4.0 (CASSANDRA-13072) + * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) - * Fix JVM metric paths (CASSANDRA-13103) * Honor truststore-password parameter in cassandra-stress (CASSANDRA-12773) * Discard in-flight shadow round responses (CASSANDRA-12653) * Don't anti-compact repaired data to avoid inconsistencies (CASSANDRA-13153) http://git-wip-us.apache.org/repos/asf/cassandra/blob/a2f742cd/build.xml -- diff --cc build.xml index ce12b90,c50d85b..de6564a --- a/build.xml +++ b/build.xml @@@ -380,8 -377,19 +380,8 @@@ - - - - -
[07/10] cassandra git commit: Merge branch cassandra-2.2 into cassandra-3.0
Merge branch cassandra-2.2 into cassandra-3.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/a2f742cd Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/a2f742cd Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/a2f742cd Branch: refs/heads/trunk Commit: a2f742cd633ddd650b65f841c50ee96ee1da0ef5 Parents: 8ffdd26 3c81aa8 Author: Benjamin Lerer Authored: Wed May 31 14:42:17 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 14:42:17 2017 +0200 -- CHANGES.txt| 2 + build.xml | 2 +- lib/jna-4.0.0.jar | Bin 914639 -> 0 bytes lib/jna-4.4.0.jar | Bin 0 -> 1091208 bytes lib/licenses/jna-4.0.0.txt | 202 lib/licenses/jna-4.4.0.txt | 202 6 files changed, 205 insertions(+), 203 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/a2f742cd/CHANGES.txt -- diff --cc CHANGES.txt index 18dca09,4f3fba8..164470f --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,43 -1,9 +1,45 @@@ -2.2.10 +3.0.14 + * Interned ColumnIdentifiers should use minimal ByteBuffers (CASSANDRA-13533) + * ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade (CASSANDRA-13525) + * Fix repair process violating start/end token limits for small ranges (CASSANDRA-13052) + * Add storage port options to sstableloader (CASSANDRA-13518) + * Properly handle quoted index names in cqlsh DESCRIBE output (CASSANDRA-12847) + * Avoid reading static row twice from old format sstables (CASSANDRA-13236) + * Fix NPE in StorageService.excise() (CASSANDRA-13163) + * Expire OutboundTcpConnection messages by a single Thread (CASSANDRA-13265) + * Fail repair if insufficient responses received (CASSANDRA-13397) + * Fix SSTableLoader fail when the loaded table contains dropped columns (CASSANDRA-13276) + * Avoid name clashes in CassandraIndexTest (CASSANDRA-13427) + * Handling partially written hint files (CASSANDRA-12728) + * Interrupt replaying hints on decommission (CASSANDRA-13308) + * Fix schema version calculation for rolling upgrades (CASSANDRA-13441) + +3.0.13 + * Make reading of range tombstones more reliable (CASSANDRA-12811) + * Fix startup problems due to schema tables not completely flushed (CASSANDRA-12213) + * Fix view builder bug that can filter out data on restart (CASSANDRA-13405) + * Fix 2i page size calculation when there are no regular columns (CASSANDRA-13400) + * Fix the conversion of 2.X expired rows without regular column data (CASSANDRA-13395) + * Fix hint delivery when using ext+internal IPs with prefer_local enabled (CASSANDRA-13020) + * Fix possible NPE on upgrade to 3.0/3.X in case of IO errors (CASSANDRA-13389) + * Legacy deserializer can create empty range tombstones (CASSANDRA-13341) + * Use the Kernel32 library to retrieve the PID on Windows and fix startup checks (CASSANDRA-1) + * Fix code to not exchange schema across major versions (CASSANDRA-13274) + * Dropping column results in "corrupt" SSTable (CASSANDRA-13337) + * Bugs handling range tombstones in the sstable iterators (CASSANDRA-13340) + * Fix CONTAINS filtering for null collections (CASSANDRA-13246) + * Applying: Use a unique metric reservoir per test run when using Cassandra-wide metrics residing in MBeans (CASSANDRA-13216) + * Propagate row deletions in 2i tables on upgrade (CASSANDRA-13320) + * Slice.isEmpty() returns false for some empty slices (CASSANDRA-13305) + * Add formatted row output to assertEmpty in CQL Tester (CASSANDRA-13238) + * Legacy caching options can prevent 3.0 upgrade (CASSANDRA-13384) + * Nodetool upgradesstables/scrub/compact ignores system tables (CASSANDRA-13410) + * Fix NPE issue in StorageService (CASSANDRA-13060) +Merged from 2.2: + * upgrade JNA version to 4.4.0 (CASSANDRA-13072) + * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) - * Fix JVM metric paths (CASSANDRA-13103) * Honor truststore-password parameter in cassandra-stress (CASSANDRA-12773) * Discard in-flight shadow round responses (CASSANDRA-12653) * Don't anti-compact repaired data to avoid inconsistencies (CASSANDRA-13153) http://git-wip-us.apache.org/repos/asf/cassandra/blob/a2f742cd/build.xml -- diff --cc build.xml index ce12b90,c50d85b..de6564a --- a/build.xml +++ b/build.xml @@@ -380,8 -377,19 +380,8 @@@ - - - - -
[02/10] cassandra git commit: upgrade JNA version to 4.4.0
upgrade JNA version to 4.4.0 patch by Benjamin Lerer; reviewed by Aleksey Yeschenko for CASSANDRA-13072 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/3c81aa82 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/3c81aa82 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/3c81aa82 Branch: refs/heads/cassandra-3.0 Commit: 3c81aa825de1855a1cfd8de49d946e478d6bb085 Parents: dd6aa99 Author: Benjamin Lerer Authored: Wed May 31 14:37:10 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 14:37:10 2017 +0200 -- CHANGES.txt| 1 + build.xml | 2 +- lib/jna-4.0.0.jar | Bin 914639 -> 0 bytes lib/jna-4.4.0.jar | Bin 0 -> 1091208 bytes lib/licenses/jna-4.0.0.txt | 202 lib/licenses/jna-4.4.0.txt | 202 6 files changed, 204 insertions(+), 203 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index ef2e12c..4f3fba8 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 2.2.10 + * upgrade JNA version to 4.4.0 (CASSANDRA-13072) * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/build.xml -- diff --git a/build.xml b/build.xml index dc5aecb..c50d85b 100644 --- a/build.xml +++ b/build.xml @@ -382,7 +382,7 @@ - + http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/lib/jna-4.0.0.jar -- diff --git a/lib/jna-4.0.0.jar b/lib/jna-4.0.0.jar deleted file mode 100644 index 9038048..000 Binary files a/lib/jna-4.0.0.jar and /dev/null differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/lib/jna-4.4.0.jar -- diff --git a/lib/jna-4.4.0.jar b/lib/jna-4.4.0.jar new file mode 100644 index 000..521bd92 Binary files /dev/null and b/lib/jna-4.4.0.jar differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/lib/licenses/jna-4.0.0.txt -- diff --git a/lib/licenses/jna-4.0.0.txt b/lib/licenses/jna-4.0.0.txt deleted file mode 100644 index 7a4a3ea..000 --- a/lib/licenses/jna-4.0.0.txt +++ /dev/null @@ -1,202 +0,0 @@ - - Apache License - Version 2.0, January 2004 -http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived from
[06/10] cassandra git commit: Merge branch cassandra-2.2 into cassandra-3.0
Merge branch cassandra-2.2 into cassandra-3.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/a2f742cd Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/a2f742cd Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/a2f742cd Branch: refs/heads/cassandra-3.0 Commit: a2f742cd633ddd650b65f841c50ee96ee1da0ef5 Parents: 8ffdd26 3c81aa8 Author: Benjamin Lerer Authored: Wed May 31 14:42:17 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 14:42:17 2017 +0200 -- CHANGES.txt| 2 + build.xml | 2 +- lib/jna-4.0.0.jar | Bin 914639 -> 0 bytes lib/jna-4.4.0.jar | Bin 0 -> 1091208 bytes lib/licenses/jna-4.0.0.txt | 202 lib/licenses/jna-4.4.0.txt | 202 6 files changed, 205 insertions(+), 203 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/a2f742cd/CHANGES.txt -- diff --cc CHANGES.txt index 18dca09,4f3fba8..164470f --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,43 -1,9 +1,45 @@@ -2.2.10 +3.0.14 + * Interned ColumnIdentifiers should use minimal ByteBuffers (CASSANDRA-13533) + * ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade (CASSANDRA-13525) + * Fix repair process violating start/end token limits for small ranges (CASSANDRA-13052) + * Add storage port options to sstableloader (CASSANDRA-13518) + * Properly handle quoted index names in cqlsh DESCRIBE output (CASSANDRA-12847) + * Avoid reading static row twice from old format sstables (CASSANDRA-13236) + * Fix NPE in StorageService.excise() (CASSANDRA-13163) + * Expire OutboundTcpConnection messages by a single Thread (CASSANDRA-13265) + * Fail repair if insufficient responses received (CASSANDRA-13397) + * Fix SSTableLoader fail when the loaded table contains dropped columns (CASSANDRA-13276) + * Avoid name clashes in CassandraIndexTest (CASSANDRA-13427) + * Handling partially written hint files (CASSANDRA-12728) + * Interrupt replaying hints on decommission (CASSANDRA-13308) + * Fix schema version calculation for rolling upgrades (CASSANDRA-13441) + +3.0.13 + * Make reading of range tombstones more reliable (CASSANDRA-12811) + * Fix startup problems due to schema tables not completely flushed (CASSANDRA-12213) + * Fix view builder bug that can filter out data on restart (CASSANDRA-13405) + * Fix 2i page size calculation when there are no regular columns (CASSANDRA-13400) + * Fix the conversion of 2.X expired rows without regular column data (CASSANDRA-13395) + * Fix hint delivery when using ext+internal IPs with prefer_local enabled (CASSANDRA-13020) + * Fix possible NPE on upgrade to 3.0/3.X in case of IO errors (CASSANDRA-13389) + * Legacy deserializer can create empty range tombstones (CASSANDRA-13341) + * Use the Kernel32 library to retrieve the PID on Windows and fix startup checks (CASSANDRA-1) + * Fix code to not exchange schema across major versions (CASSANDRA-13274) + * Dropping column results in "corrupt" SSTable (CASSANDRA-13337) + * Bugs handling range tombstones in the sstable iterators (CASSANDRA-13340) + * Fix CONTAINS filtering for null collections (CASSANDRA-13246) + * Applying: Use a unique metric reservoir per test run when using Cassandra-wide metrics residing in MBeans (CASSANDRA-13216) + * Propagate row deletions in 2i tables on upgrade (CASSANDRA-13320) + * Slice.isEmpty() returns false for some empty slices (CASSANDRA-13305) + * Add formatted row output to assertEmpty in CQL Tester (CASSANDRA-13238) + * Legacy caching options can prevent 3.0 upgrade (CASSANDRA-13384) + * Nodetool upgradesstables/scrub/compact ignores system tables (CASSANDRA-13410) + * Fix NPE issue in StorageService (CASSANDRA-13060) +Merged from 2.2: + * upgrade JNA version to 4.4.0 (CASSANDRA-13072) + * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) - * Fix JVM metric paths (CASSANDRA-13103) * Honor truststore-password parameter in cassandra-stress (CASSANDRA-12773) * Discard in-flight shadow round responses (CASSANDRA-12653) * Don't anti-compact repaired data to avoid inconsistencies (CASSANDRA-13153) http://git-wip-us.apache.org/repos/asf/cassandra/blob/a2f742cd/build.xml -- diff --cc build.xml index ce12b90,c50d85b..de6564a --- a/build.xml +++ b/build.xml @@@ -380,8 -377,19 +380,8 @@@ - - - - -
[10/10] cassandra git commit: Merge branch cassandra-3.11 into trunk
Merge branch cassandra-3.11 into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/ea57a4db Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/ea57a4db Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/ea57a4db Branch: refs/heads/trunk Commit: ea57a4dbe8b3c312465cd2a0fe315d5f04f8ce92 Parents: 7b149ce 54ff619 Author: Benjamin Lerer Authored: Wed May 31 14:48:48 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 14:52:30 2017 +0200 -- CHANGES.txt| 1 + build.xml | 2 +- lib/futures-2.1.6-py2.py3-none-any.zip | Bin 16571 -> 1090481 bytes lib/jna-4.3.0.jar | Bin 945524 -> 0 bytes lib/licenses/jna-4.3.0.txt | 202 lib/licenses/jna-4.4.0.txt | 202 6 files changed, 204 insertions(+), 203 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/ea57a4db/CHANGES.txt -- diff --cc CHANGES.txt index d81d2c5,26a8018..0bda3a6 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -163,6 -93,8 +163,7 @@@ Merged from 3.0 * Nodetool upgradesstables/scrub/compact ignores system tables (CASSANDRA-13410) * Fix schema version calculation for rolling upgrades (CASSANDRA-13441) Merged from 2.2: - * upgrade JNA version to 4.4.0 (CASSANDRA-13072) - * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) ++ * Upgrade JNA to version 4.4.0 (CASSANDRA-13072) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) * Fix JVM metric names (CASSANDRA-13103) http://git-wip-us.apache.org/repos/asf/cassandra/blob/ea57a4db/build.xml -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/ea57a4db/lib/futures-2.1.6-py2.py3-none-any.zip -- diff --cc lib/futures-2.1.6-py2.py3-none-any.zip index 50bd78b,50bd78b..4c27243 Binary files differ - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[08/10] cassandra git commit: Merge branch cassandra-3.0 into cassandra-3.11
Merge branch cassandra-3.0 into cassandra-3.11 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/54ff6193 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/54ff6193 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/54ff6193 Branch: refs/heads/cassandra-3.11 Commit: 54ff61931c04640a0358a9eaac332331f2009b29 Parents: 5a860a7 a2f742c Author: Benjamin Lerer Authored: Wed May 31 14:44:24 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 14:44:42 2017 +0200 -- CHANGES.txt| 2 + build.xml | 2 +- lib/jna-4.0.0.jar | Bin 914639 -> 0 bytes lib/jna-4.4.0.jar | Bin 0 -> 1091208 bytes lib/licenses/jna-4.0.0.txt | 202 lib/licenses/jna-4.4.0.txt | 202 6 files changed, 205 insertions(+), 203 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/54ff6193/CHANGES.txt -- diff --cc CHANGES.txt index c006b50,164470f..26a8018 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -69,33 -32,14 +69,35 @@@ Merged from 3.0 * Propagate row deletions in 2i tables on upgrade (CASSANDRA-13320) * Slice.isEmpty() returns false for some empty slices (CASSANDRA-13305) * Add formatted row output to assertEmpty in CQL Tester (CASSANDRA-13238) - * Legacy caching options can prevent 3.0 upgrade (CASSANDRA-13384) + * Prevent data loss on upgrade 2.1 - 3.0 by adding component separator to LogRecord absolute path (CASSANDRA-13294) + * Improve testing on macOS by eliminating sigar logging (CASSANDRA-13233) + * Cqlsh copy-from should error out when csv contains invalid data for collections (CASSANDRA-13071) + * Fix "multiple versions of ant detected..." when running ant test (CASSANDRA-13232) + * Coalescing strategy sleeps too much (CASSANDRA-13090) + * Faster StreamingHistogram (CASSANDRA-13038) + * Legacy deserializer can create unexpected boundary range tombstones (CASSANDRA-13237) + * Remove unnecessary assertion from AntiCompactionTest (CASSANDRA-13070) + * Fix cqlsh COPY for dates before 1900 (CASSANDRA-13185) + * Use keyspace replication settings on system.size_estimates table (CASSANDRA-9639) + * Add vm.max_map_count StartupCheck (CASSANDRA-13008) + * Hint related logging should include the IP address of the destination in addition to + host ID (CASSANDRA-13205) + * Reloading logback.xml does not work (CASSANDRA-13173) + * Lightweight transactions temporarily fail after upgrade from 2.1 to 3.0 (CASSANDRA-13109) + * Duplicate rows after upgrading from 2.1.16 to 3.0.10/3.9 (CASSANDRA-13125) + * Fix UPDATE queries with empty IN restrictions (CASSANDRA-13152) + * Fix handling of partition with partition-level deletion plus + live rows in sstabledump (CASSANDRA-13177) + * Provide user workaround when system_schema.columns does not contain entries + for a table that's in system_schema.tables (CASSANDRA-13180) * Nodetool upgradesstables/scrub/compact ignores system tables (CASSANDRA-13410) - * Fix NPE issue in StorageService (CASSANDRA-13060) + * Fix schema version calculation for rolling upgrades (CASSANDRA-13441) Merged from 2.2: + * upgrade JNA version to 4.4.0 (CASSANDRA-13072) + * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) + * Fix JVM metric names (CASSANDRA-13103) * Honor truststore-password parameter in cassandra-stress (CASSANDRA-12773) * Discard in-flight shadow round responses (CASSANDRA-12653) * Don't anti-compact repaired data to avoid inconsistencies (CASSANDRA-13153) http://git-wip-us.apache.org/repos/asf/cassandra/blob/54ff6193/build.xml -- - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[01/10] cassandra git commit: upgrade JNA version to 4.4.0
Repository: cassandra Updated Branches: refs/heads/cassandra-2.2 dd6aa991b -> 3c81aa825 refs/heads/cassandra-3.0 8ffdd26cb -> a2f742cd6 refs/heads/cassandra-3.11 5a860a70f -> 54ff61931 refs/heads/trunk 7b149ce4a -> ea57a4dbe upgrade JNA version to 4.4.0 patch by Benjamin Lerer; reviewed by Aleksey Yeschenko for CASSANDRA-13072 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/3c81aa82 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/3c81aa82 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/3c81aa82 Branch: refs/heads/cassandra-2.2 Commit: 3c81aa825de1855a1cfd8de49d946e478d6bb085 Parents: dd6aa99 Author: Benjamin Lerer Authored: Wed May 31 14:37:10 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 14:37:10 2017 +0200 -- CHANGES.txt| 1 + build.xml | 2 +- lib/jna-4.0.0.jar | Bin 914639 -> 0 bytes lib/jna-4.4.0.jar | Bin 0 -> 1091208 bytes lib/licenses/jna-4.0.0.txt | 202 lib/licenses/jna-4.4.0.txt | 202 6 files changed, 204 insertions(+), 203 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index ef2e12c..4f3fba8 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 2.2.10 + * upgrade JNA version to 4.4.0 (CASSANDRA-13072) * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/build.xml -- diff --git a/build.xml b/build.xml index dc5aecb..c50d85b 100644 --- a/build.xml +++ b/build.xml @@ -382,7 +382,7 @@ - + http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/lib/jna-4.0.0.jar -- diff --git a/lib/jna-4.0.0.jar b/lib/jna-4.0.0.jar deleted file mode 100644 index 9038048..000 Binary files a/lib/jna-4.0.0.jar and /dev/null differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/lib/jna-4.4.0.jar -- diff --git a/lib/jna-4.4.0.jar b/lib/jna-4.4.0.jar new file mode 100644 index 000..521bd92 Binary files /dev/null and b/lib/jna-4.4.0.jar differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/3c81aa82/lib/licenses/jna-4.0.0.txt -- diff --git a/lib/licenses/jna-4.0.0.txt b/lib/licenses/jna-4.0.0.txt deleted file mode 100644 index 7a4a3ea..000 --- a/lib/licenses/jna-4.0.0.txt +++ /dev/null @@ -1,202 +0,0 @@ - - Apache License - Version 2.0, January 2004 -http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copy
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031118#comment-16031118 ] Aleksey Yeschenko commented on CASSANDRA-13559: --- +1 from me as well. Sorry for not spotting the issue in the original ticket, or even steering the implementation towards this issue. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13072) Cassandra failed to run on Linux-aarch64
[ https://issues.apache.org/jira/browse/CASSANDRA-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031126#comment-16031126 ] Benjamin Lerer commented on CASSANDRA-13072: I am not sure that I follow you. Your initial comment was about the fact that we do have not testing support for Linux-aarch64 and your new comment is about the fact that the testing is not good enough. If your problem is about 2.2. I will not argue about that and revert my commit in that branch. > Cassandra failed to run on Linux-aarch64 > > > Key: CASSANDRA-13072 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13072 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: Hardware: ARM aarch64 > OS: Ubuntu 16.04.1 LTS >Reporter: Jun He >Assignee: Benjamin Lerer > Labels: incompatible > Attachments: compat_report.html > > > Steps to reproduce: > 1. Download cassandra latest source > 2. Build it with "ant" > 3. Run with "./bin/cassandra". Daemon is crashed with following error message: > {quote} > INFO 05:30:21 Initializing system.schema_functions > INFO 05:30:21 Initializing system.schema_aggregates > ERROR 05:30:22 Exception in thread Thread[MemtableFlushWriter:1,5,main] > java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native > at > org.apache.cassandra.utils.memory.MemoryUtil.allocate(MemoryUtil.java:97) > ~[main/:na] > at org.apache.cassandra.io.util.Memory.(Memory.java:74) > ~[main/:na] > at org.apache.cassandra.io.util.SafeMemory.(SafeMemory.java:32) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.(CompressionMetadata.java:316) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.open(CompressionMetadata.java:330) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressedSequentialWriter.(CompressedSequentialWriter.java:76) > ~[main/:na] > at > org.apache.cassandra.io.util.SequentialWriter.open(SequentialWriter.java:163) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigTableWriter.(BigTableWriter.java:73) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigFormat$WriterFactory.open(BigFormat.java:93) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.SSTableWriter.create(SSTableWriter.java:96) > ~[main/:na] > at > org.apache.cassandra.io.sstable.SimpleSSTableMultiWriter.create(SimpleSSTableMultiWriter.java:114) > ~[main/:na] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.createSSTableMultiWriter(AbstractCompactionStrategy.java:519) > ~[main/:na] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.createSSTableMultiWriter(CompactionStrategyManager.java:497) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore.createSSTableMultiWriter(ColumnFamilyStore.java:480) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.createFlushWriter(Memtable.java:439) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.writeSortedContents(Memtable.java:371) > ~[main/:na] > at org.apache.cassandra.db.Memtable.flush(Memtable.java:332) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1054) > ~[main/:na] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > ~[na:1.8.0_111] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > ~[na:1.8.0_111] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_111] > {quote} > Analyze: > This issue is caused by bundled jna-4.0.0.jar which doesn't come with aarch64 > native support. Replace lib/jna-4.0.0.jar with jna-4.2.0.jar from > http://central.maven.org/maven2/net/java/dev/jna/jna/4.2.0/ can fix this > problem. > Attached is the binary compatibility report of jna.jar between 4.0 and 4.2. > The result is good (97.4%). So is there possibility to upgrade jna to 4.2.0 > in upstream? Should there be any kind of tests to execute, please kindly > point me. Thanks a lot. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-13072) Cassandra failed to run on Linux-aarch64
[ https://issues.apache.org/jira/browse/CASSANDRA-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031126#comment-16031126 ] Benjamin Lerer edited comment on CASSANDRA-13072 at 5/31/17 1:11 PM: - I am not sure that I follow you. Your initial comment was about the fact that we do not have testing support for Linux-aarch64 and your new comment is about the fact that the testing is not good enough. If your problem is about 2.2. I will not argue about that and revert my commit in that branch. was (Author: blerer): I am not sure that I follow you. Your initial comment was about the fact that we do have not testing support for Linux-aarch64 and your new comment is about the fact that the testing is not good enough. If your problem is about 2.2. I will not argue about that and revert my commit in that branch. > Cassandra failed to run on Linux-aarch64 > > > Key: CASSANDRA-13072 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13072 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: Hardware: ARM aarch64 > OS: Ubuntu 16.04.1 LTS >Reporter: Jun He >Assignee: Benjamin Lerer > Labels: incompatible > Attachments: compat_report.html > > > Steps to reproduce: > 1. Download cassandra latest source > 2. Build it with "ant" > 3. Run with "./bin/cassandra". Daemon is crashed with following error message: > {quote} > INFO 05:30:21 Initializing system.schema_functions > INFO 05:30:21 Initializing system.schema_aggregates > ERROR 05:30:22 Exception in thread Thread[MemtableFlushWriter:1,5,main] > java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native > at > org.apache.cassandra.utils.memory.MemoryUtil.allocate(MemoryUtil.java:97) > ~[main/:na] > at org.apache.cassandra.io.util.Memory.(Memory.java:74) > ~[main/:na] > at org.apache.cassandra.io.util.SafeMemory.(SafeMemory.java:32) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.(CompressionMetadata.java:316) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.open(CompressionMetadata.java:330) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressedSequentialWriter.(CompressedSequentialWriter.java:76) > ~[main/:na] > at > org.apache.cassandra.io.util.SequentialWriter.open(SequentialWriter.java:163) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigTableWriter.(BigTableWriter.java:73) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigFormat$WriterFactory.open(BigFormat.java:93) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.SSTableWriter.create(SSTableWriter.java:96) > ~[main/:na] > at > org.apache.cassandra.io.sstable.SimpleSSTableMultiWriter.create(SimpleSSTableMultiWriter.java:114) > ~[main/:na] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.createSSTableMultiWriter(AbstractCompactionStrategy.java:519) > ~[main/:na] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.createSSTableMultiWriter(CompactionStrategyManager.java:497) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore.createSSTableMultiWriter(ColumnFamilyStore.java:480) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.createFlushWriter(Memtable.java:439) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.writeSortedContents(Memtable.java:371) > ~[main/:na] > at org.apache.cassandra.db.Memtable.flush(Memtable.java:332) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1054) > ~[main/:na] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > ~[na:1.8.0_111] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > ~[na:1.8.0_111] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_111] > {quote} > Analyze: > This issue is caused by bundled jna-4.0.0.jar which doesn't come with aarch64 > native support. Replace lib/jna-4.0.0.jar with jna-4.2.0.jar from > http://central.maven.org/maven2/net/java/dev/jna/jna/4.2.0/ can fix this > problem. > Attached is the binary compatibility report of jna.jar between 4.0 and 4.2. > The result is good (97.4%). So is there possibility to upgrade jna to 4.2.0 > in upstream? Should there be any kind of tests to execute, please kindly > point me. Thanks a lot. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For a
[jira] [Commented] (CASSANDRA-13444) Fast and garbage-free Streaming Histogram
[ https://issues.apache.org/jira/browse/CASSANDRA-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031130#comment-16031130 ] Jason Brown commented on CASSANDRA-13444: - Sorry for the delay, very busy these days. I've added a few tiny doc things on my local branch, and will probably commit this afternoon as everything else looks really good. > Fast and garbage-free Streaming Histogram > - > > Key: CASSANDRA-13444 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13444 > Project: Cassandra > Issue Type: Improvement > Components: Compaction >Reporter: Fuud >Assignee: Fuud > Fix For: 4.x > > Attachments: results.csv, results.xlsx > > > StreamingHistogram is cause of high cpu usage and GC pressure. > It was improved at CASSANDRA-13038 by introducing intermediate buffer to try > accumulate different values into the big map before merging them into smaller > one. > But there was not enought for TTL's distributed within large time. Rounding > (also introduced at 13038) can help but it reduce histogram precision > specially in case where TTL's does not distributed uniformly. > There are several improvements that can help to reduce cpu and gc usage. Them > all included in the pool-request as separate revisions thus you can test them > independently. > Improvements list: > # Use Map.computeIfAbsent instead of get->checkIfNull->put chain. In this way > "add-or-accumulate" operation takes one map operation instead of two. But > this method (default-defined in interface Map) is overriden in HashMap but > not in TreeMap. Thus I changed spool type to HashMap. > # As we round incoming values to _roundSeconds_ we can also round value on > merge. It will enlarge hit rate for bin operations. > # Because we inserted only integers into Histogram and rounding values to > integers we can use *int* type everywhere. > # Histogram takes huge amount of time merging values. In merge method largest > amount of time taken by finding nearest points. It can be eliminated by > holding additional TreeSet with differences, sorted from smalest to greatest. > # Because we know max size of _bin_ and _differences_ maps we can replace > them with sorted arrays. Search can be done with _Arrays.binarySearch_ and > insertion/deletions can be done by _System.arraycopy_. Also it helps to merge > some operations into one. > # Because spool map is also limited we can replace it with open address > primitive map. It's finaly reduce allocation rate to zero. > You can see gain given by each step in the attached file. First number is > time for one benchmark invocation and second - is allocation rate in Mb per > operation. > Dependends of payload time is reduced up to 90%. > Overall gain: > |.|.|Payload/SpoolSize|.|.|.|% from original > |.|.|.|original|.|optimized| > |.|.|secondInMonth/0|.|.|.| > |time ms/op|.|.|10747,684|.|5545,063|51,6 > |allocation Mb/op|.|.|2441,38858|.|0,002105713|0 > |.|.|.|.|.|.| > |.|.|secondInMonth/1000|.|.|.| > |time ms/op|.|.|8988,578|.|5791,179|64,4 > |allocation Mb/op|.|.|2440,951141|.|0,017715454|0 > |.|.|.|.|.|.| > |.|.|secondInMonth/1|.|.|.| > |time ms/op|.|.|10711,671|.|5765,243|53,8 > |allocation Mb/op|.|.|2437,022537|.|0,264083862|0 > |.|.|.|.|.|.| > |.|.|secondInMonth/10|.|.|.| > |time ms/op|.|.|13001,841|.|5638,069|43,4 > |allocation Mb/op|.|.|2396,947113|.|2,003662109|0,1 > |.|.|.|.|.|.| > |.|.|secondInDay/0|.|.|.| > |time ms/op|.|.|10381,833|.|5497,804|53 > |allocation Mb/op|.|.|2441,166107|.|0,002105713|0 > |.|.|.|.|.|.| > |.|.|secondInDay/1000|.|.|.| > |time ms/op|.|.|8522,157|.|5929,871|69,6 > |allocation Mb/op|.|.|1973,112381|.|0,017715454|0 > |.|.|.|.|.|.| > |.|.|secondInDay/1|.|.|.| > |time ms/op|.|.|10234,978|.|5480,077|53,5 > |allocation Mb/op|.|.|2306,057404|.|0,262969971|0 > |.|.|.|.|.|.| > |.|.|secondInDay/10|.|.|.| > |time ms/op|.|.|2971,178|.|139,079|4,7 > |allocation Mb/op|.|.|172,1276245|.|2,001721191|1,2 > |.|.|.|.|.|.| > |.|.|secondIn3Hour/0|.|.|.| > |time ms/op|.|.|10663,123|.|5605,672|52,6 > |allocation Mb/op|.|.|2439,456818|.|0,002105713|0 > |.|.|.|.|.|.| > |.|.|secondIn3Hour/1000|.|.|.| > |time ms/op|.|.|9029,788|.|5838,618|64,7 > |allocation Mb/op|.|.|2331,839249|.|0,180664063|0 > |.|.|.|.|.|.| > |.|.|secondIn3Hour/1|.|.|.| > |time ms/op|.|.|4862,409|.|89,001|1,8 > |allocation Mb/op|.|.|965,4871887|.|0,251711652|0 > |.|.|.|.|.|.| > |.|.|secondIn3Hour/10|.|.|.| > |time ms/op|.|.|1484,454|.|95,044|6,4 > |allocation Mb/op|.|.|153,2464722|.|2,001712809|1,3 > |.|.|.|.|.|.| > |.|.|secondInMin/0|.|.|.| > |time ms/op|.|.|875,118|.|424,11|48,5 > |allocation Mb/op|.|.|610,3554993|.|0,001776123|0 > |.|.|.|.|.|.| > |.|.|secondInMin/1000|.|.|.| > |time ms/op|.|.|568,7|.|84,208|14,8 > |allocation Mb/op|.|.|0,007598114|.|0,
[3/3] cassandra git commit: Merge branch cassandra-2.2 into cassandra-3.0
Merge branch cassandra-2.2 into cassandra-3.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/80b79973 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/80b79973 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/80b79973 Branch: refs/heads/cassandra-3.0 Commit: 80b79973a8e6e496eb3b50188afc059daabbe3eb Parents: a2f742c 8405f73 Author: Benjamin Lerer Authored: Wed May 31 15:17:01 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 15:20:20 2017 +0200 -- CHANGES.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/80b79973/CHANGES.txt -- diff --cc CHANGES.txt index 164470f,ef2e12c..6bdb283 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,45 -1,8 +1,44 @@@ -2.2.10 - * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) +3.0.14 ++ * Upgrade JNA version to 4.4.0 (CASSANDRA-13072) + * Interned ColumnIdentifiers should use minimal ByteBuffers (CASSANDRA-13533) + * ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade (CASSANDRA-13525) + * Fix repair process violating start/end token limits for small ranges (CASSANDRA-13052) + * Add storage port options to sstableloader (CASSANDRA-13518) + * Properly handle quoted index names in cqlsh DESCRIBE output (CASSANDRA-12847) + * Avoid reading static row twice from old format sstables (CASSANDRA-13236) + * Fix NPE in StorageService.excise() (CASSANDRA-13163) + * Expire OutboundTcpConnection messages by a single Thread (CASSANDRA-13265) + * Fail repair if insufficient responses received (CASSANDRA-13397) + * Fix SSTableLoader fail when the loaded table contains dropped columns (CASSANDRA-13276) + * Avoid name clashes in CassandraIndexTest (CASSANDRA-13427) + * Handling partially written hint files (CASSANDRA-12728) + * Interrupt replaying hints on decommission (CASSANDRA-13308) + * Fix schema version calculation for rolling upgrades (CASSANDRA-13441) + +3.0.13 + * Make reading of range tombstones more reliable (CASSANDRA-12811) + * Fix startup problems due to schema tables not completely flushed (CASSANDRA-12213) + * Fix view builder bug that can filter out data on restart (CASSANDRA-13405) + * Fix 2i page size calculation when there are no regular columns (CASSANDRA-13400) + * Fix the conversion of 2.X expired rows without regular column data (CASSANDRA-13395) + * Fix hint delivery when using ext+internal IPs with prefer_local enabled (CASSANDRA-13020) + * Fix possible NPE on upgrade to 3.0/3.X in case of IO errors (CASSANDRA-13389) + * Legacy deserializer can create empty range tombstones (CASSANDRA-13341) + * Use the Kernel32 library to retrieve the PID on Windows and fix startup checks (CASSANDRA-1) + * Fix code to not exchange schema across major versions (CASSANDRA-13274) + * Dropping column results in "corrupt" SSTable (CASSANDRA-13337) + * Bugs handling range tombstones in the sstable iterators (CASSANDRA-13340) + * Fix CONTAINS filtering for null collections (CASSANDRA-13246) + * Applying: Use a unique metric reservoir per test run when using Cassandra-wide metrics residing in MBeans (CASSANDRA-13216) + * Propagate row deletions in 2i tables on upgrade (CASSANDRA-13320) + * Slice.isEmpty() returns false for some empty slices (CASSANDRA-13305) + * Add formatted row output to assertEmpty in CQL Tester (CASSANDRA-13238) + * Legacy caching options can prevent 3.0 upgrade (CASSANDRA-13384) + * Nodetool upgradesstables/scrub/compact ignores system tables (CASSANDRA-13410) + * Fix NPE issue in StorageService (CASSANDRA-13060) +Merged from 2.2: - * upgrade JNA version to 4.4.0 (CASSANDRA-13072) - * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) - * Fix JVM metric paths (CASSANDRA-13103) * Honor truststore-password parameter in cassandra-stress (CASSANDRA-12773) * Discard in-flight shadow round responses (CASSANDRA-12653) * Don't anti-compact repaired data to avoid inconsistencies (CASSANDRA-13153) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[2/3] cassandra git commit: Revert "upgrade JNA version to 4.4.0"
Revert "upgrade JNA version to 4.4.0" This reverts commit 3c81aa825de1855a1cfd8de49d946e478d6bb085. Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/8405f736 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/8405f736 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/8405f736 Branch: refs/heads/cassandra-3.0 Commit: 8405f7366f8881951f76c5899cfa699063db7378 Parents: 3c81aa8 Author: Benjamin Lerer Authored: Wed May 31 15:14:22 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 15:14:22 2017 +0200 -- CHANGES.txt| 1 - build.xml | 2 +- lib/jna-4.0.0.jar | Bin 0 -> 914639 bytes lib/jna-4.4.0.jar | Bin 1091208 -> 0 bytes lib/licenses/jna-4.0.0.txt | 202 lib/licenses/jna-4.4.0.txt | 202 6 files changed, 203 insertions(+), 204 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index 4f3fba8..ef2e12c 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,5 +1,4 @@ 2.2.10 - * upgrade JNA version to 4.4.0 (CASSANDRA-13072) * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/build.xml -- diff --git a/build.xml b/build.xml index c50d85b..dc5aecb 100644 --- a/build.xml +++ b/build.xml @@ -382,7 +382,7 @@ - + http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/lib/jna-4.0.0.jar -- diff --git a/lib/jna-4.0.0.jar b/lib/jna-4.0.0.jar new file mode 100644 index 000..9038048 Binary files /dev/null and b/lib/jna-4.0.0.jar differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/lib/jna-4.4.0.jar -- diff --git a/lib/jna-4.4.0.jar b/lib/jna-4.4.0.jar deleted file mode 100644 index 521bd92..000 Binary files a/lib/jna-4.4.0.jar and /dev/null differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/lib/licenses/jna-4.0.0.txt -- diff --git a/lib/licenses/jna-4.0.0.txt b/lib/licenses/jna-4.0.0.txt new file mode 100644 index 000..7a4a3ea --- /dev/null +++ b/lib/licenses/jna-4.0.0.txt @@ -0,0 +1,202 @@ + + Apache License + Version 2.0, January 2004 +http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Wor
[1/3] cassandra git commit: Revert "upgrade JNA version to 4.4.0"
Repository: cassandra Updated Branches: refs/heads/cassandra-2.2 3c81aa825 -> 8405f7366 refs/heads/cassandra-3.0 a2f742cd6 -> 80b79973a Revert "upgrade JNA version to 4.4.0" This reverts commit 3c81aa825de1855a1cfd8de49d946e478d6bb085. Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/8405f736 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/8405f736 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/8405f736 Branch: refs/heads/cassandra-2.2 Commit: 8405f7366f8881951f76c5899cfa699063db7378 Parents: 3c81aa8 Author: Benjamin Lerer Authored: Wed May 31 15:14:22 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 15:14:22 2017 +0200 -- CHANGES.txt| 1 - build.xml | 2 +- lib/jna-4.0.0.jar | Bin 0 -> 914639 bytes lib/jna-4.4.0.jar | Bin 1091208 -> 0 bytes lib/licenses/jna-4.0.0.txt | 202 lib/licenses/jna-4.4.0.txt | 202 6 files changed, 203 insertions(+), 204 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index 4f3fba8..ef2e12c 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,5 +1,4 @@ 2.2.10 - * upgrade JNA version to 4.4.0 (CASSANDRA-13072) * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/build.xml -- diff --git a/build.xml b/build.xml index c50d85b..dc5aecb 100644 --- a/build.xml +++ b/build.xml @@ -382,7 +382,7 @@ - + http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/lib/jna-4.0.0.jar -- diff --git a/lib/jna-4.0.0.jar b/lib/jna-4.0.0.jar new file mode 100644 index 000..9038048 Binary files /dev/null and b/lib/jna-4.0.0.jar differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/lib/jna-4.4.0.jar -- diff --git a/lib/jna-4.4.0.jar b/lib/jna-4.4.0.jar deleted file mode 100644 index 521bd92..000 Binary files a/lib/jna-4.4.0.jar and /dev/null differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/lib/licenses/jna-4.0.0.txt -- diff --git a/lib/licenses/jna-4.0.0.txt b/lib/licenses/jna-4.0.0.txt new file mode 100644 index 000..7a4a3ea --- /dev/null +++ b/lib/licenses/jna-4.0.0.txt @@ -0,0 +1,202 @@ + + Apache License + Version 2.0, January 2004 +http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendi
[3/7] cassandra git commit: Merge branch cassandra-2.2 into cassandra-3.0
Merge branch cassandra-2.2 into cassandra-3.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/80b79973 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/80b79973 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/80b79973 Branch: refs/heads/trunk Commit: 80b79973a8e6e496eb3b50188afc059daabbe3eb Parents: a2f742c 8405f73 Author: Benjamin Lerer Authored: Wed May 31 15:17:01 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 15:20:20 2017 +0200 -- CHANGES.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/80b79973/CHANGES.txt -- diff --cc CHANGES.txt index 164470f,ef2e12c..6bdb283 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,45 -1,8 +1,44 @@@ -2.2.10 - * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) +3.0.14 ++ * Upgrade JNA version to 4.4.0 (CASSANDRA-13072) + * Interned ColumnIdentifiers should use minimal ByteBuffers (CASSANDRA-13533) + * ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade (CASSANDRA-13525) + * Fix repair process violating start/end token limits for small ranges (CASSANDRA-13052) + * Add storage port options to sstableloader (CASSANDRA-13518) + * Properly handle quoted index names in cqlsh DESCRIBE output (CASSANDRA-12847) + * Avoid reading static row twice from old format sstables (CASSANDRA-13236) + * Fix NPE in StorageService.excise() (CASSANDRA-13163) + * Expire OutboundTcpConnection messages by a single Thread (CASSANDRA-13265) + * Fail repair if insufficient responses received (CASSANDRA-13397) + * Fix SSTableLoader fail when the loaded table contains dropped columns (CASSANDRA-13276) + * Avoid name clashes in CassandraIndexTest (CASSANDRA-13427) + * Handling partially written hint files (CASSANDRA-12728) + * Interrupt replaying hints on decommission (CASSANDRA-13308) + * Fix schema version calculation for rolling upgrades (CASSANDRA-13441) + +3.0.13 + * Make reading of range tombstones more reliable (CASSANDRA-12811) + * Fix startup problems due to schema tables not completely flushed (CASSANDRA-12213) + * Fix view builder bug that can filter out data on restart (CASSANDRA-13405) + * Fix 2i page size calculation when there are no regular columns (CASSANDRA-13400) + * Fix the conversion of 2.X expired rows without regular column data (CASSANDRA-13395) + * Fix hint delivery when using ext+internal IPs with prefer_local enabled (CASSANDRA-13020) + * Fix possible NPE on upgrade to 3.0/3.X in case of IO errors (CASSANDRA-13389) + * Legacy deserializer can create empty range tombstones (CASSANDRA-13341) + * Use the Kernel32 library to retrieve the PID on Windows and fix startup checks (CASSANDRA-1) + * Fix code to not exchange schema across major versions (CASSANDRA-13274) + * Dropping column results in "corrupt" SSTable (CASSANDRA-13337) + * Bugs handling range tombstones in the sstable iterators (CASSANDRA-13340) + * Fix CONTAINS filtering for null collections (CASSANDRA-13246) + * Applying: Use a unique metric reservoir per test run when using Cassandra-wide metrics residing in MBeans (CASSANDRA-13216) + * Propagate row deletions in 2i tables on upgrade (CASSANDRA-13320) + * Slice.isEmpty() returns false for some empty slices (CASSANDRA-13305) + * Add formatted row output to assertEmpty in CQL Tester (CASSANDRA-13238) + * Legacy caching options can prevent 3.0 upgrade (CASSANDRA-13384) + * Nodetool upgradesstables/scrub/compact ignores system tables (CASSANDRA-13410) + * Fix NPE issue in StorageService (CASSANDRA-13060) +Merged from 2.2: - * upgrade JNA version to 4.4.0 (CASSANDRA-13072) - * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) - * Fix JVM metric paths (CASSANDRA-13103) * Honor truststore-password parameter in cassandra-stress (CASSANDRA-12773) * Discard in-flight shadow round responses (CASSANDRA-12653) * Don't anti-compact repaired data to avoid inconsistencies (CASSANDRA-13153) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[5/7] cassandra git commit: Merge branch cassandra-3.0 into cassandra-3.11
Merge branch cassandra-3.0 into cassandra-3.11 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/2bd135eb Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/2bd135eb Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/2bd135eb Branch: refs/heads/trunk Commit: 2bd135ebd136484766cd1a1083f9fd3ae8bfc8f9 Parents: 54ff619 80b7997 Author: Benjamin Lerer Authored: Wed May 31 15:23:46 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 15:23:46 2017 +0200 -- CHANGES.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/2bd135eb/CHANGES.txt -- diff --cc CHANGES.txt index 26a8018,6bdb283..4e72464 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,41 -1,5 +1,42 @@@ -3.0.14 +3.11.0 + * Fix formatting of duration columns in CQLSH (CASSANDRA-13549) + * Fix the problem with duplicated rows when using paging with SASI (CASSANDRA-13302) + * Allow CONTAINS statements filtering on the partition key and itâs parts (CASSANDRA-13275) + * Fall back to even ranges calculation in clusters with vnodes when tokens are distributed unevenly (CASSANDRA-13229) + * Fix duration type validation to prevent overflow (CASSANDRA-13218) + * Forbid unsupported creation of SASI indexes over partition key columns (CASSANDRA-13228) + * Reject multiple values for a key in CQL grammar. (CASSANDRA-13369) + * UDA fails without input rows (CASSANDRA-13399) + * Fix compaction-stress by using daemonInitialization (CASSANDRA-13188) + * V5 protocol flags decoding broken (CASSANDRA-13443) + * Use write lock not read lock for removing sstables from compaction strategies. (CASSANDRA-13422) + * Use corePoolSize equal to maxPoolSize in JMXEnabledThreadPoolExecutors (CASSANDRA-13329) + * Avoid rebuilding SASI indexes containing no values (CASSANDRA-12962) + * Add charset to Analyser input stream (CASSANDRA-13151) + * Fix testLimitSSTables flake caused by concurrent flush (CASSANDRA-12820) + * cdc column addition strikes again (CASSANDRA-13382) + * Fix static column indexes (CASSANDRA-13277) + * DataOutputBuffer.asNewBuffer broken (CASSANDRA-13298) + * unittest CipherFactoryTest failed on MacOS (CASSANDRA-13370) + * Forbid SELECT restrictions and CREATE INDEX over non-frozen UDT columns (CASSANDRA-13247) + * Default logging we ship will incorrectly print "?:?" for "%F:%L" pattern (CASSANDRA-13317) + * Possible AssertionError in UnfilteredRowIteratorWithLowerBound (CASSANDRA-13366) + * Support unaligned memory access for AArch64 (CASSANDRA-13326) + * Improve SASI range iterator efficiency on intersection with an empty range (CASSANDRA-12915). + * Fix equality comparisons of columns using the duration type (CASSANDRA-13174) + * Obfuscate password in stress-graphs (CASSANDRA-12233) + * Move to FastThreadLocalThread and FastThreadLocal (CASSANDRA-13034) + * nodetool stopdaemon errors out (CASSANDRA-13030) + * Tables in system_distributed should not use gcgs of 0 (CASSANDRA-12954) + * Fix primary index calculation for SASI (CASSANDRA-12910) + * More fixes to the TokenAllocator (CASSANDRA-12990) + * NoReplicationTokenAllocator should work with zero replication factor (CASSANDRA-12983) + * Address message coalescing regression (CASSANDRA-12676) + * Delete illegal character from StandardTokenizerImpl.jflex (CASSANDRA-13417) + * Fix cqlsh automatic protocol downgrade regression (CASSANDRA-13307) + * Tracing payload not passed from QueryMessage to tracing session (CASSANDRA-12835) +Merged from 3.0: + * Upgrade JNA version to 4.4.0 (CASSANDRA-13072) * Interned ColumnIdentifiers should use minimal ByteBuffers (CASSANDRA-13533) * ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade (CASSANDRA-13525) * Fix repair process violating start/end token limits for small ranges (CASSANDRA-13052) @@@ -69,35 -33,12 +70,33 @@@ * Propagate row deletions in 2i tables on upgrade (CASSANDRA-13320) * Slice.isEmpty() returns false for some empty slices (CASSANDRA-13305) * Add formatted row output to assertEmpty in CQL Tester (CASSANDRA-13238) - * Legacy caching options can prevent 3.0 upgrade (CASSANDRA-13384) + * Prevent data loss on upgrade 2.1 - 3.0 by adding component separator to LogRecord absolute path (CASSANDRA-13294) + * Improve testing on macOS by eliminating sigar logging (CASSANDRA-13233) + * Cqlsh copy-from should error out when csv contains invalid data for collections (CASSANDRA-13071) + * Fix "multiple versions of ant detected..." when running ant test (CASSANDRA-13232) + * Coalescing strategy sleeps too much (CASSANDRA-13090) + * Faster StreamingHistogram (CASSANDRA-13038) + * Legacy deserializer can create unexpected bound
[1/7] cassandra git commit: Revert "upgrade JNA version to 4.4.0"
Repository: cassandra Updated Branches: refs/heads/cassandra-3.11 54ff61931 -> 2bd135ebd refs/heads/trunk ea57a4dbe -> 9bef25efb Revert "upgrade JNA version to 4.4.0" This reverts commit 3c81aa825de1855a1cfd8de49d946e478d6bb085. Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/8405f736 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/8405f736 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/8405f736 Branch: refs/heads/cassandra-3.11 Commit: 8405f7366f8881951f76c5899cfa699063db7378 Parents: 3c81aa8 Author: Benjamin Lerer Authored: Wed May 31 15:14:22 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 15:14:22 2017 +0200 -- CHANGES.txt| 1 - build.xml | 2 +- lib/jna-4.0.0.jar | Bin 0 -> 914639 bytes lib/jna-4.4.0.jar | Bin 1091208 -> 0 bytes lib/licenses/jna-4.0.0.txt | 202 lib/licenses/jna-4.4.0.txt | 202 6 files changed, 203 insertions(+), 204 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index 4f3fba8..ef2e12c 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,5 +1,4 @@ 2.2.10 - * upgrade JNA version to 4.4.0 (CASSANDRA-13072) * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/build.xml -- diff --git a/build.xml b/build.xml index c50d85b..dc5aecb 100644 --- a/build.xml +++ b/build.xml @@ -382,7 +382,7 @@ - + http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/lib/jna-4.0.0.jar -- diff --git a/lib/jna-4.0.0.jar b/lib/jna-4.0.0.jar new file mode 100644 index 000..9038048 Binary files /dev/null and b/lib/jna-4.0.0.jar differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/lib/jna-4.4.0.jar -- diff --git a/lib/jna-4.4.0.jar b/lib/jna-4.4.0.jar deleted file mode 100644 index 521bd92..000 Binary files a/lib/jna-4.4.0.jar and /dev/null differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/lib/licenses/jna-4.0.0.txt -- diff --git a/lib/licenses/jna-4.0.0.txt b/lib/licenses/jna-4.0.0.txt new file mode 100644 index 000..7a4a3ea --- /dev/null +++ b/lib/licenses/jna-4.0.0.txt @@ -0,0 +1,202 @@ + + Apache License + Version 2.0, January 2004 +http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix belo
[7/7] cassandra git commit: Merge branch cassandra-3.11 into trunk
Merge branch cassandra-3.11 into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/9bef25ef Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/9bef25ef Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/9bef25ef Branch: refs/heads/trunk Commit: 9bef25efb3527a00ff97487cfbb38cea1d99d571 Parents: ea57a4d 2bd135e Author: Benjamin Lerer Authored: Wed May 31 15:25:09 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 15:25:09 2017 +0200 -- CHANGES.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/9bef25ef/CHANGES.txt -- diff --cc CHANGES.txt index 0bda3a6,4e72464..0f844a6 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -108,7 -36,9 +108,8 @@@ * Fix cqlsh automatic protocol downgrade regression (CASSANDRA-13307) * Tracing payload not passed from QueryMessage to tracing session (CASSANDRA-12835) Merged from 3.0: + * Upgrade JNA version to 4.4.0 (CASSANDRA-13072) * Interned ColumnIdentifiers should use minimal ByteBuffers (CASSANDRA-13533) - * ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade (CASSANDRA-13525) * Fix repair process violating start/end token limits for small ranges (CASSANDRA-13052) * Add storage port options to sstableloader (CASSANDRA-13518) * Properly handle quoted index names in cqlsh DESCRIBE output (CASSANDRA-12847) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[4/7] cassandra git commit: Merge branch cassandra-2.2 into cassandra-3.0
Merge branch cassandra-2.2 into cassandra-3.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/80b79973 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/80b79973 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/80b79973 Branch: refs/heads/cassandra-3.11 Commit: 80b79973a8e6e496eb3b50188afc059daabbe3eb Parents: a2f742c 8405f73 Author: Benjamin Lerer Authored: Wed May 31 15:17:01 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 15:20:20 2017 +0200 -- CHANGES.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/80b79973/CHANGES.txt -- diff --cc CHANGES.txt index 164470f,ef2e12c..6bdb283 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,45 -1,8 +1,44 @@@ -2.2.10 - * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) +3.0.14 ++ * Upgrade JNA version to 4.4.0 (CASSANDRA-13072) + * Interned ColumnIdentifiers should use minimal ByteBuffers (CASSANDRA-13533) + * ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade (CASSANDRA-13525) + * Fix repair process violating start/end token limits for small ranges (CASSANDRA-13052) + * Add storage port options to sstableloader (CASSANDRA-13518) + * Properly handle quoted index names in cqlsh DESCRIBE output (CASSANDRA-12847) + * Avoid reading static row twice from old format sstables (CASSANDRA-13236) + * Fix NPE in StorageService.excise() (CASSANDRA-13163) + * Expire OutboundTcpConnection messages by a single Thread (CASSANDRA-13265) + * Fail repair if insufficient responses received (CASSANDRA-13397) + * Fix SSTableLoader fail when the loaded table contains dropped columns (CASSANDRA-13276) + * Avoid name clashes in CassandraIndexTest (CASSANDRA-13427) + * Handling partially written hint files (CASSANDRA-12728) + * Interrupt replaying hints on decommission (CASSANDRA-13308) + * Fix schema version calculation for rolling upgrades (CASSANDRA-13441) + +3.0.13 + * Make reading of range tombstones more reliable (CASSANDRA-12811) + * Fix startup problems due to schema tables not completely flushed (CASSANDRA-12213) + * Fix view builder bug that can filter out data on restart (CASSANDRA-13405) + * Fix 2i page size calculation when there are no regular columns (CASSANDRA-13400) + * Fix the conversion of 2.X expired rows without regular column data (CASSANDRA-13395) + * Fix hint delivery when using ext+internal IPs with prefer_local enabled (CASSANDRA-13020) + * Fix possible NPE on upgrade to 3.0/3.X in case of IO errors (CASSANDRA-13389) + * Legacy deserializer can create empty range tombstones (CASSANDRA-13341) + * Use the Kernel32 library to retrieve the PID on Windows and fix startup checks (CASSANDRA-1) + * Fix code to not exchange schema across major versions (CASSANDRA-13274) + * Dropping column results in "corrupt" SSTable (CASSANDRA-13337) + * Bugs handling range tombstones in the sstable iterators (CASSANDRA-13340) + * Fix CONTAINS filtering for null collections (CASSANDRA-13246) + * Applying: Use a unique metric reservoir per test run when using Cassandra-wide metrics residing in MBeans (CASSANDRA-13216) + * Propagate row deletions in 2i tables on upgrade (CASSANDRA-13320) + * Slice.isEmpty() returns false for some empty slices (CASSANDRA-13305) + * Add formatted row output to assertEmpty in CQL Tester (CASSANDRA-13238) + * Legacy caching options can prevent 3.0 upgrade (CASSANDRA-13384) + * Nodetool upgradesstables/scrub/compact ignores system tables (CASSANDRA-13410) + * Fix NPE issue in StorageService (CASSANDRA-13060) +Merged from 2.2: - * upgrade JNA version to 4.4.0 (CASSANDRA-13072) - * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) - * Fix JVM metric paths (CASSANDRA-13103) * Honor truststore-password parameter in cassandra-stress (CASSANDRA-12773) * Discard in-flight shadow round responses (CASSANDRA-12653) * Don't anti-compact repaired data to avoid inconsistencies (CASSANDRA-13153) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[2/7] cassandra git commit: Revert "upgrade JNA version to 4.4.0"
Revert "upgrade JNA version to 4.4.0" This reverts commit 3c81aa825de1855a1cfd8de49d946e478d6bb085. Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/8405f736 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/8405f736 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/8405f736 Branch: refs/heads/trunk Commit: 8405f7366f8881951f76c5899cfa699063db7378 Parents: 3c81aa8 Author: Benjamin Lerer Authored: Wed May 31 15:14:22 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 15:14:22 2017 +0200 -- CHANGES.txt| 1 - build.xml | 2 +- lib/jna-4.0.0.jar | Bin 0 -> 914639 bytes lib/jna-4.4.0.jar | Bin 1091208 -> 0 bytes lib/licenses/jna-4.0.0.txt | 202 lib/licenses/jna-4.4.0.txt | 202 6 files changed, 203 insertions(+), 204 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index 4f3fba8..ef2e12c 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,5 +1,4 @@ 2.2.10 - * upgrade JNA version to 4.4.0 (CASSANDRA-13072) * nodetool upgradesstables should upgrade system tables (CASSANDRA-13119) * Avoid starting gossiper in RemoveTest (CASSANDRA-13407) * Fix weightedSize() for row-cache reported by JMX and NodeTool (CASSANDRA-13393) http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/build.xml -- diff --git a/build.xml b/build.xml index c50d85b..dc5aecb 100644 --- a/build.xml +++ b/build.xml @@ -382,7 +382,7 @@ - + http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/lib/jna-4.0.0.jar -- diff --git a/lib/jna-4.0.0.jar b/lib/jna-4.0.0.jar new file mode 100644 index 000..9038048 Binary files /dev/null and b/lib/jna-4.0.0.jar differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/lib/jna-4.4.0.jar -- diff --git a/lib/jna-4.4.0.jar b/lib/jna-4.4.0.jar deleted file mode 100644 index 521bd92..000 Binary files a/lib/jna-4.4.0.jar and /dev/null differ http://git-wip-us.apache.org/repos/asf/cassandra/blob/8405f736/lib/licenses/jna-4.0.0.txt -- diff --git a/lib/licenses/jna-4.0.0.txt b/lib/licenses/jna-4.0.0.txt new file mode 100644 index 000..7a4a3ea --- /dev/null +++ b/lib/licenses/jna-4.0.0.txt @@ -0,0 +1,202 @@ + + Apache License + Version 2.0, January 2004 +http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and fo
[6/7] cassandra git commit: Merge branch cassandra-3.0 into cassandra-3.11
Merge branch cassandra-3.0 into cassandra-3.11 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/2bd135eb Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/2bd135eb Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/2bd135eb Branch: refs/heads/cassandra-3.11 Commit: 2bd135ebd136484766cd1a1083f9fd3ae8bfc8f9 Parents: 54ff619 80b7997 Author: Benjamin Lerer Authored: Wed May 31 15:23:46 2017 +0200 Committer: Benjamin Lerer Committed: Wed May 31 15:23:46 2017 +0200 -- CHANGES.txt | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/2bd135eb/CHANGES.txt -- diff --cc CHANGES.txt index 26a8018,6bdb283..4e72464 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,41 -1,5 +1,42 @@@ -3.0.14 +3.11.0 + * Fix formatting of duration columns in CQLSH (CASSANDRA-13549) + * Fix the problem with duplicated rows when using paging with SASI (CASSANDRA-13302) + * Allow CONTAINS statements filtering on the partition key and itâs parts (CASSANDRA-13275) + * Fall back to even ranges calculation in clusters with vnodes when tokens are distributed unevenly (CASSANDRA-13229) + * Fix duration type validation to prevent overflow (CASSANDRA-13218) + * Forbid unsupported creation of SASI indexes over partition key columns (CASSANDRA-13228) + * Reject multiple values for a key in CQL grammar. (CASSANDRA-13369) + * UDA fails without input rows (CASSANDRA-13399) + * Fix compaction-stress by using daemonInitialization (CASSANDRA-13188) + * V5 protocol flags decoding broken (CASSANDRA-13443) + * Use write lock not read lock for removing sstables from compaction strategies. (CASSANDRA-13422) + * Use corePoolSize equal to maxPoolSize in JMXEnabledThreadPoolExecutors (CASSANDRA-13329) + * Avoid rebuilding SASI indexes containing no values (CASSANDRA-12962) + * Add charset to Analyser input stream (CASSANDRA-13151) + * Fix testLimitSSTables flake caused by concurrent flush (CASSANDRA-12820) + * cdc column addition strikes again (CASSANDRA-13382) + * Fix static column indexes (CASSANDRA-13277) + * DataOutputBuffer.asNewBuffer broken (CASSANDRA-13298) + * unittest CipherFactoryTest failed on MacOS (CASSANDRA-13370) + * Forbid SELECT restrictions and CREATE INDEX over non-frozen UDT columns (CASSANDRA-13247) + * Default logging we ship will incorrectly print "?:?" for "%F:%L" pattern (CASSANDRA-13317) + * Possible AssertionError in UnfilteredRowIteratorWithLowerBound (CASSANDRA-13366) + * Support unaligned memory access for AArch64 (CASSANDRA-13326) + * Improve SASI range iterator efficiency on intersection with an empty range (CASSANDRA-12915). + * Fix equality comparisons of columns using the duration type (CASSANDRA-13174) + * Obfuscate password in stress-graphs (CASSANDRA-12233) + * Move to FastThreadLocalThread and FastThreadLocal (CASSANDRA-13034) + * nodetool stopdaemon errors out (CASSANDRA-13030) + * Tables in system_distributed should not use gcgs of 0 (CASSANDRA-12954) + * Fix primary index calculation for SASI (CASSANDRA-12910) + * More fixes to the TokenAllocator (CASSANDRA-12990) + * NoReplicationTokenAllocator should work with zero replication factor (CASSANDRA-12983) + * Address message coalescing regression (CASSANDRA-12676) + * Delete illegal character from StandardTokenizerImpl.jflex (CASSANDRA-13417) + * Fix cqlsh automatic protocol downgrade regression (CASSANDRA-13307) + * Tracing payload not passed from QueryMessage to tracing session (CASSANDRA-12835) +Merged from 3.0: + * Upgrade JNA version to 4.4.0 (CASSANDRA-13072) * Interned ColumnIdentifiers should use minimal ByteBuffers (CASSANDRA-13533) * ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade (CASSANDRA-13525) * Fix repair process violating start/end token limits for small ranges (CASSANDRA-13052) @@@ -69,35 -33,12 +70,33 @@@ * Propagate row deletions in 2i tables on upgrade (CASSANDRA-13320) * Slice.isEmpty() returns false for some empty slices (CASSANDRA-13305) * Add formatted row output to assertEmpty in CQL Tester (CASSANDRA-13238) - * Legacy caching options can prevent 3.0 upgrade (CASSANDRA-13384) + * Prevent data loss on upgrade 2.1 - 3.0 by adding component separator to LogRecord absolute path (CASSANDRA-13294) + * Improve testing on macOS by eliminating sigar logging (CASSANDRA-13233) + * Cqlsh copy-from should error out when csv contains invalid data for collections (CASSANDRA-13071) + * Fix "multiple versions of ant detected..." when running ant test (CASSANDRA-13232) + * Coalescing strategy sleeps too much (CASSANDRA-13090) + * Faster StreamingHistogram (CASSANDRA-13038) + * Legacy deserializer can create unexpec
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031144#comment-16031144 ] Jeff Jirsa commented on CASSANDRA-13559: Can someone explain the upgrade path from 3.0.13 to 3.0.14 please? > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13072) Cassandra failed to run on Linux-aarch64
[ https://issues.apache.org/jira/browse/CASSANDRA-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-13072: --- Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed into 2.2 at a2f742cd633ddd650b65f841c50ee96ee1da0ef5 and merged into 3.0, 3.11 and trunk. The commit into 2.2 as then been reverted as discussed in the ticket at 8405f7366f8881951f76c5899cfa699063db7378 > Cassandra failed to run on Linux-aarch64 > > > Key: CASSANDRA-13072 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13072 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: Hardware: ARM aarch64 > OS: Ubuntu 16.04.1 LTS >Reporter: Jun He >Assignee: Benjamin Lerer > Labels: incompatible > Attachments: compat_report.html > > > Steps to reproduce: > 1. Download cassandra latest source > 2. Build it with "ant" > 3. Run with "./bin/cassandra". Daemon is crashed with following error message: > {quote} > INFO 05:30:21 Initializing system.schema_functions > INFO 05:30:21 Initializing system.schema_aggregates > ERROR 05:30:22 Exception in thread Thread[MemtableFlushWriter:1,5,main] > java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native > at > org.apache.cassandra.utils.memory.MemoryUtil.allocate(MemoryUtil.java:97) > ~[main/:na] > at org.apache.cassandra.io.util.Memory.(Memory.java:74) > ~[main/:na] > at org.apache.cassandra.io.util.SafeMemory.(SafeMemory.java:32) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.(CompressionMetadata.java:316) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.open(CompressionMetadata.java:330) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressedSequentialWriter.(CompressedSequentialWriter.java:76) > ~[main/:na] > at > org.apache.cassandra.io.util.SequentialWriter.open(SequentialWriter.java:163) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigTableWriter.(BigTableWriter.java:73) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigFormat$WriterFactory.open(BigFormat.java:93) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.SSTableWriter.create(SSTableWriter.java:96) > ~[main/:na] > at > org.apache.cassandra.io.sstable.SimpleSSTableMultiWriter.create(SimpleSSTableMultiWriter.java:114) > ~[main/:na] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.createSSTableMultiWriter(AbstractCompactionStrategy.java:519) > ~[main/:na] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.createSSTableMultiWriter(CompactionStrategyManager.java:497) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore.createSSTableMultiWriter(ColumnFamilyStore.java:480) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.createFlushWriter(Memtable.java:439) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.writeSortedContents(Memtable.java:371) > ~[main/:na] > at org.apache.cassandra.db.Memtable.flush(Memtable.java:332) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1054) > ~[main/:na] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > ~[na:1.8.0_111] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > ~[na:1.8.0_111] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_111] > {quote} > Analyze: > This issue is caused by bundled jna-4.0.0.jar which doesn't come with aarch64 > native support. Replace lib/jna-4.0.0.jar with jna-4.2.0.jar from > http://central.maven.org/maven2/net/java/dev/jna/jna/4.2.0/ can fix this > problem. > Attached is the binary compatibility report of jna.jar between 4.0 and 4.2. > The result is good (97.4%). So is there possibility to upgrade jna to 4.2.0 > in upstream? Should there be any kind of tests to execute, please kindly > point me. Thanks a lot. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13540) QUORUM CL is used for new superuser
[ https://issues.apache.org/jira/browse/CASSANDRA-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031148#comment-16031148 ] Dennis Noordzij commented on CASSANDRA-13540: - No corresponding errors other than this really. Well, yes, but I removed `SUPERUSER` privileges for the default `cassandra` user. Once all nodes join again, I can login again. > QUORUM CL is used for new superuser > --- > > Key: CASSANDRA-13540 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13540 > Project: Cassandra > Issue Type: Bug > Components: Distributed Metadata >Reporter: Dennis Noordzij > > After bootstrapping Cassandra, we're creating a new superuser, and setting RF > of system_auth keyspace to 2, NetworkTopologyStrategy. Then a nodetool repair > on the system_auth KS. > Documentation says > {quote} > The system_auth keyspace uses a QUORUM consistency level when checking > authentication for the default cassandra user. For all other users created, > superuser or otherwise, a LOCAL_ONE consistency level is used for > authenticating. > {quote} > But for my new superuser, new node members are rejected because QUORUM CL > can't be achieved: > {code} > May 19th 2017, 17:40:14.462 Connection error: ('Unable to connect to any > servers', {'xx.xx.xx.xx': AuthenticationFailed('Failed to authenticate to > xx.xx.xx.xx: Error from server: code=0100 [Bad credentials] > message="org.apache.cassandra.exceptions.UnavailableException: Cannot achieve > consistency level QUORUM"',)}) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13072) Cassandra failed to run on Linux-aarch64
[ https://issues.apache.org/jira/browse/CASSANDRA-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031149#comment-16031149 ] Jeff Jirsa commented on CASSANDRA-13072: Sorry, that's my fault for not being explicit. Here's my thinking: 2.2 and 3.0 are bug-fix-only. The only way this is a bug fix is if aarch64 is a supported platform. It's not a supported platform because there are no tests for it. Therefore, I don't see how this qualifies for either 2.2 or 3.0. This belongs in 3.11 and trunk, unless someone can tell me why I'm wrong. > Cassandra failed to run on Linux-aarch64 > > > Key: CASSANDRA-13072 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13072 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: Hardware: ARM aarch64 > OS: Ubuntu 16.04.1 LTS >Reporter: Jun He >Assignee: Benjamin Lerer > Labels: incompatible > Attachments: compat_report.html > > > Steps to reproduce: > 1. Download cassandra latest source > 2. Build it with "ant" > 3. Run with "./bin/cassandra". Daemon is crashed with following error message: > {quote} > INFO 05:30:21 Initializing system.schema_functions > INFO 05:30:21 Initializing system.schema_aggregates > ERROR 05:30:22 Exception in thread Thread[MemtableFlushWriter:1,5,main] > java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native > at > org.apache.cassandra.utils.memory.MemoryUtil.allocate(MemoryUtil.java:97) > ~[main/:na] > at org.apache.cassandra.io.util.Memory.(Memory.java:74) > ~[main/:na] > at org.apache.cassandra.io.util.SafeMemory.(SafeMemory.java:32) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.(CompressionMetadata.java:316) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.open(CompressionMetadata.java:330) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressedSequentialWriter.(CompressedSequentialWriter.java:76) > ~[main/:na] > at > org.apache.cassandra.io.util.SequentialWriter.open(SequentialWriter.java:163) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigTableWriter.(BigTableWriter.java:73) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigFormat$WriterFactory.open(BigFormat.java:93) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.SSTableWriter.create(SSTableWriter.java:96) > ~[main/:na] > at > org.apache.cassandra.io.sstable.SimpleSSTableMultiWriter.create(SimpleSSTableMultiWriter.java:114) > ~[main/:na] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.createSSTableMultiWriter(AbstractCompactionStrategy.java:519) > ~[main/:na] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.createSSTableMultiWriter(CompactionStrategyManager.java:497) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore.createSSTableMultiWriter(ColumnFamilyStore.java:480) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.createFlushWriter(Memtable.java:439) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.writeSortedContents(Memtable.java:371) > ~[main/:na] > at org.apache.cassandra.db.Memtable.flush(Memtable.java:332) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1054) > ~[main/:na] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > ~[na:1.8.0_111] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > ~[na:1.8.0_111] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_111] > {quote} > Analyze: > This issue is caused by bundled jna-4.0.0.jar which doesn't come with aarch64 > native support. Replace lib/jna-4.0.0.jar with jna-4.2.0.jar from > http://central.maven.org/maven2/net/java/dev/jna/jna/4.2.0/ can fix this > problem. > Attached is the binary compatibility report of jna.jar between 4.0 and 4.2. > The result is good (97.4%). So is there possibility to upgrade jna to 4.2.0 > in upstream? Should there be any kind of tests to execute, please kindly > point me. Thanks a lot. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13540) QUORUM CL is used for new superuser
[ https://issues.apache.org/jira/browse/CASSANDRA-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031151#comment-16031151 ] Dennis Noordzij commented on CASSANDRA-13540: - No corresponding errors other than this really. Well, yes, but I removed `SUPERUSER` privileges for the default `cassandra` user. Once all nodes join again, I can login again. > QUORUM CL is used for new superuser > --- > > Key: CASSANDRA-13540 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13540 > Project: Cassandra > Issue Type: Bug > Components: Distributed Metadata >Reporter: Dennis Noordzij > > After bootstrapping Cassandra, we're creating a new superuser, and setting RF > of system_auth keyspace to 2, NetworkTopologyStrategy. Then a nodetool repair > on the system_auth KS. > Documentation says > {quote} > The system_auth keyspace uses a QUORUM consistency level when checking > authentication for the default cassandra user. For all other users created, > superuser or otherwise, a LOCAL_ONE consistency level is used for > authenticating. > {quote} > But for my new superuser, new node members are rejected because QUORUM CL > can't be achieved: > {code} > May 19th 2017, 17:40:14.462 Connection error: ('Unable to connect to any > servers', {'xx.xx.xx.xx': AuthenticationFailed('Failed to authenticate to > xx.xx.xx.xx: Error from server: code=0100 [Bad credentials] > message="org.apache.cassandra.exceptions.UnavailableException: Cannot achieve > consistency level QUORUM"',)}) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Issue Comment Deleted] (CASSANDRA-13540) QUORUM CL is used for new superuser
[ https://issues.apache.org/jira/browse/CASSANDRA-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Noordzij updated CASSANDRA-13540: Comment: was deleted (was: No corresponding errors other than this really. Well, yes, but I removed `SUPERUSER` privileges for the default `cassandra` user. Once all nodes join again, I can login again. ) > QUORUM CL is used for new superuser > --- > > Key: CASSANDRA-13540 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13540 > Project: Cassandra > Issue Type: Bug > Components: Distributed Metadata >Reporter: Dennis Noordzij > > After bootstrapping Cassandra, we're creating a new superuser, and setting RF > of system_auth keyspace to 2, NetworkTopologyStrategy. Then a nodetool repair > on the system_auth KS. > Documentation says > {quote} > The system_auth keyspace uses a QUORUM consistency level when checking > authentication for the default cassandra user. For all other users created, > superuser or otherwise, a LOCAL_ONE consistency level is used for > authenticating. > {quote} > But for my new superuser, new node members are rejected because QUORUM CL > can't be achieved: > {code} > May 19th 2017, 17:40:14.462 Connection error: ('Unable to connect to any > servers', {'xx.xx.xx.xx': AuthenticationFailed('Failed to authenticate to > xx.xx.xx.xx: Error from server: code=0100 [Bad credentials] > message="org.apache.cassandra.exceptions.UnavailableException: Cannot achieve > consistency level QUORUM"',)}) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-13540) QUORUM CL is used for new superuser
[ https://issues.apache.org/jira/browse/CASSANDRA-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031148#comment-16031148 ] Dennis Noordzij edited comment on CASSANDRA-13540 at 5/31/17 1:31 PM: -- No corresponding errors other than this really. Well, yes, but I removed {{SUPERUSER}} privileges for the default {{cassandra}} user. Once all nodes join again, I can login again. was (Author: denno): No corresponding errors other than this really. Well, yes, but I removed `SUPERUSER` privileges for the default `cassandra` user. Once all nodes join again, I can login again. > QUORUM CL is used for new superuser > --- > > Key: CASSANDRA-13540 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13540 > Project: Cassandra > Issue Type: Bug > Components: Distributed Metadata >Reporter: Dennis Noordzij > > After bootstrapping Cassandra, we're creating a new superuser, and setting RF > of system_auth keyspace to 2, NetworkTopologyStrategy. Then a nodetool repair > on the system_auth KS. > Documentation says > {quote} > The system_auth keyspace uses a QUORUM consistency level when checking > authentication for the default cassandra user. For all other users created, > superuser or otherwise, a LOCAL_ONE consistency level is used for > authenticating. > {quote} > But for my new superuser, new node members are rejected because QUORUM CL > can't be achieved: > {code} > May 19th 2017, 17:40:14.462 Connection error: ('Unable to connect to any > servers', {'xx.xx.xx.xx': AuthenticationFailed('Failed to authenticate to > xx.xx.xx.xx: Error from server: code=0100 [Bad credentials] > message="org.apache.cassandra.exceptions.UnavailableException: Cannot achieve > consistency level QUORUM"',)}) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13072) Cassandra failed to run on Linux-aarch64
[ https://issues.apache.org/jira/browse/CASSANDRA-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031156#comment-16031156 ] Aleksey Yeschenko commented on CASSANDRA-13072: --- I assumed from wording of the ticket that this was a regression, in which case it potentially warranted a JNA upgrade. Otherwise we should probably go for trunk only, as 3.11 is bugfix only at this point. Is this or is this not a regression though? > Cassandra failed to run on Linux-aarch64 > > > Key: CASSANDRA-13072 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13072 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: Hardware: ARM aarch64 > OS: Ubuntu 16.04.1 LTS >Reporter: Jun He >Assignee: Benjamin Lerer > Labels: incompatible > Attachments: compat_report.html > > > Steps to reproduce: > 1. Download cassandra latest source > 2. Build it with "ant" > 3. Run with "./bin/cassandra". Daemon is crashed with following error message: > {quote} > INFO 05:30:21 Initializing system.schema_functions > INFO 05:30:21 Initializing system.schema_aggregates > ERROR 05:30:22 Exception in thread Thread[MemtableFlushWriter:1,5,main] > java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native > at > org.apache.cassandra.utils.memory.MemoryUtil.allocate(MemoryUtil.java:97) > ~[main/:na] > at org.apache.cassandra.io.util.Memory.(Memory.java:74) > ~[main/:na] > at org.apache.cassandra.io.util.SafeMemory.(SafeMemory.java:32) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.(CompressionMetadata.java:316) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.open(CompressionMetadata.java:330) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressedSequentialWriter.(CompressedSequentialWriter.java:76) > ~[main/:na] > at > org.apache.cassandra.io.util.SequentialWriter.open(SequentialWriter.java:163) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigTableWriter.(BigTableWriter.java:73) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigFormat$WriterFactory.open(BigFormat.java:93) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.SSTableWriter.create(SSTableWriter.java:96) > ~[main/:na] > at > org.apache.cassandra.io.sstable.SimpleSSTableMultiWriter.create(SimpleSSTableMultiWriter.java:114) > ~[main/:na] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.createSSTableMultiWriter(AbstractCompactionStrategy.java:519) > ~[main/:na] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.createSSTableMultiWriter(CompactionStrategyManager.java:497) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore.createSSTableMultiWriter(ColumnFamilyStore.java:480) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.createFlushWriter(Memtable.java:439) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.writeSortedContents(Memtable.java:371) > ~[main/:na] > at org.apache.cassandra.db.Memtable.flush(Memtable.java:332) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1054) > ~[main/:na] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > ~[na:1.8.0_111] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > ~[na:1.8.0_111] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_111] > {quote} > Analyze: > This issue is caused by bundled jna-4.0.0.jar which doesn't come with aarch64 > native support. Replace lib/jna-4.0.0.jar with jna-4.2.0.jar from > http://central.maven.org/maven2/net/java/dev/jna/jna/4.2.0/ can fix this > problem. > Attached is the binary compatibility report of jna.jar between 4.0 and 4.2. > The result is good (97.4%). So is there possibility to upgrade jna to 4.2.0 > in upstream? Should there be any kind of tests to execute, please kindly > point me. Thanks a lot. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031159#comment-16031159 ] Aleksey Yeschenko commented on CASSANDRA-13559: --- You face the storm; no way around it it seems. Pragmatically however there will be a lot more people upgrading from versions that aren't 3.0.13 then from the single recently released 3.0.13, so it makes sense to optimise for the majority of the users. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13072) Cassandra failed to run on Linux-aarch64
[ https://issues.apache.org/jira/browse/CASSANDRA-13072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031158#comment-16031158 ] Jeff Jirsa commented on CASSANDRA-13072: Since-version is 2.0.5, which suggests it's a regression. 2.1 is using {{jna-4.0.0}} though, so 2.2 didn't regress, 2.1 did. > Cassandra failed to run on Linux-aarch64 > > > Key: CASSANDRA-13072 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13072 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: Hardware: ARM aarch64 > OS: Ubuntu 16.04.1 LTS >Reporter: Jun He >Assignee: Benjamin Lerer > Labels: incompatible > Attachments: compat_report.html > > > Steps to reproduce: > 1. Download cassandra latest source > 2. Build it with "ant" > 3. Run with "./bin/cassandra". Daemon is crashed with following error message: > {quote} > INFO 05:30:21 Initializing system.schema_functions > INFO 05:30:21 Initializing system.schema_aggregates > ERROR 05:30:22 Exception in thread Thread[MemtableFlushWriter:1,5,main] > java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native > at > org.apache.cassandra.utils.memory.MemoryUtil.allocate(MemoryUtil.java:97) > ~[main/:na] > at org.apache.cassandra.io.util.Memory.(Memory.java:74) > ~[main/:na] > at org.apache.cassandra.io.util.SafeMemory.(SafeMemory.java:32) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.(CompressionMetadata.java:316) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressionMetadata$Writer.open(CompressionMetadata.java:330) > ~[main/:na] > at > org.apache.cassandra.io.compress.CompressedSequentialWriter.(CompressedSequentialWriter.java:76) > ~[main/:na] > at > org.apache.cassandra.io.util.SequentialWriter.open(SequentialWriter.java:163) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigTableWriter.(BigTableWriter.java:73) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.big.BigFormat$WriterFactory.open(BigFormat.java:93) > ~[main/:na] > at > org.apache.cassandra.io.sstable.format.SSTableWriter.create(SSTableWriter.java:96) > ~[main/:na] > at > org.apache.cassandra.io.sstable.SimpleSSTableMultiWriter.create(SimpleSSTableMultiWriter.java:114) > ~[main/:na] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.createSSTableMultiWriter(AbstractCompactionStrategy.java:519) > ~[main/:na] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.createSSTableMultiWriter(CompactionStrategyManager.java:497) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore.createSSTableMultiWriter(ColumnFamilyStore.java:480) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.createFlushWriter(Memtable.java:439) > ~[main/:na] > at > org.apache.cassandra.db.Memtable.writeSortedContents(Memtable.java:371) > ~[main/:na] > at org.apache.cassandra.db.Memtable.flush(Memtable.java:332) > ~[main/:na] > at > org.apache.cassandra.db.ColumnFamilyStore$Flush.run(ColumnFamilyStore.java:1054) > ~[main/:na] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > ~[na:1.8.0_111] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > ~[na:1.8.0_111] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_111] > {quote} > Analyze: > This issue is caused by bundled jna-4.0.0.jar which doesn't come with aarch64 > native support. Replace lib/jna-4.0.0.jar with jna-4.2.0.jar from > http://central.maven.org/maven2/net/java/dev/jna/jna/4.2.0/ can fix this > problem. > Attached is the binary compatibility report of jna.jar between 4.0 and 4.2. > The result is good (97.4%). So is there possibility to upgrade jna to 4.2.0 > in upstream? Should there be any kind of tests to execute, please kindly > point me. Thanks a lot. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031162#comment-16031162 ] Jeff Jirsa commented on CASSANDRA-13559: There are three stack traces in the ticket that aren't just migration storm, and 2 of them are fail-to-startup errors. How does changing the schema version cause any of those? I realize I can go run through minor version uploads and try to hit this myself, but I don't intuitively "get" why those stacks happen with "just" changing the schema version, but it seems likely they'll happen for anyone going 3.0.13 -> 3.0.14. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031170#comment-16031170 ] Aleksey Yeschenko commented on CASSANDRA-13559: --- bq. How does changing the schema version cause any of those? It can't and it doesn't. Those should be separate JIRA tickets, if valid at all. This ticket is only addressing the difference in digest calculation. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031170#comment-16031170 ] Aleksey Yeschenko edited comment on CASSANDRA-13559 at 5/31/17 1:45 PM: bq. How does changing the schema version cause any of those? It can't and it doesn't. Those should be separate JIRA tickets, if valid at all. This patch is only addressing the difference in digest calculation, which is objectively an issue and has been reproduced. was (Author: iamaleksey): bq. How does changing the schema version cause any of those? It can't and it doesn't. Those should be separate JIRA tickets, if valid at all. This ticket is only addressing the difference in digest calculation. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted
[ https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031177#comment-16031177 ] Andrés de la Peña commented on CASSANDRA-10130: --- [~pauloricardomg], definitively the event driven approach is a better idea than the lambda. Here is the updated patch: ||[trunk|https://github.com/apache/cassandra/compare/trunk...adelapena:10130-trunk]|[utests|http://cassci.datastax.com/view/Dev/view/adelapena/job/adelapena-10130-trunk-testall/]|[dtests|http://cassci.datastax.com/view/Dev/view/adelapena/job/adelapena-10130-trunk-dtest/]| There is a new [{{SSTableLoadedNotification}}|https://github.com/adelapena/cassandra/blob/33a603bf89f95a2cfea737572840897fb26c6585/src/java/org/apache/cassandra/notifications/SSTableLoadedNotification.java]. This notification contains the unused list of added SSTables; maybe be could remove them. There is a new attribute named {{areLoaded}} to [{{SSTableAddedNotification}}|https://github.com/adelapena/cassandra/blob/33a603bf89f95a2cfea737572840897fb26c6585/src/java/org/apache/cassandra/notifications/SSTableAddedNotification.java#L27]. This attribute indicates if the added SSTables come from an external source such as streaming or sstableoader. The new {{SSTableLoadedNotification}} is sent by [{{Tracker#addSSTables}}|https://github.com/adelapena/cassandra/blob/33a603bf89f95a2cfea737572840897fb26c6585/src/java/org/apache/cassandra/db/lifecycle/Tracker.java#L204] depending on its new {{areLoaded}} parameter, with the same meaning as in {{SSTableAddedNotification}}. [{{SecondaryIndexManager#buildAllIndexesBlocking}}|https://github.com/adelapena/cassandra/blob/33a603bf89f95a2cfea737572840897fb26c6585/src/java/org/apache/cassandra/index/SecondaryIndexManager.java#L289] is now private and called by [{{SecondaryIndexManager#handleNotification}}|https://github.com/adelapena/cassandra/blob/33a603bf89f95a2cfea737572840897fb26c6585/src/java/org/apache/cassandra/index/SecondaryIndexManager.java#L1231]. > Node failure during 2i update after streaming can have incomplete 2i when > restarted > --- > > Key: CASSANDRA-10130 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10130 > Project: Cassandra > Issue Type: Bug > Components: Coordination >Reporter: Yuki Morishita >Assignee: Andrés de la Peña >Priority: Minor > > Since MV/2i update happens after SSTables are received, node failure during > MV/2i update can leave received SSTables live when restarted while MV/2i are > partially up to date. > We can add some kind of tracking mechanism to automatically rebuild at the > startup, or at least warn user when the node restarts. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031243#comment-16031243 ] Stefania commented on CASSANDRA-13559: -- bq. could you please elaborate a bit further on the .13-.14 upgrade path? When an upgraded node joins the ring, all non-upgraded nodes will pull the schema from it, after 1 minute. They shouldn't pull any longer from this node unless a real schema change happens. Since the schema is identical, a schema pull results in all schema mutations being applied and the schema tables being flushed, nothing else since the delta would be nil. When another node is upgraded and joins, the process repeats itself. Furthermore, the upgraded nodes will see the schema of the non-upgraded nodes as different and pull from them. Eventually the process converges, when all nodes are upgraded the schema versions will be the same. Things visible to the operator should be the schema migrations in the logs. Other noticeable things will be the schema version logged, which will be different after the upgrade, and different schema versions appearing in {{nodetool describecluster|describering}}. Also, in the system local table. This means that if any problems are likely to occur, they will mostly likely be client side, i.e. clients will not see a schema agreement until the upgrade is completed. This might cause issues in some applications. To limit the flow of schema pulls. the schema should not be changed during the upgrade, if at all possible. I'll add a section to NEWS.txt. That's all I could find from code inspection. [~spo...@gmail.com] rightly pointed out in the dev mailing list that the only urgent thing is to pull 3.0.13. We can take our time before releasing 3.0.14, at a minimum we should write an upgrade test. The startup problem is not related to the digest mismatch: the {{ALL}} fields exist, so I don't understand it at all. I also struggle to explain the unknown cf exceptions, they may be unrelated and the upgrade test should shed some light. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) >
[jira] [Comment Edited] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031243#comment-16031243 ] Stefania edited comment on CASSANDRA-13559 at 5/31/17 2:36 PM: --- bq. could you please elaborate a bit further on the .13-.14 upgrade path? When an upgraded node joins the ring, all non-upgraded nodes will pull the schema from it, after 1 minute. They shouldn't pull any longer from this node unless a real schema change happens. Since the schema is identical, a schema pull results in all schema mutations being applied and the schema tables being flushed, nothing else since the delta would be nil. When another node is upgraded and joins, the process repeats itself. Furthermore, the upgraded nodes will see the schema of the non-upgraded nodes as different and pull from them. Eventually the process converges, when all nodes are upgraded the schema versions will be the same. Things visible to the operator should be the schema migrations in the logs. Other noticeable things will be the schema version logged, which will be different after the upgrade, and different schema versions appearing in {{nodetool describecluster|describering}}. Also, in the system local table. This means that if any problems are likely to occur, they will mostly likely be client side, i.e. clients will not see a schema agreement until the upgrade is completed. This might cause issues in some applications. To limit the flow of schema pulls. the schema should not be changed during the upgrade, if at all possible. I'll add a section to NEWS.txt. That's all I could find from code inspection. [~spo...@gmail.com] rightly pointed out in the dev mailing list that the only urgent thing is to pull 3.0.13. We can take our time before releasing 3.0.14, at a minimum we should write an upgrade test. The startup problem is not related to the digest mismatch: the {{ALL}} field exists, so I don't understand it at all. I also struggle to explain the unknown cf exceptions, they are probably unrelated but the upgrade test should shed some light. was (Author: stefania): bq. could you please elaborate a bit further on the .13-.14 upgrade path? When an upgraded node joins the ring, all non-upgraded nodes will pull the schema from it, after 1 minute. They shouldn't pull any longer from this node unless a real schema change happens. Since the schema is identical, a schema pull results in all schema mutations being applied and the schema tables being flushed, nothing else since the delta would be nil. When another node is upgraded and joins, the process repeats itself. Furthermore, the upgraded nodes will see the schema of the non-upgraded nodes as different and pull from them. Eventually the process converges, when all nodes are upgraded the schema versions will be the same. Things visible to the operator should be the schema migrations in the logs. Other noticeable things will be the schema version logged, which will be different after the upgrade, and different schema versions appearing in {{nodetool describecluster|describering}}. Also, in the system local table. This means that if any problems are likely to occur, they will mostly likely be client side, i.e. clients will not see a schema agreement until the upgrade is completed. This might cause issues in some applications. To limit the flow of schema pulls. the schema should not be changed during the upgrade, if at all possible. I'll add a section to NEWS.txt. That's all I could find from code inspection. [~spo...@gmail.com] rightly pointed out in the dev mailing list that the only urgent thing is to pull 3.0.13. We can take our time before releasing 3.0.14, at a minimum we should write an upgrade test. The startup problem is not related to the digest mismatch: the {{ALL}} fields exist, so I don't understand it at all. I also struggle to explain the unknown cf exceptions, they may be unrelated and the upgrade test should shed some light. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031255#comment-16031255 ] Jeff Jirsa commented on CASSANDRA-13559: If this is really just a single version change, this is a tiny nonissue that doesn't justify pulling the package - CASSANDRA-13441 is present in .13 and earlier 3.0 versions will cause far more schema changes than this patch will for anyone upgrading from 2.1/2.2. This is worth fixing, but I don't see why it's worth pulling binaries. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031255#comment-16031255 ] Jeff Jirsa edited comment on CASSANDRA-13559 at 5/31/17 2:48 PM: - If this is really just a single version change, this is a minor issue that doesn't justify pulling the package - CASSANDRA-13441 is present in .13 and earlier 3.0 versions will cause far more schema changes than this patch will for anyone upgrading from 2.1/2.2. This is worth fixing, but I don't see why it's worth pulling binaries. was (Author: jjirsa): If this is really just a single version change, this is a tiny nonissue that doesn't justify pulling the package - CASSANDRA-13441 is present in .13 and earlier 3.0 versions will cause far more schema changes than this patch will for anyone upgrading from 2.1/2.2. This is worth fixing, but I don't see why it's worth pulling binaries. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031268#comment-16031268 ] Aleksey Yeschenko commented on CASSANDRA-13559: --- bq. CASSANDRA-13441 is present in .13 and earlier 3.0 versions will cause far more schema changes than this patch will for anyone upgrading from 2.1/2.2 Yeah, but for people upgrading from 3.0.x that aren't 3.0.13 the fix would still be nice, and there are more of those than people on 3.0.13 - I would assume. Not advocating for pulling binaries. Neither is a an urgent 3.0.14 release necessary imo. But the fix should go in. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031336#comment-16031336 ] Stefan Podkowinski commented on CASSANDRA-13559: There are two different upgrade issues here. Let's not mix those up. *3.0.x -> 3.0.13* Based on the description by [~jay.zhuang] for this ticket, any node on 3.0.x that will be upgraded to the latest 3.0.13 bug fix release, will fail to start. This is the actual point why pulling the .13 release from the download page is probably a good idea, so people won't upgrade their cluster just to find themselves in a situation unable to bring any node up again. *3.0.13 -> 3.0.14 (unrelease)* Some users may already run 3.0.13 (e.g. by upgrading from 2.x or fresh installs). Maybe even on large production clusters. If we change the schema digest calculation in .14 again, we need to make sure that the users on .13 will be able to upgrade to .14 as well without seeing major issues, e.g. with schema migration storms. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031377#comment-16031377 ] Stefano Ortolani commented on CASSANDRA-13559: -- bq. Some users may already run 3.0.13 (e.g. by upgrading from 2.x or fresh installs). I am not quite sure the issue as described by Jay Zhuang was meant to be deterministic. I have upgraded from 3.0.12 to 3.0.13 without issues but the schema change storm. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031391#comment-16031391 ] Stefan Podkowinski commented on CASSANDRA-13559: Regarding the {{NoSuchFieldError}} startup error seems to be caused by some dirty class files. I can always reproduce this locally by doing something like this: {noformat} git checkout cassandra-3.0.12 ant clean jar ccm create 3.0-3n --install-dir=/home/spod/git/cassandra-3.0 -n 3 ccm start ccm node3 stop git checkout cassandra-3.0.13 ant jar # NO CLEAN ccm node3 start {noformat} If I do "ant clean jar" instead, the node is starting up fine. [~jay.zhuang], are you sure you've installed the vanilla Apacha tarbar cleanly on your side? > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13120) Trace and Histogram output misleading
[ https://issues.apache.org/jira/browse/CASSANDRA-13120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031404#comment-16031404 ] Benjamin Lerer commented on CASSANDRA-13120: I took the feedbacks into account and made some new patches for [3.0|https://github.com/apache/cassandra/compare/cassandra-3.0...blerer:13120-3.0], [3.11|https://github.com/apache/cassandra/compare/cassandra-3.11...blerer:13120-3.11] and [trunk|https://github.com/apache/cassandra/compare/trunk...blerer:13120-trunk]. I ran the patch on our internal CI. There are not failures for the unit tests and the failing dtests are not related to the change. > Trace and Histogram output misleading > - > > Key: CASSANDRA-13120 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13120 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Adam Hattrell >Assignee: Benjamin Lerer >Priority: Minor > > If we look at the following output: > {noformat} > [centos@cassandra-c-3]$ nodetool getsstables -- keyspace table > 60ea4399-6b9f-4419-9ccb-ff2e6742de10 > /mnt/cassandra/data/data/keyspace/table-62f30431acf411e69a4ed7dd11246f8a/mc-647146-big-Data.db > /mnt/cassandra/data/data/keyspace/table-62f30431acf411e69a4ed7dd11246f8a/mc-647147-big-Data.db > /mnt/cassandra/data/data/keyspace/table-62f30431acf411e69a4ed7dd11246f8a/mc-647145-big-Data.db > /mnt/cassandra/data/data/keyspace/table-62f30431acf411e69a4ed7dd11246f8a/mc-647152-big-Data.db > /mnt/cassandra/data/data/keyspace/table-62f30431acf411e69a4ed7dd11246f8a/mc-647157-big-Data.db > /mnt/cassandra/data/data/keyspace/table-62f30431acf411e69a4ed7dd11246f8a/mc-648137-big-Data.db > {noformat} > We can see that this key value appears in just 6 sstables. However, when we > run a select against the table and key we get: > {noformat} > Tracing session: a6c81330-d670-11e6-b00b-c1d403fd6e84 > activity > | timestamp | source > | source_elapsed > ---+++ > > Execute CQL3 query | 2017-01-09 13:36:40.419000 | > 10.200.254.141 | 0 > Parsing SELECT * FROM keyspace.table WHERE id = > 60ea4399-6b9f-4419-9ccb-ff2e6742de10; [SharedPool-Worker-2] | > 2017-01-09 13:36:40.419000 | 10.200.254.141 |104 > > Preparing statement [SharedPool-Worker-2] | 2017-01-09 13:36:40.419000 | > 10.200.254.141 |220 > Executing single-partition query on > table [SharedPool-Worker-1]| 2017-01-09 13:36:40.419000 | > 10.200.254.141 |450 > Acquiring > sstable references [SharedPool-Worker-1] | 2017-01-09 13:36:40.419000 | > 10.200.254.141 |477 > Bloom filter allows skipping > sstable 648146 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419000 | > 10.200.254.141 |496 > Bloom filter allows skipping > sstable 648145 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |503 > Key cache hit for > sstable 648140 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |513 > Bloom filter allows skipping > sstable 648135 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |520 > Bloom filter allows skipping > sstable 648130 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |526 > Bloom filter allows skipping > sstable 648048 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |530 > Bloom filter allows skipping > sstable 647749 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |535 > Bloom filter allows skipping > sstable 647404 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |540 > Key cache hit for > sstable 647145 [SharedPool-Worker-1] | 2017-01-09 13:36:40
[jira] [Updated] (CASSANDRA-13120) Trace and Histogram output misleading
[ https://issues.apache.org/jira/browse/CASSANDRA-13120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-13120: --- Status: Patch Available (was: Open) > Trace and Histogram output misleading > - > > Key: CASSANDRA-13120 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13120 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Adam Hattrell >Assignee: Benjamin Lerer >Priority: Minor > > If we look at the following output: > {noformat} > [centos@cassandra-c-3]$ nodetool getsstables -- keyspace table > 60ea4399-6b9f-4419-9ccb-ff2e6742de10 > /mnt/cassandra/data/data/keyspace/table-62f30431acf411e69a4ed7dd11246f8a/mc-647146-big-Data.db > /mnt/cassandra/data/data/keyspace/table-62f30431acf411e69a4ed7dd11246f8a/mc-647147-big-Data.db > /mnt/cassandra/data/data/keyspace/table-62f30431acf411e69a4ed7dd11246f8a/mc-647145-big-Data.db > /mnt/cassandra/data/data/keyspace/table-62f30431acf411e69a4ed7dd11246f8a/mc-647152-big-Data.db > /mnt/cassandra/data/data/keyspace/table-62f30431acf411e69a4ed7dd11246f8a/mc-647157-big-Data.db > /mnt/cassandra/data/data/keyspace/table-62f30431acf411e69a4ed7dd11246f8a/mc-648137-big-Data.db > {noformat} > We can see that this key value appears in just 6 sstables. However, when we > run a select against the table and key we get: > {noformat} > Tracing session: a6c81330-d670-11e6-b00b-c1d403fd6e84 > activity > | timestamp | source > | source_elapsed > ---+++ > > Execute CQL3 query | 2017-01-09 13:36:40.419000 | > 10.200.254.141 | 0 > Parsing SELECT * FROM keyspace.table WHERE id = > 60ea4399-6b9f-4419-9ccb-ff2e6742de10; [SharedPool-Worker-2] | > 2017-01-09 13:36:40.419000 | 10.200.254.141 |104 > > Preparing statement [SharedPool-Worker-2] | 2017-01-09 13:36:40.419000 | > 10.200.254.141 |220 > Executing single-partition query on > table [SharedPool-Worker-1]| 2017-01-09 13:36:40.419000 | > 10.200.254.141 |450 > Acquiring > sstable references [SharedPool-Worker-1] | 2017-01-09 13:36:40.419000 | > 10.200.254.141 |477 > Bloom filter allows skipping > sstable 648146 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419000 | > 10.200.254.141 |496 > Bloom filter allows skipping > sstable 648145 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |503 > Key cache hit for > sstable 648140 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |513 > Bloom filter allows skipping > sstable 648135 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |520 > Bloom filter allows skipping > sstable 648130 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |526 > Bloom filter allows skipping > sstable 648048 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |530 > Bloom filter allows skipping > sstable 647749 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |535 > Bloom filter allows skipping > sstable 647404 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |540 > Key cache hit for > sstable 647145 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |548 > Key cache hit for > sstable 647146 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419001 | > 10.200.254.141 |556 > Key cache hit for > sstable 647147 [SharedPool-Worker-1] | 2017-01-09 13:36:40.419002 | > 10.200.254.141 |564 > Bloom fil
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031411#comment-16031411 ] Aleksey Yeschenko commented on CASSANDRA-13559: --- bq. There are two different upgrade issues here. Let's not mix those up. There is only one confirmed issue here. It's a shame the JIRA is mixed up. We accidentally changed the way the digest is calculated, slightly, in 3.0.13. The issue is increased migration traffic. Not a big deal, but we should roll it back, so that the majority (lagging behind latest, always) is not affected. bq, If we change the schema digest calculation in .14 again, we need to make sure that the users on .13 will be able to upgrade to .14 as well without seeing major issues, e.g. with schema migration storms. Well, we can't, so you have to choose one: 1. prevent extra migration traffic for those migrating from [3.0.0, 3.0.12] to 3.0.14+ 2. prevent extra migration traffic for those migrating from 3.0.13 to 3.0.14+ With 3.0.13 being super fresh, with relatively few people on it (who already went through some extra migrations and survived anyway), I would say (1) is more important than (2). > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031411#comment-16031411 ] Aleksey Yeschenko edited comment on CASSANDRA-13559 at 5/31/17 3:57 PM: bq. There are two different upgrade issues here. Let's not mix those up. There is only one confirmed issue here. It's a shame the JIRA is mixed up. We accidentally changed the way the digest is calculated, slightly, in 3.0.13. The issue is increased migration traffic. Not a big deal, but we should roll it back, so that the majority (lagging behind latest, always) is not affected. bq. If we change the schema digest calculation in .14 again, we need to make sure that the users on .13 will be able to upgrade to .14 as well without seeing major issues, e.g. with schema migration storms. Well, we can't, so you have to choose one: 1. prevent extra migration traffic for those migrating from [3.0.0, 3.0.12] to 3.0.14+ 2. prevent extra migration traffic for those migrating from 3.0.13 to 3.0.14+ With 3.0.13 being super fresh, with relatively few people on it (who already went through some extra migrations and survived anyway), I would say (1) is more important than (2). was (Author: iamaleksey): bq. There are two different upgrade issues here. Let's not mix those up. There is only one confirmed issue here. It's a shame the JIRA is mixed up. We accidentally changed the way the digest is calculated, slightly, in 3.0.13. The issue is increased migration traffic. Not a big deal, but we should roll it back, so that the majority (lagging behind latest, always) is not affected. bq, If we change the schema digest calculation in .14 again, we need to make sure that the users on .13 will be able to upgrade to .14 as well without seeing major issues, e.g. with schema migration storms. Well, we can't, so you have to choose one: 1. prevent extra migration traffic for those migrating from [3.0.0, 3.0.12] to 3.0.14+ 2. prevent extra migration traffic for those migrating from 3.0.13 to 3.0.14+ With 3.0.13 being super fresh, with relatively few people on it (who already went through some extra migrations and survived anyway), I would say (1) is more important than (2). > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > a
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031425#comment-16031425 ] Stefan Podkowinski commented on CASSANDRA-13559: That makes it much clearer, thanks for the wrap up! > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[2/6] cassandra git commit: Fix schema digest mismatch during rolling upgrades from versions before 3.0.13
Fix schema digest mismatch during rolling upgrades from versions before 3.0.13 patch by Jay Zhuang; reviewed by Stefania Alborghetti for CASSANDRA-13559 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/f96a5dc5 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/f96a5dc5 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/f96a5dc5 Branch: refs/heads/cassandra-3.11 Commit: f96a5dc5840c7d1fea99aa450543af8e889c161e Parents: 80b7997 Author: Jay Zhuang Authored: Wed May 31 14:35:37 2017 +0800 Committer: Aleksey Yeschenko Committed: Wed May 31 17:06:41 2017 +0100 -- CHANGES.txt | 5 - src/java/org/apache/cassandra/schema/SchemaKeyspace.java | 9 - 2 files changed, 12 insertions(+), 2 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/f96a5dc5/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index 6bdb283..c75ca87 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 3.0.14 + * Fix schema digest mismatch during rolling upgrades from versions before 3.0.12 (CASSANDRA-13559) * Upgrade JNA version to 4.4.0 (CASSANDRA-13072) * Interned ColumnIdentifiers should use minimal ByteBuffers (CASSANDRA-13533) * ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade (CASSANDRA-13525) @@ -11,10 +12,11 @@ * Fail repair if insufficient responses received (CASSANDRA-13397) * Fix SSTableLoader fail when the loaded table contains dropped columns (CASSANDRA-13276) * Avoid name clashes in CassandraIndexTest (CASSANDRA-13427) - * Handling partially written hint files (CASSANDRA-12728) + * Handling partially written hint files (CASSANDRA-12728) * Interrupt replaying hints on decommission (CASSANDRA-13308) * Fix schema version calculation for rolling upgrades (CASSANDRA-13441) + 3.0.13 * Make reading of range tombstones more reliable (CASSANDRA-12811) * Fix startup problems due to schema tables not completely flushed (CASSANDRA-12213) @@ -50,6 +52,7 @@ Merged from 2.1: * Fix 2ndary index queries on partition keys for tables with static columns CASSANDRA-13147 * Fix ParseError unhashable type list in cqlsh copy from (CASSANDRA-13364) + 3.0.12 * Prevent data loss on upgrade 2.1 - 3.0 by adding component separator to LogRecord absolute path (CASSANDRA-13294) * Improve testing on macOS by eliminating sigar logging (CASSANDRA-13233) http://git-wip-us.apache.org/repos/asf/cassandra/blob/f96a5dc5/src/java/org/apache/cassandra/schema/SchemaKeyspace.java -- diff --git a/src/java/org/apache/cassandra/schema/SchemaKeyspace.java b/src/java/org/apache/cassandra/schema/SchemaKeyspace.java index e860c59..8719b2f 100644 --- a/src/java/org/apache/cassandra/schema/SchemaKeyspace.java +++ b/src/java/org/apache/cassandra/schema/SchemaKeyspace.java @@ -97,6 +97,13 @@ public final class SchemaKeyspace public static final ImmutableList ALL = ImmutableList.of(COLUMNS, DROPPED_COLUMNS, TRIGGERS, TYPES, FUNCTIONS, AGGREGATES, INDEXES, TABLES, VIEWS, KEYSPACES); +/** + * Until we upgrade the messaging service version, that is version 4.0, we must preserve the old order (before CASSANDRA-12213) + * for digest calculations, otherwise the nodes will never agree on the schema during a rolling upgrade, see CASSANDRA-13559. + */ +public static final ImmutableList ALL_FOR_DIGEST = +ImmutableList.of(KEYSPACES, TABLES, COLUMNS, DROPPED_COLUMNS, TRIGGERS, VIEWS, TYPES, FUNCTIONS, AGGREGATES, INDEXES); + private static final CFMetaData Keyspaces = compile(KEYSPACES, "keyspace definitions", @@ -308,7 +315,7 @@ public final class SchemaKeyspace throw new RuntimeException(e); } -for (String table : ALL) +for (String table : ALL_FOR_DIGEST) { // Due to CASSANDRA-11050 we want to exclude DROPPED_COLUMNS for schema digest computation. We can and // should remove that in the next major release (so C* 4.0). - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[4/6] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.11
Merge branch 'cassandra-3.0' into cassandra-3.11 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/88fa1697 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/88fa1697 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/88fa1697 Branch: refs/heads/trunk Commit: 88fa1697773391910094849f15c5096616972bcf Parents: 2bd135e f96a5dc Author: Aleksey Yeschenko Authored: Wed May 31 17:13:13 2017 +0100 Committer: Aleksey Yeschenko Committed: Wed May 31 17:13:13 2017 +0100 -- CHANGES.txt | 2 ++ src/java/org/apache/cassandra/schema/SchemaKeyspace.java | 10 +- 2 files changed, 11 insertions(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/88fa1697/CHANGES.txt -- diff --cc CHANGES.txt index 4e72464,c75ca87..b28f75f --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,41 -1,5 +1,42 @@@ -3.0.14 +3.11.0 + * Fix formatting of duration columns in CQLSH (CASSANDRA-13549) + * Fix the problem with duplicated rows when using paging with SASI (CASSANDRA-13302) + * Allow CONTAINS statements filtering on the partition key and itâs parts (CASSANDRA-13275) + * Fall back to even ranges calculation in clusters with vnodes when tokens are distributed unevenly (CASSANDRA-13229) + * Fix duration type validation to prevent overflow (CASSANDRA-13218) + * Forbid unsupported creation of SASI indexes over partition key columns (CASSANDRA-13228) + * Reject multiple values for a key in CQL grammar. (CASSANDRA-13369) + * UDA fails without input rows (CASSANDRA-13399) + * Fix compaction-stress by using daemonInitialization (CASSANDRA-13188) + * V5 protocol flags decoding broken (CASSANDRA-13443) + * Use write lock not read lock for removing sstables from compaction strategies. (CASSANDRA-13422) + * Use corePoolSize equal to maxPoolSize in JMXEnabledThreadPoolExecutors (CASSANDRA-13329) + * Avoid rebuilding SASI indexes containing no values (CASSANDRA-12962) + * Add charset to Analyser input stream (CASSANDRA-13151) + * Fix testLimitSSTables flake caused by concurrent flush (CASSANDRA-12820) + * cdc column addition strikes again (CASSANDRA-13382) + * Fix static column indexes (CASSANDRA-13277) + * DataOutputBuffer.asNewBuffer broken (CASSANDRA-13298) + * unittest CipherFactoryTest failed on MacOS (CASSANDRA-13370) + * Forbid SELECT restrictions and CREATE INDEX over non-frozen UDT columns (CASSANDRA-13247) + * Default logging we ship will incorrectly print "?:?" for "%F:%L" pattern (CASSANDRA-13317) + * Possible AssertionError in UnfilteredRowIteratorWithLowerBound (CASSANDRA-13366) + * Support unaligned memory access for AArch64 (CASSANDRA-13326) + * Improve SASI range iterator efficiency on intersection with an empty range (CASSANDRA-12915). + * Fix equality comparisons of columns using the duration type (CASSANDRA-13174) + * Obfuscate password in stress-graphs (CASSANDRA-12233) + * Move to FastThreadLocalThread and FastThreadLocal (CASSANDRA-13034) + * nodetool stopdaemon errors out (CASSANDRA-13030) + * Tables in system_distributed should not use gcgs of 0 (CASSANDRA-12954) + * Fix primary index calculation for SASI (CASSANDRA-12910) + * More fixes to the TokenAllocator (CASSANDRA-12990) + * NoReplicationTokenAllocator should work with zero replication factor (CASSANDRA-12983) + * Address message coalescing regression (CASSANDRA-12676) + * Delete illegal character from StandardTokenizerImpl.jflex (CASSANDRA-13417) + * Fix cqlsh automatic protocol downgrade regression (CASSANDRA-13307) + * Tracing payload not passed from QueryMessage to tracing session (CASSANDRA-12835) +Merged from 3.0: + * Fix schema digest mismatch during rolling upgrades from versions before 3.0.12 (CASSANDRA-13559) * Upgrade JNA version to 4.4.0 (CASSANDRA-13072) * Interned ColumnIdentifiers should use minimal ByteBuffers (CASSANDRA-13533) * ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade (CASSANDRA-13525) @@@ -108,134 -70,25 +109,135 @@@ Merged from 2.2 * Fix failing COPY TO STDOUT (CASSANDRA-12497) * Fix ColumnCounter::countAll behaviour for reverse queries (CASSANDRA-13222) * Exceptions encountered calling getSeeds() breaks OTC thread (CASSANDRA-13018) + * Fix negative mean latency metric (CASSANDRA-12876) + * Use only one file pointer when creating commitlog segments (CASSANDRA-12539) Merged from 2.1: + * Fix 2ndary index queries on partition keys for tables with static columns (CASSANDRA-13147) + * Fix ParseError unhashable type list in cqlsh copy from (CASSANDRA-13364) * Remove unused repositories (CASSANDRA-13278) * Log stacktrace of uncaught exceptions (CASSANDRA-13108) + * Use portable stderr
[6/6] cassandra git commit: Merge branch 'cassandra-3.11' into trunk
Merge branch 'cassandra-3.11' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/3e0a911b Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/3e0a911b Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/3e0a911b Branch: refs/heads/trunk Commit: 3e0a911b30a057a0418593fc906f6c6e038b9325 Parents: 9bef25e 88fa169 Author: Aleksey Yeschenko Authored: Wed May 31 17:16:01 2017 +0100 Committer: Aleksey Yeschenko Committed: Wed May 31 17:16:01 2017 +0100 -- CHANGES.txt | 2 ++ 1 file changed, 2 insertions(+) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/3e0a911b/CHANGES.txt -- diff --cc CHANGES.txt index 0f844a6,b28f75f..07fa8d9 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -108,8 -36,10 +108,9 @@@ * Fix cqlsh automatic protocol downgrade regression (CASSANDRA-13307) * Tracing payload not passed from QueryMessage to tracing session (CASSANDRA-12835) Merged from 3.0: + * Fix schema digest mismatch during rolling upgrades from versions before 3.0.12 (CASSANDRA-13559) * Upgrade JNA version to 4.4.0 (CASSANDRA-13072) * Interned ColumnIdentifiers should use minimal ByteBuffers (CASSANDRA-13533) - * ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade (CASSANDRA-13525) * Fix repair process violating start/end token limits for small ranges (CASSANDRA-13052) * Add storage port options to sstableloader (CASSANDRA-13518) * Properly handle quoted index names in cqlsh DESCRIBE output (CASSANDRA-12847) @@@ -187,9 -118,9 +188,10 @@@ Merged from 2.1 * Log stacktrace of uncaught exceptions (CASSANDRA-13108) * Use portable stderr for java error in startup (CASSANDRA-13211) * Fix Thread Leak in OutboundTcpConnection (CASSANDRA-13204) + * Upgrade netty version to fix memory leak with client encryption (CASSANDRA-13114) * Coalescing strategy can enter infinite loop (CASSANDRA-13159) + 3.10 * Fix secondary index queries regression (CASSANDRA-13013) * Add duration type to the protocol V5 (CASSANDRA-12850) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[5/6] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.11
Merge branch 'cassandra-3.0' into cassandra-3.11 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/88fa1697 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/88fa1697 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/88fa1697 Branch: refs/heads/cassandra-3.11 Commit: 88fa1697773391910094849f15c5096616972bcf Parents: 2bd135e f96a5dc Author: Aleksey Yeschenko Authored: Wed May 31 17:13:13 2017 +0100 Committer: Aleksey Yeschenko Committed: Wed May 31 17:13:13 2017 +0100 -- CHANGES.txt | 2 ++ src/java/org/apache/cassandra/schema/SchemaKeyspace.java | 10 +- 2 files changed, 11 insertions(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/88fa1697/CHANGES.txt -- diff --cc CHANGES.txt index 4e72464,c75ca87..b28f75f --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,41 -1,5 +1,42 @@@ -3.0.14 +3.11.0 + * Fix formatting of duration columns in CQLSH (CASSANDRA-13549) + * Fix the problem with duplicated rows when using paging with SASI (CASSANDRA-13302) + * Allow CONTAINS statements filtering on the partition key and itâs parts (CASSANDRA-13275) + * Fall back to even ranges calculation in clusters with vnodes when tokens are distributed unevenly (CASSANDRA-13229) + * Fix duration type validation to prevent overflow (CASSANDRA-13218) + * Forbid unsupported creation of SASI indexes over partition key columns (CASSANDRA-13228) + * Reject multiple values for a key in CQL grammar. (CASSANDRA-13369) + * UDA fails without input rows (CASSANDRA-13399) + * Fix compaction-stress by using daemonInitialization (CASSANDRA-13188) + * V5 protocol flags decoding broken (CASSANDRA-13443) + * Use write lock not read lock for removing sstables from compaction strategies. (CASSANDRA-13422) + * Use corePoolSize equal to maxPoolSize in JMXEnabledThreadPoolExecutors (CASSANDRA-13329) + * Avoid rebuilding SASI indexes containing no values (CASSANDRA-12962) + * Add charset to Analyser input stream (CASSANDRA-13151) + * Fix testLimitSSTables flake caused by concurrent flush (CASSANDRA-12820) + * cdc column addition strikes again (CASSANDRA-13382) + * Fix static column indexes (CASSANDRA-13277) + * DataOutputBuffer.asNewBuffer broken (CASSANDRA-13298) + * unittest CipherFactoryTest failed on MacOS (CASSANDRA-13370) + * Forbid SELECT restrictions and CREATE INDEX over non-frozen UDT columns (CASSANDRA-13247) + * Default logging we ship will incorrectly print "?:?" for "%F:%L" pattern (CASSANDRA-13317) + * Possible AssertionError in UnfilteredRowIteratorWithLowerBound (CASSANDRA-13366) + * Support unaligned memory access for AArch64 (CASSANDRA-13326) + * Improve SASI range iterator efficiency on intersection with an empty range (CASSANDRA-12915). + * Fix equality comparisons of columns using the duration type (CASSANDRA-13174) + * Obfuscate password in stress-graphs (CASSANDRA-12233) + * Move to FastThreadLocalThread and FastThreadLocal (CASSANDRA-13034) + * nodetool stopdaemon errors out (CASSANDRA-13030) + * Tables in system_distributed should not use gcgs of 0 (CASSANDRA-12954) + * Fix primary index calculation for SASI (CASSANDRA-12910) + * More fixes to the TokenAllocator (CASSANDRA-12990) + * NoReplicationTokenAllocator should work with zero replication factor (CASSANDRA-12983) + * Address message coalescing regression (CASSANDRA-12676) + * Delete illegal character from StandardTokenizerImpl.jflex (CASSANDRA-13417) + * Fix cqlsh automatic protocol downgrade regression (CASSANDRA-13307) + * Tracing payload not passed from QueryMessage to tracing session (CASSANDRA-12835) +Merged from 3.0: + * Fix schema digest mismatch during rolling upgrades from versions before 3.0.12 (CASSANDRA-13559) * Upgrade JNA version to 4.4.0 (CASSANDRA-13072) * Interned ColumnIdentifiers should use minimal ByteBuffers (CASSANDRA-13533) * ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade (CASSANDRA-13525) @@@ -108,134 -70,25 +109,135 @@@ Merged from 2.2 * Fix failing COPY TO STDOUT (CASSANDRA-12497) * Fix ColumnCounter::countAll behaviour for reverse queries (CASSANDRA-13222) * Exceptions encountered calling getSeeds() breaks OTC thread (CASSANDRA-13018) + * Fix negative mean latency metric (CASSANDRA-12876) + * Use only one file pointer when creating commitlog segments (CASSANDRA-12539) Merged from 2.1: + * Fix 2ndary index queries on partition keys for tables with static columns (CASSANDRA-13147) + * Fix ParseError unhashable type list in cqlsh copy from (CASSANDRA-13364) * Remove unused repositories (CASSANDRA-13278) * Log stacktrace of uncaught exceptions (CASSANDRA-13108) + * Use portab
[1/6] cassandra git commit: Fix schema digest mismatch during rolling upgrades from versions before 3.0.13
Repository: cassandra Updated Branches: refs/heads/cassandra-3.0 80b79973a -> f96a5dc58 refs/heads/cassandra-3.11 2bd135ebd -> 88fa16977 refs/heads/trunk 9bef25efb -> 3e0a911b3 Fix schema digest mismatch during rolling upgrades from versions before 3.0.13 patch by Jay Zhuang; reviewed by Stefania Alborghetti for CASSANDRA-13559 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/f96a5dc5 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/f96a5dc5 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/f96a5dc5 Branch: refs/heads/cassandra-3.0 Commit: f96a5dc5840c7d1fea99aa450543af8e889c161e Parents: 80b7997 Author: Jay Zhuang Authored: Wed May 31 14:35:37 2017 +0800 Committer: Aleksey Yeschenko Committed: Wed May 31 17:06:41 2017 +0100 -- CHANGES.txt | 5 - src/java/org/apache/cassandra/schema/SchemaKeyspace.java | 9 - 2 files changed, 12 insertions(+), 2 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/f96a5dc5/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index 6bdb283..c75ca87 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 3.0.14 + * Fix schema digest mismatch during rolling upgrades from versions before 3.0.12 (CASSANDRA-13559) * Upgrade JNA version to 4.4.0 (CASSANDRA-13072) * Interned ColumnIdentifiers should use minimal ByteBuffers (CASSANDRA-13533) * ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade (CASSANDRA-13525) @@ -11,10 +12,11 @@ * Fail repair if insufficient responses received (CASSANDRA-13397) * Fix SSTableLoader fail when the loaded table contains dropped columns (CASSANDRA-13276) * Avoid name clashes in CassandraIndexTest (CASSANDRA-13427) - * Handling partially written hint files (CASSANDRA-12728) + * Handling partially written hint files (CASSANDRA-12728) * Interrupt replaying hints on decommission (CASSANDRA-13308) * Fix schema version calculation for rolling upgrades (CASSANDRA-13441) + 3.0.13 * Make reading of range tombstones more reliable (CASSANDRA-12811) * Fix startup problems due to schema tables not completely flushed (CASSANDRA-12213) @@ -50,6 +52,7 @@ Merged from 2.1: * Fix 2ndary index queries on partition keys for tables with static columns CASSANDRA-13147 * Fix ParseError unhashable type list in cqlsh copy from (CASSANDRA-13364) + 3.0.12 * Prevent data loss on upgrade 2.1 - 3.0 by adding component separator to LogRecord absolute path (CASSANDRA-13294) * Improve testing on macOS by eliminating sigar logging (CASSANDRA-13233) http://git-wip-us.apache.org/repos/asf/cassandra/blob/f96a5dc5/src/java/org/apache/cassandra/schema/SchemaKeyspace.java -- diff --git a/src/java/org/apache/cassandra/schema/SchemaKeyspace.java b/src/java/org/apache/cassandra/schema/SchemaKeyspace.java index e860c59..8719b2f 100644 --- a/src/java/org/apache/cassandra/schema/SchemaKeyspace.java +++ b/src/java/org/apache/cassandra/schema/SchemaKeyspace.java @@ -97,6 +97,13 @@ public final class SchemaKeyspace public static final ImmutableList ALL = ImmutableList.of(COLUMNS, DROPPED_COLUMNS, TRIGGERS, TYPES, FUNCTIONS, AGGREGATES, INDEXES, TABLES, VIEWS, KEYSPACES); +/** + * Until we upgrade the messaging service version, that is version 4.0, we must preserve the old order (before CASSANDRA-12213) + * for digest calculations, otherwise the nodes will never agree on the schema during a rolling upgrade, see CASSANDRA-13559. + */ +public static final ImmutableList ALL_FOR_DIGEST = +ImmutableList.of(KEYSPACES, TABLES, COLUMNS, DROPPED_COLUMNS, TRIGGERS, VIEWS, TYPES, FUNCTIONS, AGGREGATES, INDEXES); + private static final CFMetaData Keyspaces = compile(KEYSPACES, "keyspace definitions", @@ -308,7 +315,7 @@ public final class SchemaKeyspace throw new RuntimeException(e); } -for (String table : ALL) +for (String table : ALL_FOR_DIGEST) { // Due to CASSANDRA-11050 we want to exclude DROPPED_COLUMNS for schema digest computation. We can and // should remove that in the next major release (so C* 4.0). - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[3/6] cassandra git commit: Fix schema digest mismatch during rolling upgrades from versions before 3.0.13
Fix schema digest mismatch during rolling upgrades from versions before 3.0.13 patch by Jay Zhuang; reviewed by Stefania Alborghetti for CASSANDRA-13559 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/f96a5dc5 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/f96a5dc5 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/f96a5dc5 Branch: refs/heads/trunk Commit: f96a5dc5840c7d1fea99aa450543af8e889c161e Parents: 80b7997 Author: Jay Zhuang Authored: Wed May 31 14:35:37 2017 +0800 Committer: Aleksey Yeschenko Committed: Wed May 31 17:06:41 2017 +0100 -- CHANGES.txt | 5 - src/java/org/apache/cassandra/schema/SchemaKeyspace.java | 9 - 2 files changed, 12 insertions(+), 2 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/f96a5dc5/CHANGES.txt -- diff --git a/CHANGES.txt b/CHANGES.txt index 6bdb283..c75ca87 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 3.0.14 + * Fix schema digest mismatch during rolling upgrades from versions before 3.0.12 (CASSANDRA-13559) * Upgrade JNA version to 4.4.0 (CASSANDRA-13072) * Interned ColumnIdentifiers should use minimal ByteBuffers (CASSANDRA-13533) * ReverseIndexedReader may drop rows during 2.1 to 3.0 upgrade (CASSANDRA-13525) @@ -11,10 +12,11 @@ * Fail repair if insufficient responses received (CASSANDRA-13397) * Fix SSTableLoader fail when the loaded table contains dropped columns (CASSANDRA-13276) * Avoid name clashes in CassandraIndexTest (CASSANDRA-13427) - * Handling partially written hint files (CASSANDRA-12728) + * Handling partially written hint files (CASSANDRA-12728) * Interrupt replaying hints on decommission (CASSANDRA-13308) * Fix schema version calculation for rolling upgrades (CASSANDRA-13441) + 3.0.13 * Make reading of range tombstones more reliable (CASSANDRA-12811) * Fix startup problems due to schema tables not completely flushed (CASSANDRA-12213) @@ -50,6 +52,7 @@ Merged from 2.1: * Fix 2ndary index queries on partition keys for tables with static columns CASSANDRA-13147 * Fix ParseError unhashable type list in cqlsh copy from (CASSANDRA-13364) + 3.0.12 * Prevent data loss on upgrade 2.1 - 3.0 by adding component separator to LogRecord absolute path (CASSANDRA-13294) * Improve testing on macOS by eliminating sigar logging (CASSANDRA-13233) http://git-wip-us.apache.org/repos/asf/cassandra/blob/f96a5dc5/src/java/org/apache/cassandra/schema/SchemaKeyspace.java -- diff --git a/src/java/org/apache/cassandra/schema/SchemaKeyspace.java b/src/java/org/apache/cassandra/schema/SchemaKeyspace.java index e860c59..8719b2f 100644 --- a/src/java/org/apache/cassandra/schema/SchemaKeyspace.java +++ b/src/java/org/apache/cassandra/schema/SchemaKeyspace.java @@ -97,6 +97,13 @@ public final class SchemaKeyspace public static final ImmutableList ALL = ImmutableList.of(COLUMNS, DROPPED_COLUMNS, TRIGGERS, TYPES, FUNCTIONS, AGGREGATES, INDEXES, TABLES, VIEWS, KEYSPACES); +/** + * Until we upgrade the messaging service version, that is version 4.0, we must preserve the old order (before CASSANDRA-12213) + * for digest calculations, otherwise the nodes will never agree on the schema during a rolling upgrade, see CASSANDRA-13559. + */ +public static final ImmutableList ALL_FOR_DIGEST = +ImmutableList.of(KEYSPACES, TABLES, COLUMNS, DROPPED_COLUMNS, TRIGGERS, VIEWS, TYPES, FUNCTIONS, AGGREGATES, INDEXES); + private static final CFMetaData Keyspaces = compile(KEYSPACES, "keyspace definitions", @@ -308,7 +315,7 @@ public final class SchemaKeyspace throw new RuntimeException(e); } -for (String table : ALL) +for (String table : ALL_FOR_DIGEST) { // Due to CASSANDRA-11050 we want to exclude DROPPED_COLUMNS for schema digest computation. We can and // should remove that in the next major release (so C* 4.0). - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031444#comment-16031444 ] Aleksey Yeschenko commented on CASSANDRA-13559: --- Committed to 3.0 as [f96a5dc5840c7d1fea99aa450543af8e889c161e|https://github.com/apache/cassandra/commit/f96a5dc5840c7d1fea99aa450543af8e889c161e] and merged into 3.11, trunk omitted. Thanks. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031442#comment-16031442 ] Jay Zhuang commented on CASSANDRA-13559: Thanks [~Stefania] for the quick fix. For a normal upgrade, I don't see the fail to start issue. For call stack: {noformat} ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception encountered during startup java.lang.IllegalArgumentException: Unknown CF 83c8eae0-3a65-11e7-9a27-e17fd11571e3 {noformat} It happens when the schema is changed while upgrading. For our case, a few nodes are not upgraded, so we have a cluster with mixed versions (3.0.x and 3.0.13) which causes this issue. For {noformat} Exception (java.lang.NoSuchFieldError) encountered during startup: ALL java.lang.NoSuchFieldError: ALL at org.apache.cassandra.service.ClientState.(ClientState.java:67) at org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) at org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) at org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) at org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) at org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) at org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) at org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) at org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) {noformat} I don't think it's caused by this issue. Schema version id mismatch also happens when upgrading from 2.2.x -> 3.0.x and maybe other major/minor version upgrade. I guess it not worthing pulling 3.0.13 binaries. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.se
[jira] [Comment Edited] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031442#comment-16031442 ] Jay Zhuang edited comment on CASSANDRA-13559 at 5/31/17 4:18 PM: - Thanks [~Stefania] for the quick fix. For a normal upgrade, I don't see the fail to start issue. For call stack: {noformat} ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception encountered during startup java.lang.IllegalArgumentException: Unknown CF 83c8eae0-3a65-11e7-9a27-e17fd11571e3 {noformat} It happens when the schema is changed while upgrading. For our case, a few nodes are not upgraded, so we have a cluster with mixed versions (3.0.x and 3.0.13) which causes this issue. For {noformat} Exception (java.lang.NoSuchFieldError) encountered during startup: ALL java.lang.NoSuchFieldError: ALL {noformat} I don't think it's caused by this issue. Schema version id mismatch also happens when upgrading from 2.2.x -> 3.0.x and maybe other major/minor version upgrade. I guess it not worthing pulling 3.0.13 binaries. was (Author: jay.zhuang): Thanks [~Stefania] for the quick fix. For a normal upgrade, I don't see the fail to start issue. For call stack: {noformat} ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception encountered during startup java.lang.IllegalArgumentException: Unknown CF 83c8eae0-3a65-11e7-9a27-e17fd11571e3 {noformat} It happens when the schema is changed while upgrading. For our case, a few nodes are not upgraded, so we have a cluster with mixed versions (3.0.x and 3.0.13) which causes this issue. For {noformat} Exception (java.lang.NoSuchFieldError) encountered during startup: ALL java.lang.NoSuchFieldError: ALL at org.apache.cassandra.service.ClientState.(ClientState.java:67) at org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) at org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) at org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) at org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) at org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) at org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) at org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) at org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) {noformat} I don't think it's caused by this issue. Schema version id mismatch also happens when upgrading from 2.2.x -> 3.0.x and maybe other major/minor version upgrade. I guess it not worthing pulling 3.0.13 binaries. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Stefania >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(Clie
[jira] [Assigned] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko reassigned CASSANDRA-13559: - Assignee: Jay Zhuang (was: Stefania) > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Blocker > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031442#comment-16031442 ] Jay Zhuang edited comment on CASSANDRA-13559 at 5/31/17 4:19 PM: - Thanks [~Stefania] for the quick fix. For a normal upgrade, I don't see the "fail to start" issue. For call stack: {noformat} ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception encountered during startup java.lang.IllegalArgumentException: Unknown CF 83c8eae0-3a65-11e7-9a27-e17fd11571e3 {noformat} It happens when the schema is changed while upgrading. For our case, a few nodes are not upgraded, so we have a cluster with mixed versions (3.0.x and 3.0.13) which causes this issue. For {noformat} Exception (java.lang.NoSuchFieldError) encountered during startup: ALL java.lang.NoSuchFieldError: ALL {noformat} I don't think it's caused by this issue. Schema version id mismatch also happens when upgrading from 2.2.x -> 3.0.x and maybe other major/minor version upgrade. I guess it not worthing pulling 3.0.13 binaries. was (Author: jay.zhuang): Thanks [~Stefania] for the quick fix. For a normal upgrade, I don't see the fail to start issue. For call stack: {noformat} ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception encountered during startup java.lang.IllegalArgumentException: Unknown CF 83c8eae0-3a65-11e7-9a27-e17fd11571e3 {noformat} It happens when the schema is changed while upgrading. For our case, a few nodes are not upgraded, so we have a cluster with mixed versions (3.0.x and 3.0.13) which causes this issue. For {noformat} Exception (java.lang.NoSuchFieldError) encountered during startup: ALL java.lang.NoSuchFieldError: ALL {noformat} I don't think it's caused by this issue. Schema version id mismatch also happens when upgrading from 2.2.x -> 3.0.x and maybe other major/minor version upgrade. I guess it not worthing pulling 3.0.13 binaries. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Blocker > Fix For: 3.0.14, 3.11.0 > > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.m
[jira] [Updated] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-13559: -- Resolution: Fixed Fix Version/s: 3.11.0 3.0.14 Status: Resolved (was: Ready to Commit) > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Blocker > Fix For: 3.0.14, 3.11.0 > > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-13559: -- Reviewer: Stefania (was: Robert Stupp) > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Blocker > Fix For: 3.0.14, 3.11.0 > > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031448#comment-16031448 ] Aleksey Yeschenko commented on CASSANDRA-13559: --- [~jay.zhuang] Feel free to continue in a new JIRA ticket to handle your remaining issues. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Blocker > Fix For: 3.0.14, 3.11.0 > > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:697) > {noformat} > I would suggest to have the older list back for digest calculation and > release 3.0.14. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031442#comment-16031442 ] Jay Zhuang edited comment on CASSANDRA-13559 at 5/31/17 4:23 PM: - Thanks [~Stefania] for the quick fix. For a normal upgrade, I don't see the "fail to start" issue. For call stack: {noformat} ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception encountered during startup java.lang.IllegalArgumentException: Unknown CF 83c8eae0-3a65-11e7-9a27-e17fd11571e3 {noformat} It happens when the schema is changed while upgrading. For our case, a few nodes are not upgraded, so we have a cluster with mixed versions (3.0.x and 3.0.13) plus we add a table during that time which causes this issue. For {noformat} Exception (java.lang.NoSuchFieldError) encountered during startup: ALL java.lang.NoSuchFieldError: ALL {noformat} I don't think it's caused by this issue. Schema version id mismatch also happens when upgrading from 2.2.x -> 3.0.x and maybe other major/minor version upgrade. I think it not worthing pulling 3.0.13 binaries. was (Author: jay.zhuang): Thanks [~Stefania] for the quick fix. For a normal upgrade, I don't see the "fail to start" issue. For call stack: {noformat} ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception encountered during startup java.lang.IllegalArgumentException: Unknown CF 83c8eae0-3a65-11e7-9a27-e17fd11571e3 {noformat} It happens when the schema is changed while upgrading. For our case, a few nodes are not upgraded, so we have a cluster with mixed versions (3.0.x and 3.0.13) which causes this issue. For {noformat} Exception (java.lang.NoSuchFieldError) encountered during startup: ALL java.lang.NoSuchFieldError: ALL {noformat} I don't think it's caused by this issue. Schema version id mismatch also happens when upgrading from 2.2.x -> 3.0.x and maybe other major/minor version upgrade. I guess it not worthing pulling 3.0.13 binaries. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Blocker > Fix For: 3.0.14, 3.11.0 > > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:569) > at > org.apa
[jira] [Comment Edited] (CASSANDRA-13559) Schema version id mismatch while upgrading to 3.0.13
[ https://issues.apache.org/jira/browse/CASSANDRA-13559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031442#comment-16031442 ] Jay Zhuang edited comment on CASSANDRA-13559 at 5/31/17 4:23 PM: - Thanks [~Stefania] for the quick fix. For a normal upgrade, I don't see the "fail to start" issue. For call stack: {noformat} ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception encountered during startup java.lang.IllegalArgumentException: Unknown CF 83c8eae0-3a65-11e7-9a27-e17fd11571e3 {noformat} It happens when the schema is changed while upgrading. For our case, a few nodes are not upgraded, so we have a cluster with mixed versions (3.0.x and 3.0.13) plus we add a table during that time which causes this issue. For {noformat} Exception (java.lang.NoSuchFieldError) encountered during startup: ALL java.lang.NoSuchFieldError: ALL {noformat} I don't think it's caused by this issue. Schema version id mismatch also happens when upgrading from 2.2.x -> 3.0.x and maybe other major/minor version upgrade. I think it not worth pulling 3.0.13 binaries. was (Author: jay.zhuang): Thanks [~Stefania] for the quick fix. For a normal upgrade, I don't see the "fail to start" issue. For call stack: {noformat} ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception encountered during startup java.lang.IllegalArgumentException: Unknown CF 83c8eae0-3a65-11e7-9a27-e17fd11571e3 {noformat} It happens when the schema is changed while upgrading. For our case, a few nodes are not upgraded, so we have a cluster with mixed versions (3.0.x and 3.0.13) plus we add a table during that time which causes this issue. For {noformat} Exception (java.lang.NoSuchFieldError) encountered during startup: ALL java.lang.NoSuchFieldError: ALL {noformat} I don't think it's caused by this issue. Schema version id mismatch also happens when upgrading from 2.2.x -> 3.0.x and maybe other major/minor version upgrade. I think it not worthing pulling 3.0.13 binaries. > Schema version id mismatch while upgrading to 3.0.13 > > > Key: CASSANDRA-13559 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13559 > Project: Cassandra > Issue Type: Bug > Components: Core >Reporter: Jay Zhuang >Assignee: Jay Zhuang >Priority: Blocker > Fix For: 3.0.14, 3.11.0 > > > As the order of SchemaKeyspace is changed ([6991556 | > https://github.com/apache/cassandra/commit/6991556e431a51575744248a4c484270c4f918c9], > CASSANDRA-12213), the result of function > [{{calculateSchemaDigest}}|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/schema/SchemaKeyspace.java#L311] > is also changed for the same schema. Which causes schema mismatch while > upgrading 3.0.x -> 3.0.13. > It could cause cassandra fail to start because Unknown CF exception. And > streaming will fail: > {noformat} > ERROR [main] 2017-05-26 18:58:57,572 CassandraDaemon.java:709 - Exception > encountered during startup > java.lang.IllegalArgumentException: Unknown CF > 83c8eae0-3a65-11e7-9a27-e17fd11571e3 > {noformat} > {noformat} > WARN [MessagingService-Incoming-/IP] 2017-05-26 19:27:11,523 > IncomingTcpConnection.java:101 - UnknownColumnFamilyException reading from > socket; closing > org.apache.cassandra.db.UnknownColumnFamilyException: Couldn't find table for > cfId 922b7940-3a65-11e7-adf3-a3ff55d9bcf1. If a table was just created, this > is likely due to the schema not being fully propagated. Please wait for > schema agreement on table creation. > {noformat} > Restart the new node will cause: > {noformat} > Exception (java.lang.NoSuchFieldError) encountered during startup: ALL > java.lang.NoSuchFieldError: ALL > at > org.apache.cassandra.service.ClientState.(ClientState.java:67) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:155) > at > org.apache.cassandra.cql3.QueryProcessor$InternalStateInstance.(QueryProcessor.java:149) > at > org.apache.cassandra.cql3.QueryProcessor.internalQueryState(QueryProcessor.java:163) > at > org.apache.cassandra.cql3.QueryProcessor.prepareInternal(QueryProcessor.java:286) > at > org.apache.cassandra.cql3.QueryProcessor.executeInternal(QueryProcessor.java:294) > at > org.apache.cassandra.db.SystemKeyspace.checkHealth(SystemKeyspace.java:900) > at > org.apache.cassandra.service.StartupChecks$9.execute(StartupChecks.java:354) > at > org.apache.cassandra.service.StartupChecks.verify(StartupChecks.java:110) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:179) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon
[jira] [Created] (CASSANDRA-13565) Materialized view usage of commit logs requires large mutation but commitlog_segment_size_in_mb=2048 causes exception
Tania S Engel created CASSANDRA-13565: - Summary: Materialized view usage of commit logs requires large mutation but commitlog_segment_size_in_mb=2048 causes exception Key: CASSANDRA-13565 URL: https://issues.apache.org/jira/browse/CASSANDRA-13565 Project: Cassandra Issue Type: Bug Components: Configuration, Materialized Views, Streaming and Messaging Environment: Cassandra 3.9.0, Windows Reporter: Tania S Engel We will be upgrading to 3.10 for CASSANDRA-11670. However, there is another scenario (not applyunsafe during JOIN) which leads to : java.lang.IllegalArgumentException: Mutation of 525.847MiB is too large for the maximum size of 512.000MiB at org.apache.cassandra.db.commitlog.CommitLog.add(CommitLog.java:262) ~[apache-cassandra-3.9.0.jar:3.9.0] at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:493) ~[apache-cassandra-3.9.0.jar:3.9.0] at org.apache.cassandra.db.Keyspace.apply(Keyspace.java:396) ~[apache-cassandra-3.9.0.jar:3.9.0] at org.apache.cassandra.db.Mutation.applyFuture(Mutation.java:215) ~[apache-cassandra-3.9.0.jar:3.9.0] at org.apache.cassandra.db.Mutation.apply(Mutation.java:227) ~[apache-cassandra-3.9.0.jar:3.9.0] at org.apache.cassandra.batchlog.BatchlogManager.store(BatchlogManager.java:147) ~[apache-cassandra-3.9.0.jar:3.9.0] at org.apache.cassandra.service.StorageProxy.mutateMV(StorageProxy.java:797) ~[apache-cassandra-3.9.0.jar:3.9.0] at org.apache.cassandra.db.view.ViewBuilder.buildKey(ViewBuilder.java:96) ~[apache-cassandra-3.9.0.jar:3.9.0] at org.apache.cassandra.db.view.ViewBuilder.run(ViewBuilder.java:165) ~[apache-cassandra-3.9.0.jar:3.9.0] at org.apache.cassandra.db.compaction.CompactionManager$14.run(CompactionManager.java:1591) [apache-cassandra-3.9.0.jar:3.9.0] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_66] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_66] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_66] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_66] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_66] Due to the relationship of max_mutation_size_in_kb and commitlog_segment_size_in_mb, we increased commitlog_segment_size_in_mb and left Cassandra to calculate max_mutation_size_in_kb as half the size commitlog_segment_size_in_mb * 1024. However, we have found that if we set commitlog_segment_size_in_mb=2048 we get an exception upon starting Cassandra, when it is creating a new commit log. ERROR [COMMIT-LOG-ALLOCATOR] 2017-05-31 17:01:48,005 JVMStabilityInspector.java:82 - Exiting due to error while processing commit log during initialization. org.apache.cassandra.io.FSWriteError: java.io.IOException: An attempt was made to move the file pointer before the beginning of the file Perhaps the index you are using is not big enough and it goes negative. Is the relationship between max_mutation_size_in_kb and commitlog_segment_size_in_mb important to preserve? In our limited stress test we are finding mutation size already over 512mb and we expect more data in our sstables and associated materialized views. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted
[ https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031557#comment-16031557 ] Andrés de la Peña commented on CASSANDRA-10130: --- And here is an alternative version of the patch in which [{{SSTableAddedNotification}}|https://github.com/adelapena/cassandra/blob/10130-trunk-memtable/src/java/org/apache/cassandra/notifications/SSTableAddedNotification.java#L31] uses the origin {{Memtable}} instead of the boolean parameter: ||[trunk|https://github.com/apache/cassandra/compare/trunk...adelapena:10130-trunk-memtable]|[utests|http://cassci.datastax.com/view/Dev/view/adelapena/job/adelapena-10130-trunk-memtable-testall/]|[dtests|http://cassci.datastax.com/view/Dev/view/adelapena/job/adelapena-10130-trunk-memtable-dtest/]| Probably the boolean argument if strictly enough but consumers could be interested in the {{Memtable}}. > Node failure during 2i update after streaming can have incomplete 2i when > restarted > --- > > Key: CASSANDRA-10130 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10130 > Project: Cassandra > Issue Type: Bug > Components: Coordination >Reporter: Yuki Morishita >Assignee: Andrés de la Peña >Priority: Minor > > Since MV/2i update happens after SSTables are received, node failure during > MV/2i update can leave received SSTables live when restarted while MV/2i are > partially up to date. > We can add some kind of tracking mechanism to automatically rebuild at the > startup, or at least warn user when the node restarts. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[03/11] cassandra git commit: 13426: work in progress
http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/src/java/org/apache/cassandra/schema/Schema.java -- diff --git a/src/java/org/apache/cassandra/schema/Schema.java b/src/java/org/apache/cassandra/schema/Schema.java index 6dc63aa..37af5a3 100644 --- a/src/java/org/apache/cassandra/schema/Schema.java +++ b/src/java/org/apache/cassandra/schema/Schema.java @@ -17,7 +17,6 @@ */ package org.apache.cassandra.schema; -import java.nio.ByteBuffer; import java.util.*; import java.util.concurrent.CopyOnWriteArrayList; import java.util.stream.Collectors; @@ -42,6 +41,8 @@ import org.apache.cassandra.exceptions.InvalidRequestException; import org.apache.cassandra.exceptions.UnknownTableException; import org.apache.cassandra.io.sstable.Descriptor; import org.apache.cassandra.locator.LocalStrategy; +import org.apache.cassandra.schema.KeyspaceMetadata.KeyspaceDiff; +import org.apache.cassandra.schema.Keyspaces.KeyspacesDiff; import org.apache.cassandra.utils.Pair; import org.cliffc.high_scale_lib.NonBlockingHashMap; @@ -110,22 +111,12 @@ public final class Schema */ public void loadFromDisk(boolean updateVersion) { -load(SchemaKeyspace.fetchNonSystemKeyspaces()); +SchemaKeyspace.fetchNonSystemKeyspaces().forEach(this::load); if (updateVersion) updateVersion(); } /** - * Load up non-system keyspaces - * - * @param keyspaceDefs The non-system keyspace definitions - */ -private void load(Iterable keyspaceDefs) -{ -keyspaceDefs.forEach(this::load); -} - -/** * Update (or insert) new keyspace definition * * @param ksm The metadata about keyspace @@ -152,53 +143,49 @@ public final class Schema .forEach((name, metadata) -> indexMetadataRefs.put(Pair.create(ksm.name, name), new TableMetadataRef(metadata))); } +synchronized KeyspacesDiff apply(SchemaTransformation transformation) +{ +Keyspaces before = keyspaces; +Keyspaces after = transformation.apply(before); + +KeyspacesDiff diff = Keyspaces.diff(before, after, Diff.Mode.IN_MEMORY); + +//keyspaces = after; TODO, more efficient this way +merge(diff); + +return diff; +} + private void reload(KeyspaceMetadata previous, KeyspaceMetadata updated) { Keyspace keyspace = getKeyspaceInstance(updated.name); -if (keyspace != null) +if (null != keyspace) keyspace.setMetadata(updated); -MapDifference tablesDiff = previous.tables.diff(updated.tables); -MapDifference viewsDiff = previous.views.diff(updated.views); +Tables.TablesDiff tablesDiff = Tables.diff(previous.tables, updated.tables, Diff.Mode.IN_MEMORY); +Views.ViewsDiff viewsDiff = Views.diff(previous.views, updated.views, Diff.Mode.IN_MEMORY); + MapDifference indexesDiff = previous.tables.indexesDiff(updated.tables); // clean up after removed entries - -tablesDiff.entriesOnlyOnLeft() - .values() - .forEach(table -> metadataRefs.remove(table.id)); - -viewsDiff.entriesOnlyOnLeft() - .values() - .forEach(view -> metadataRefs.remove(view.metadata.id)); +tablesDiff.dropped.forEach(table -> metadataRefs.remove(table.id)); +viewsDiff.dropped.forEach(view -> metadataRefs.remove(view.metadata.id)); indexesDiff.entriesOnlyOnLeft() .values() .forEach(indexTable -> indexMetadataRefs.remove(Pair.create(indexTable.keyspace, indexTable.indexName().get(; // load up new entries - -tablesDiff.entriesOnlyOnRight() - .values() - .forEach(table -> metadataRefs.put(table.id, new TableMetadataRef(table))); - -viewsDiff.entriesOnlyOnRight() - .values() - .forEach(view -> metadataRefs.put(view.metadata.id, new TableMetadataRef(view.metadata))); +tablesDiff.created.forEach(table -> metadataRefs.put(table.id, new TableMetadataRef(table))); +viewsDiff.created.forEach(view -> metadataRefs.put(view.metadata.id, new TableMetadataRef(view.metadata))); indexesDiff.entriesOnlyOnRight() .values() .forEach(indexTable -> indexMetadataRefs.put(Pair.create(indexTable.keyspace, indexTable.indexName().get()), new TableMetadataRef(indexTable))); // refresh refs to updated ones - -tablesDiff.entriesDiffering() - .values() - .forEach(diff -> metadataRefs.get(diff.rightValue().id).set(diff.rightValue())); - -viewsDiff.entriesDiffering() - .values() - .forEach(diff -> metadataRefs.get(diff.rightValue().metadata.id).set(diff.rightValue().metadata)); +tablesDiff
[02/11] cassandra git commit: 13426: work in progress
http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/src/java/org/apache/cassandra/transport/messages/ExecuteMessage.java -- diff --git a/src/java/org/apache/cassandra/transport/messages/ExecuteMessage.java b/src/java/org/apache/cassandra/transport/messages/ExecuteMessage.java index d881e63..1dd0bc6 100644 --- a/src/java/org/apache/cassandra/transport/messages/ExecuteMessage.java +++ b/src/java/org/apache/cassandra/transport/messages/ExecuteMessage.java @@ -26,7 +26,7 @@ import org.apache.cassandra.cql3.CQLStatement; import org.apache.cassandra.cql3.ColumnSpecification; import org.apache.cassandra.cql3.QueryHandler; import org.apache.cassandra.cql3.QueryOptions; -import org.apache.cassandra.cql3.statements.ParsedStatement; +import org.apache.cassandra.cql3.QueryProcessor; import org.apache.cassandra.exceptions.PreparedQueryNotFoundException; import org.apache.cassandra.service.ClientState; import org.apache.cassandra.service.QueryState; @@ -92,12 +92,12 @@ public class ExecuteMessage extends Message.Request try { QueryHandler handler = ClientState.getCQLQueryHandler(); -ParsedStatement.Prepared prepared = handler.getPrepared(statementId); +QueryProcessor.Prepared prepared = handler.getPrepared(statementId); if (prepared == null) throw new PreparedQueryNotFoundException(statementId); -options.prepare(prepared.boundNames); CQLStatement statement = prepared.statement; +options.prepare(statement.getBindVariables()); if (options.getPageSize() == 0) throw new ProtocolException("The page size cannot be 0"); @@ -122,9 +122,9 @@ public class ExecuteMessage extends Message.Request builder.put("serial_consistency_level", options.getSerialConsistency().name()); builder.put("query", prepared.rawCQLStatement); -for(int i=0;i 1000 ) @@ -142,7 +142,7 @@ public class ExecuteMessage extends Message.Request // Some custom QueryHandlers are interested by the bound names. We provide them this information // by wrapping the QueryOptions. -QueryOptions queryOptions = QueryOptions.addColumnSpecifications(options, prepared.boundNames); +QueryOptions queryOptions = QueryOptions.addColumnSpecifications(options, statement.getBindVariables()); Message.Response response = handler.processPrepared(statement, state, queryOptions, getCustomPayload(), queryStartNanoTime); if (options.skipMetadata() && response instanceof ResultMessage.Rows) ((ResultMessage.Rows)response).result.metadata.setSkipMetadata(); http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/src/java/org/apache/cassandra/transport/messages/ResultMessage.java -- diff --git a/src/java/org/apache/cassandra/transport/messages/ResultMessage.java b/src/java/org/apache/cassandra/transport/messages/ResultMessage.java index e1ea948..a04f4ff 100644 --- a/src/java/org/apache/cassandra/transport/messages/ResultMessage.java +++ b/src/java/org/apache/cassandra/transport/messages/ResultMessage.java @@ -23,7 +23,6 @@ import io.netty.buffer.ByteBuf; import org.apache.cassandra.cql3.CQLStatement; import org.apache.cassandra.cql3.ResultSet; import org.apache.cassandra.cql3.statements.SelectStatement; -import org.apache.cassandra.cql3.statements.ParsedStatement; import org.apache.cassandra.transport.*; import org.apache.cassandra.utils.MD5Digest; @@ -260,9 +259,9 @@ public abstract class ResultMessage extends Message.Response /** Describes the results of executing this prepared statement */ public final ResultSet.ResultMetadata resultMetadata; -public Prepared(MD5Digest statementId, ParsedStatement.Prepared prepared) +public Prepared(MD5Digest statementId, CQLStatement prepared) { -this(statementId, new ResultSet.PreparedMetadata(prepared.boundNames, prepared.partitionKeyBindIndexes), extractResultMetadata(prepared.statement)); +this(statementId, new ResultSet.PreparedMetadata(prepared.getBindVariables(), prepared.getPartitionKeyBindVariableIndexes()), extractResultMetadata(prepared)); } private Prepared(MD5Digest statementId, ResultSet.PreparedMetadata metadata, ResultSet.ResultMetadata resultMetadata) http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/src/java/org/apache/cassandra/triggers/TriggerExecutor.java -- diff --git a/src/java/org/apache/cassandra/triggers/TriggerExecutor.java b/src/java/org/apache/cassandra/triggers/TriggerExecutor.java index 906b342..3442a9c 100644 --- a/src/java/org/apache/cassandra/triggers/TriggerExecutor.ja
[11/11] cassandra git commit: 13426: CREATE OR REPLACE AGGREGATE
13426: CREATE OR REPLACE AGGREGATE Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/b30c6da2 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/b30c6da2 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/b30c6da2 Branch: refs/heads/13426 Commit: b30c6da2da0b69faaa303bc2245b0b7b9a641701 Parents: aaddbd4 Author: Aleksey Yeschenko Authored: Fri May 19 13:21:35 2017 +0100 Committer: Aleksey Yeschenko Committed: Wed May 31 18:51:15 2017 +0100 -- src/antlr/Cql.g | 1 + src/antlr/Parser.g | 4 +- .../apache/cassandra/auth/FunctionResource.java | 5 + .../statements/CreateAggregateStatement.java| 256 --- .../schema/CreateAggregateStatement.java| 136 -- .../schema/CreateFunctionStatement.java | 1 - .../org/apache/cassandra/schema/Functions.java | 2 +- .../cassandra/schema/MigrationManager.java | 8 - .../apache/cassandra/schema/SchemaKeyspace.java | 12 +- .../validation/operations/AggregationTest.java | 41 ++- 10 files changed, 145 insertions(+), 321 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/b30c6da2/src/antlr/Cql.g -- diff --git a/src/antlr/Cql.g b/src/antlr/Cql.g index e0d5b3f..576a65d 100644 --- a/src/antlr/Cql.g +++ b/src/antlr/Cql.g @@ -48,6 +48,7 @@ import Parser,Lexer; import org.apache.cassandra.cql3.statements.*; import org.apache.cassandra.cql3.statements.schema.AlterKeyspaceStatement; import org.apache.cassandra.cql3.statements.schema.AlterViewStatement; +import org.apache.cassandra.cql3.statements.schema.CreateAggregateStatement; import org.apache.cassandra.cql3.statements.schema.CreateIndexStatement; import org.apache.cassandra.cql3.statements.schema.CreateKeyspaceStatement; import org.apache.cassandra.cql3.statements.schema.CreateTableStatement; http://git-wip-us.apache.org/repos/asf/cassandra/blob/b30c6da2/src/antlr/Parser.g -- diff --git a/src/antlr/Parser.g b/src/antlr/Parser.g index e93dac9..1b230c6 100644 --- a/src/antlr/Parser.g +++ b/src/antlr/Parser.g @@ -630,7 +630,7 @@ batchStatementObjective returns [ModificationStatement.Parsed statement] | d=deleteStatement { $statement = d; } ; -createAggregateStatement returns [CreateAggregateStatement expr] +createAggregateStatement returns [CreateAggregateStatement.Raw stmt] @init { boolean orReplace = false; boolean ifNotExists = false; @@ -655,7 +655,7 @@ createAggregateStatement returns [CreateAggregateStatement expr] ( K_INITCOND ival = term )? - { $expr = new CreateAggregateStatement(fn, argsTypes, sfunc, stype, ffunc, ival, orReplace, ifNotExists); } + { $stmt = new CreateAggregateStatement.Raw(fn, argsTypes, stype, sfunc, ffunc, ival, orReplace, ifNotExists); } ; dropAggregateStatement returns [DropAggregateStatement.Raw stmt] http://git-wip-us.apache.org/repos/asf/cassandra/blob/b30c6da2/src/java/org/apache/cassandra/auth/FunctionResource.java -- diff --git a/src/java/org/apache/cassandra/auth/FunctionResource.java b/src/java/org/apache/cassandra/auth/FunctionResource.java index 3e112cb..79497ef 100644 --- a/src/java/org/apache/cassandra/auth/FunctionResource.java +++ b/src/java/org/apache/cassandra/auth/FunctionResource.java @@ -162,6 +162,11 @@ public class FunctionResource implements IResource return new FunctionResource(keyspace, name, abstractTypes); } +public static FunctionResource functionFromCql(FunctionName name, List argTypes) +{ +return functionFromCql(name.keyspace, name.name, argTypes); +} + /** * Parses a resource name into a FunctionResource instance. * http://git-wip-us.apache.org/repos/asf/cassandra/blob/b30c6da2/src/java/org/apache/cassandra/cql3/statements/CreateAggregateStatement.java -- diff --git a/src/java/org/apache/cassandra/cql3/statements/CreateAggregateStatement.java b/src/java/org/apache/cassandra/cql3/statements/CreateAggregateStatement.java deleted file mode 100644 index 878195f..000 --- a/src/java/org/apache/cassandra/cql3/statements/CreateAggregateStatement.java +++ /dev/null @@ -1,256 +0,0 @@ -/* - * Licensed to the Apache Software Foundation (ASF) under one - * or more contributor license agreements. See the NOTICE file - * distributed with this work for additional information - * regarding copyright ownership. The ASF licenses this file - * to you under the Apache Lic
[07/11] cassandra git commit: 13426: work in progress
http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/src/java/org/apache/cassandra/cql3/statements/DropFunctionStatement.java -- diff --git a/src/java/org/apache/cassandra/cql3/statements/DropFunctionStatement.java b/src/java/org/apache/cassandra/cql3/statements/DropFunctionStatement.java deleted file mode 100644 index 87bfff8..000 --- a/src/java/org/apache/cassandra/cql3/statements/DropFunctionStatement.java +++ /dev/null @@ -1,189 +0,0 @@ -/* - * Licensed to the Apache Software Foundation (ASF) under one - * or more contributor license agreements. See the NOTICE file - * distributed with this work for additional information - * regarding copyright ownership. The ASF licenses this file - * to you under the Apache License, Version 2.0 (the - * "License"); you may not use this file except in compliance - * with the License. You may obtain a copy of the License at - * - * http://www.apache.org/licenses/LICENSE-2.0 - * - * Unless required by applicable law or agreed to in writing, software - * distributed under the License is distributed on an "AS IS" BASIS, - * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - * See the License for the specific language governing permissions and - * limitations under the License. - */ -package org.apache.cassandra.cql3.statements; - -import java.util.ArrayList; -import java.util.Collection; -import java.util.List; - -import com.google.common.base.Joiner; - -import org.apache.cassandra.auth.FunctionResource; -import org.apache.cassandra.auth.Permission; -import org.apache.cassandra.cql3.CQL3Type; -import org.apache.cassandra.cql3.functions.*; -import org.apache.cassandra.db.marshal.AbstractType; -import org.apache.cassandra.exceptions.InvalidRequestException; -import org.apache.cassandra.exceptions.RequestValidationException; -import org.apache.cassandra.exceptions.UnauthorizedException; -import org.apache.cassandra.schema.KeyspaceMetadata; -import org.apache.cassandra.schema.MigrationManager; -import org.apache.cassandra.schema.Schema; -import org.apache.cassandra.service.ClientState; -import org.apache.cassandra.service.QueryState; -import org.apache.cassandra.transport.Event; - -/** - * A {@code DROP FUNCTION} statement parsed from a CQL query. - */ -public final class DropFunctionStatement extends SchemaAlteringStatement -{ -private FunctionName functionName; -private final boolean ifExists; -private final List argRawTypes; -private final boolean argsPresent; - -private List> argTypes; - -public DropFunctionStatement(FunctionName functionName, - List argRawTypes, - boolean argsPresent, - boolean ifExists) -{ -this.functionName = functionName; -this.argRawTypes = argRawTypes; -this.argsPresent = argsPresent; -this.ifExists = ifExists; -} - -@Override -public Prepared prepare() throws InvalidRequestException -{ -if (Schema.instance.getKeyspaceMetadata(functionName.keyspace) != null) -{ -argTypes = new ArrayList<>(argRawTypes.size()); -for (CQL3Type.Raw rawType : argRawTypes) -{ -if (rawType.isFrozen()) -throw new InvalidRequestException("The function arguments should not be frozen; remove the frozen<> modifier"); - -// UDT are not supported non frozen but we do not allow the frozen keyword for argument. So for the moment we -// freeze them here -if (!rawType.canBeNonFrozen()) -rawType.freeze(); - -argTypes.add(rawType.prepare(functionName.keyspace).getType()); -} -} - -return super.prepare(); -} - -@Override -public void prepareKeyspace(ClientState state) throws InvalidRequestException -{ -if (!functionName.hasKeyspace() && state.getRawKeyspace() != null) -functionName = new FunctionName(state.getKeyspace(), functionName.name); - -if (!functionName.hasKeyspace()) -throw new InvalidRequestException("Functions must be fully qualified with a keyspace name if a keyspace is not set for the session"); - -Schema.validateKeyspaceNotSystem(functionName.keyspace); -} - -public void checkAccess(ClientState state) throws UnauthorizedException, InvalidRequestException -{ -Function function = findFunction(); -if (function == null) -{ -if (!ifExists) -throw new InvalidRequestException(String.format("Unconfigured function %s.%s(%s)", - functionName.keyspace, - functionName.name, - Joiner.on
[04/11] cassandra git commit: 13426: work in progress
http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/src/java/org/apache/cassandra/db/marshal/AbstractCompositeType.java -- diff --git a/src/java/org/apache/cassandra/db/marshal/AbstractCompositeType.java b/src/java/org/apache/cassandra/db/marshal/AbstractCompositeType.java index 9eb5d82..9c05a77 100644 --- a/src/java/org/apache/cassandra/db/marshal/AbstractCompositeType.java +++ b/src/java/org/apache/cassandra/db/marshal/AbstractCompositeType.java @@ -30,6 +30,8 @@ import org.apache.cassandra.serializers.MarshalException; import org.apache.cassandra.transport.ProtocolVersion; import org.apache.cassandra.utils.ByteBufferUtil; +import static com.google.common.collect.Iterables.any; + /** * A class avoiding class duplication between CompositeType and * DynamicCompositeType. @@ -298,9 +300,9 @@ public abstract class AbstractCompositeType extends AbstractType } @Override -public boolean referencesUserType(String name) +public boolean referencesUserType(ByteBuffer name) { -return getComponents().stream().anyMatch(f -> f.referencesUserType(name)); +return any(getComponents(), t -> t.referencesUserType(name)); } /** http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/src/java/org/apache/cassandra/db/marshal/AbstractType.java -- diff --git a/src/java/org/apache/cassandra/db/marshal/AbstractType.java b/src/java/org/apache/cassandra/db/marshal/AbstractType.java index 99df8a2..a09d147 100644 --- a/src/java/org/apache/cassandra/db/marshal/AbstractType.java +++ b/src/java/org/apache/cassandra/db/marshal/AbstractType.java @@ -447,11 +447,19 @@ public abstract class AbstractType implements Comparator, Assignm ByteBufferUtil.skipWithVIntLength(in); } -public boolean referencesUserType(String userTypeName) +public boolean referencesUserType(ByteBuffer name) { return false; } +/** + * Returns an instance of this type with all referenced user types replaced with the new instance. + */ +public AbstractType withUpdatedUserType(UserType udt) +{ +return this; +} + public boolean referencesDuration() { return false; http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/src/java/org/apache/cassandra/db/marshal/CompositeType.java -- diff --git a/src/java/org/apache/cassandra/db/marshal/CompositeType.java b/src/java/org/apache/cassandra/db/marshal/CompositeType.java index 12e7fc3..8871eff 100644 --- a/src/java/org/apache/cassandra/db/marshal/CompositeType.java +++ b/src/java/org/apache/cassandra/db/marshal/CompositeType.java @@ -32,6 +32,8 @@ import org.apache.cassandra.exceptions.SyntaxException; import org.apache.cassandra.serializers.MarshalException; import org.apache.cassandra.utils.ByteBufferUtil; +import static com.google.common.collect.Iterables.transform; + /* * The encoding of a CompositeType column name should be: *... @@ -102,18 +104,7 @@ public class CompositeType extends AbstractCompositeType public static CompositeType getInstance(List> types) { assert types != null && !types.isEmpty(); - -CompositeType ct = instances.get(types); -if (ct == null) -{ -ct = new CompositeType(types); -CompositeType previous = instances.putIfAbsent(types, ct); -if (previous != null) -{ -ct = previous; -} -} -return ct; +return instances.computeIfAbsent(types, CompositeType::new); } protected CompositeType(List> types) @@ -287,6 +278,17 @@ public class CompositeType extends AbstractCompositeType return true; } +@Override +public CompositeType withUpdatedUserType(UserType udt) +{ +if (!referencesUserType(udt.name)) +return this; + +instances.remove(types); + +return getInstance(transform(types, t -> t.withUpdatedUserType(udt))); +} + private static class StaticParsedComparator implements ParsedComparator { final AbstractType type; http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/src/java/org/apache/cassandra/db/marshal/DynamicCompositeType.java -- diff --git a/src/java/org/apache/cassandra/db/marshal/DynamicCompositeType.java b/src/java/org/apache/cassandra/db/marshal/DynamicCompositeType.java index cade725..5b02a05 100644 --- a/src/java/org/apache/cassandra/db/marshal/DynamicCompositeType.java +++ b/src/java/org/apache/cassandra/db/marshal/DynamicCompositeType.java @@ -17,21 +17,20 @@ */ package org.apache.cassandra.db.marshal; -import java.nio.charset.CharacterCodingException; import java.nio.ByteBuffe
[05/11] cassandra git commit: 13426: work in progress
http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/src/java/org/apache/cassandra/cql3/statements/schema/CreateTableStatement.java -- diff --git a/src/java/org/apache/cassandra/cql3/statements/schema/CreateTableStatement.java b/src/java/org/apache/cassandra/cql3/statements/schema/CreateTableStatement.java new file mode 100644 index 000..d5d2c97 --- /dev/null +++ b/src/java/org/apache/cassandra/cql3/statements/schema/CreateTableStatement.java @@ -0,0 +1,417 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +package org.apache.cassandra.cql3.statements.schema; + +import java.util.*; +import java.util.stream.Collectors; + +import com.google.common.collect.ImmutableSet; + +import org.apache.cassandra.auth.DataResource; +import org.apache.cassandra.auth.IResource; +import org.apache.cassandra.auth.Permission; +import org.apache.cassandra.cql3.*; +import org.apache.cassandra.cql3.statements.TableAttributes; +import org.apache.cassandra.db.CompactTables; +import org.apache.cassandra.db.marshal.*; +import org.apache.cassandra.exceptions.AlreadyExistsException; +import org.apache.cassandra.schema.*; +import org.apache.cassandra.schema.Keyspaces.KeyspacesDiff; +import org.apache.cassandra.service.ClientState; +import org.apache.cassandra.transport.Event.SchemaChange; +import org.apache.cassandra.transport.Event.SchemaChange.Change; +import org.apache.cassandra.transport.Event.SchemaChange.Target; + +import static java.util.Comparator.comparing; + +import static com.google.common.collect.Iterables.concat; + +public final class CreateTableStatement extends AlterSchemaStatement +{ +private final String tableName; + +private final Map rawColumns; +private final Set staticColumns; +private final List partitionKeyColumns; +private final List clusteringColumns; + +private final boolean useCompactStorage; +private final LinkedHashMap clusteringOrder; +private final TableAttributes attrs; + +private final boolean ifNotExists; + +public CreateTableStatement(String keyspaceName, +String tableName, + +Map rawColumns, +Set staticColumns, +List partitionKeyColumns, +List clusteringColumns, + +boolean useCompactStorage, +LinkedHashMap clusteringOrder, +TableAttributes attrs, + +boolean ifNotExists) +{ +super(keyspaceName); +this.tableName = tableName; + +this.rawColumns = rawColumns; +this.staticColumns = staticColumns; +this.partitionKeyColumns = partitionKeyColumns; +this.clusteringColumns = clusteringColumns; + +this.useCompactStorage = useCompactStorage; +this.clusteringOrder = clusteringOrder; +this.attrs = attrs; + +this.ifNotExists = ifNotExists; +} + +public Keyspaces apply(Keyspaces schema) +{ +KeyspaceMetadata keyspace = schema.getNullable(keyspaceName); +if (null == keyspace) +throw ire("Keyspace '%s' doesn't exist", keyspaceName); + +if (keyspace.hasTable(tableName)) +{ +if (ifNotExists) +return schema; + +throw new AlreadyExistsException(keyspaceName, tableName); +} + +TableMetadata table = builder(keyspace.types).build(); +table.validate(); + +return schema.withAddedOrUpdated(keyspace.withSwapped(keyspace.tables.with(table))); +} + +SchemaChange schemaChangeEvent(KeyspacesDiff diff) +{ +return new SchemaChange(Change.CREATED, Target.TABLE, keyspaceName, tableName); +} + +public void authorize(ClientState client) +{ +client.ensureKeyspacePermission(keyspaceName, Permission.CREATE); +} + +@Override +Set createdResources(KeyspacesDiff diff) +{ +return ImmutableSet.of(DataResource.table(keyspaceName, tableName)); +} + +public TableMetadata.Builder builder(Types types) +
[10/11] cassandra git commit: 13426: work in progress
13426: work in progress Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/aaddbd49 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/aaddbd49 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/aaddbd49 Branch: refs/heads/13426 Commit: aaddbd49ae7c88e8cfea5f51809f87e9e1ea729a Parents: 7b149ce Author: Aleksey Yeschenko Authored: Thu Nov 10 01:17:36 2016 + Committer: Aleksey Yeschenko Committed: Wed May 31 14:42:08 2017 +0100 -- src/antlr/Cql.g | 18 +- src/antlr/Parser.g | 215 +- .../org/apache/cassandra/auth/AuthKeyspace.java | 2 +- .../cassandra/auth/CassandraAuthorizer.java | 26 +- .../cassandra/auth/CassandraRoleManager.java| 3 +- .../apache/cassandra/auth/FunctionResource.java | 5 + .../cassandra/auth/PasswordAuthenticator.java | 2 +- .../cassandra/auth/jmx/AuthorizationProxy.java | 2 +- src/java/org/apache/cassandra/cql3/CFName.java | 39 -- .../org/apache/cassandra/cql3/CQL3Type.java | 97 ++--- .../org/apache/cassandra/cql3/CQLStatement.java | 59 ++- .../CustomPayloadMirroringQueryHandler.java | 3 +- .../org/apache/cassandra/cql3/IndexName.java| 47 --- .../cassandra/cql3/KeyspaceElementName.java | 74 .../apache/cassandra/cql3/QualifiedName.java| 97 + .../org/apache/cassandra/cql3/QueryHandler.java | 3 +- .../apache/cassandra/cql3/QueryProcessor.java | 154 --- .../cassandra/cql3/SingleColumnRelation.java| 2 +- .../cassandra/cql3/VariableSpecifications.java | 16 +- .../org/apache/cassandra/cql3/WhereClause.java | 46 +- .../cql3/functions/AbstractFunction.java| 7 + .../cassandra/cql3/functions/Function.java | 10 + .../cassandra/cql3/functions/UDAggregate.java | 77 ++-- .../cassandra/cql3/functions/UDFunction.java| 42 ++ .../restrictions/CustomIndexExpression.java | 12 +- .../cql3/restrictions/IndexRestrictions.java| 18 +- .../restrictions/StatementRestrictions.java | 35 +- .../cql3/statements/AlterKeyspaceStatement.java | 112 - .../cql3/statements/AlterRoleStatement.java | 4 +- .../cql3/statements/AlterTableStatement.java| 20 +- .../cql3/statements/AlterTypeStatement.java | 22 +- .../cql3/statements/AlterViewStatement.java | 96 - .../statements/AuthenticationStatement.java | 18 +- .../cql3/statements/AuthorizationStatement.java | 17 +- .../cql3/statements/BatchStatement.java | 79 ++-- .../cassandra/cql3/statements/CFStatement.java | 66 --- .../statements/CreateAggregateStatement.java| 25 +- .../statements/CreateFunctionStatement.java | 22 +- .../cql3/statements/CreateIndexStatement.java | 258 .../statements/CreateKeyspaceStatement.java | 137 -- .../cql3/statements/CreateRoleStatement.java| 4 +- .../cql3/statements/CreateTableStatement.java | 414 -- .../cql3/statements/CreateTriggerStatement.java | 98 - .../cql3/statements/CreateTypeStatement.java| 135 -- .../cql3/statements/CreateViewStatement.java| 338 --- .../cql3/statements/DeleteStatement.java| 14 +- .../cql3/statements/DropAggregateStatement.java | 152 --- .../cql3/statements/DropFunctionStatement.java | 189 - .../cql3/statements/DropIndexStatement.java | 116 -- .../cql3/statements/DropKeyspaceStatement.java | 73 .../cql3/statements/DropRoleStatement.java | 4 +- .../cql3/statements/DropTableStatement.java | 104 - .../cql3/statements/DropTriggerStatement.java | 85 .../cql3/statements/DropTypeStatement.java | 123 -- .../cql3/statements/DropViewStatement.java | 69 --- .../cql3/statements/IndexAttributes.java| 76 .../cql3/statements/IndexPropDefs.java | 76 .../statements/ListPermissionsStatement.java| 2 +- .../cql3/statements/ListRolesStatement.java | 2 +- .../cql3/statements/ModificationStatement.java | 81 ++-- .../cql3/statements/ParsedStatement.java| 86 .../PermissionsManagementStatement.java | 10 +- .../cql3/statements/QualifiedStatement.java | 67 +++ .../statements/RoleManagementStatement.java | 2 +- .../statements/SchemaAlteringStatement.java | 21 +- .../cql3/statements/SelectStatement.java| 84 ++-- .../cql3/statements/TableAttributes.java| 8 +- .../cql3/statements/TruncateStatement.java | 27 +- .../cql3/statements/UpdateStatement.java| 41 +- .../cassandra/cql3/statements/UseStatement.java | 15 +- .../schema/AlterKeyspaceStatement.java | 104 + .../statements/schema/AlterSchemaStatement.java | 161 +++ .../statements/schema/AlterTableStatement.java | 341 +++ .../statements/sche
[06/11] cassandra git commit: 13426: work in progress
http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/src/java/org/apache/cassandra/cql3/statements/UpdateStatement.java -- diff --git a/src/java/org/apache/cassandra/cql3/statements/UpdateStatement.java b/src/java/org/apache/cassandra/cql3/statements/UpdateStatement.java index 7a2a1ba..deaf375 100644 --- a/src/java/org/apache/cassandra/cql3/statements/UpdateStatement.java +++ b/src/java/org/apache/cassandra/cql3/statements/UpdateStatement.java @@ -47,19 +47,14 @@ public class UpdateStatement extends ModificationStatement private static final Constants.Value EMPTY = new Constants.Value(ByteBufferUtil.EMPTY_BYTE_BUFFER); private UpdateStatement(StatementType type, -int boundTerms, +VariableSpecifications bindVariables, TableMetadata metadata, Operations operations, StatementRestrictions restrictions, Conditions conditions, Attributes attrs) { -super(type, boundTerms, metadata, operations, restrictions, conditions, attrs); -} - -public boolean requireFullClusteringKey() -{ -return true; +super(type, bindVariables, metadata, operations, restrictions, conditions, attrs); } @Override @@ -124,7 +119,7 @@ public class UpdateStatement extends ModificationStatement * @param columnValues list of column values (corresponds to names) * @param ifNotExists true if an IF NOT EXISTS condition was specified, false otherwise */ -public ParsedInsert(CFName name, +public ParsedInsert(QualifiedName name, Attributes.Raw attrs, List columnNames, List columnValues, @@ -137,7 +132,7 @@ public class UpdateStatement extends ModificationStatement @Override protected ModificationStatement prepareInternal(TableMetadata metadata, -VariableSpecifications boundNames, +VariableSpecifications bindVariables, Conditions conditions, Attributes attrs) { @@ -170,7 +165,7 @@ public class UpdateStatement extends ModificationStatement else { Operation operation = new Operation.SetValue(value).prepare(metadata, def); -operation.collectMarkerSpecification(boundNames); +operation.collectMarkerSpecification(bindVariables); operations.add(operation); } } @@ -180,13 +175,13 @@ public class UpdateStatement extends ModificationStatement StatementRestrictions restrictions = new StatementRestrictions(type, metadata, whereClause.build(), - boundNames, + bindVariables, applyOnlyToStaticColumns, false, false); return new UpdateStatement(type, - boundNames.size(), + bindVariables, metadata, operations, restrictions, @@ -203,7 +198,7 @@ public class UpdateStatement extends ModificationStatement private final Json.Raw jsonValue; private final boolean defaultUnset; -public ParsedInsertJson(CFName name, Attributes.Raw attrs, Json.Raw jsonValue, boolean defaultUnset, boolean ifNotExists) +public ParsedInsertJson(QualifiedName name, Attributes.Raw attrs, Json.Raw jsonValue, boolean defaultUnset, boolean ifNotExists) { super(name, StatementType.INSERT, attrs, null, ifNotExists, false); this.jsonValue = jsonValue; @@ -212,14 +207,14 @@ public class UpdateStatement extends ModificationStatement @Override protected ModificationStatement prepareInternal(TableMetadata metadata, -VariableSpecifications boundNames, +VariableSpecifications bindVariables,
[01/11] cassandra git commit: 13426: work in progress
Repository: cassandra Updated Branches: refs/heads/13426 [created] b30c6da2d http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/test/unit/org/apache/cassandra/cql3/validation/operations/InsertUpdateIfConditionTest.java -- diff --git a/test/unit/org/apache/cassandra/cql3/validation/operations/InsertUpdateIfConditionTest.java b/test/unit/org/apache/cassandra/cql3/validation/operations/InsertUpdateIfConditionTest.java index da5c3bd..bfd8a15 100644 --- a/test/unit/org/apache/cassandra/cql3/validation/operations/InsertUpdateIfConditionTest.java +++ b/test/unit/org/apache/cassandra/cql3/validation/operations/InsertUpdateIfConditionTest.java @@ -1414,10 +1414,8 @@ public class InsertUpdateIfConditionTest extends CQLTester { String tableName = createTable("CREATE TABLE %s (id text PRIMARY KEY, value1 blob, value2 blob)with comment = 'foo'"); -execute("use " + KEYSPACE); - // try dropping when doesn't exist -schemaChange("DROP INDEX IF EXISTS myindex"); +schemaChange(format("DROP INDEX IF EXISTS %s.myindex", KEYSPACE)); // create and confirm createIndex("CREATE INDEX IF NOT EXISTS myindex ON %s (value1)"); @@ -1428,7 +1426,7 @@ public class InsertUpdateIfConditionTest extends CQLTester execute("CREATE INDEX IF NOT EXISTS myindex ON %s (value1)"); // drop and confirm -execute("DROP INDEX IF EXISTS myindex"); +execute(format("DROP INDEX IF EXISTS %s.myindex", KEYSPACE)); Object[][] rows = getRows(execute("select index_name from system.\"IndexInfo\" where table_name = ?", tableName)); assertEquals(0, rows.length); http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/test/unit/org/apache/cassandra/cql3/validation/operations/SelectSingleColumnRelationTest.java -- diff --git a/test/unit/org/apache/cassandra/cql3/validation/operations/SelectSingleColumnRelationTest.java b/test/unit/org/apache/cassandra/cql3/validation/operations/SelectSingleColumnRelationTest.java index 7e5afda..baedd63 100644 --- a/test/unit/org/apache/cassandra/cql3/validation/operations/SelectSingleColumnRelationTest.java +++ b/test/unit/org/apache/cassandra/cql3/validation/operations/SelectSingleColumnRelationTest.java @@ -223,7 +223,7 @@ public class SelectSingleColumnRelationTest extends CQLTester @Test public void testClusteringColumnRelationsWithClusteringOrder() throws Throwable { -createTable("CREATE TABLE %s (a text, b int, c int, d int, primary key(a, b, c)) WITH CLUSTERING ORDER BY (b DESC);"); +createTable("CREATE TABLE %s (a text, b int, c int, d int, primary key(a, b, c)) WITH CLUSTERING ORDER BY (b DESC, c ASC);"); execute("insert into %s (a, b, c, d) values (?, ?, ?, ?)", "first", 1, 5, 1); execute("insert into %s (a, b, c, d) values (?, ?, ?, ?)", "first", 2, 6, 2); execute("insert into %s (a, b, c, d) values (?, ?, ?, ?)", "first", 3, 7, 3); http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/test/unit/org/apache/cassandra/cql3/validation/operations/SelectTest.java -- diff --git a/test/unit/org/apache/cassandra/cql3/validation/operations/SelectTest.java b/test/unit/org/apache/cassandra/cql3/validation/operations/SelectTest.java index c0a8a9c..327a0a7 100644 --- a/test/unit/org/apache/cassandra/cql3/validation/operations/SelectTest.java +++ b/test/unit/org/apache/cassandra/cql3/validation/operations/SelectTest.java @@ -2608,7 +2608,7 @@ public class SelectTest extends CQLTester }); // test clutering order -createTable("CREATE TABLE %s (a int, b int, c int, d int, e int, PRIMARY KEY ((a, b), c, d)) WITH CLUSTERING ORDER BY (c DESC)"); +createTable("CREATE TABLE %s (a int, b int, c int, d int, e int, PRIMARY KEY ((a, b), c, d)) WITH CLUSTERING ORDER BY (c DESC, d ASC)"); execute("INSERT INTO %s (a,b,c,d,e) VALUES (11, 11, 13, 14, 15)"); execute("INSERT INTO %s (a,b,c,d,e) VALUES (11, 11, 14, 17, 18)"); @@ -4098,7 +4098,7 @@ public class SelectTest extends CQLTester // compound, first column DESC order createTable("CREATE TABLE %s (a text, b int, c int, PRIMARY KEY (a, b, c)) WITH" + compactOption + -" CLUSTERING ORDER BY (b DESC)" +" CLUSTERING ORDER BY (b DESC, c ASC)" ); execute("INSERT INTO %s (a, b, c) VALUES ('a', 2, 4)"); http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/test/unit/org/apache/cassandra/db/RowIndexEntryTest.java -- diff --git a/test/unit/org/apache/cassandra/db/RowIndexEntryTest.java b/test/unit/org/apache/cassandr
[09/11] cassandra git commit: 13426: work in progress
http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/src/java/org/apache/cassandra/cql3/QueryProcessor.java -- diff --git a/src/java/org/apache/cassandra/cql3/QueryProcessor.java b/src/java/org/apache/cassandra/cql3/QueryProcessor.java index cca93ff..6347f9c 100644 --- a/src/java/org/apache/cassandra/cql3/QueryProcessor.java +++ b/src/java/org/apache/cassandra/cql3/QueryProcessor.java @@ -69,11 +69,11 @@ public class QueryProcessor implements QueryHandler private static final Logger logger = LoggerFactory.getLogger(QueryProcessor.class); -private static final Cache preparedStatements; +private static final Cache preparedStatements; // A map for prepared statements used internally (which we don't want to mix with user statement, in particular we don't // bother with expiration on those. -private static final ConcurrentMap internalStatements = new ConcurrentHashMap<>(); +private static final ConcurrentMap internalStatements = new ConcurrentHashMap<>(); // Direct calls to processStatement do not increment the preparedStatementsExecuted/regularStatementsExecuted // counters. Callers of processStatement are responsible for correctly notifying metrics @@ -117,7 +117,7 @@ public class QueryProcessor implements QueryHandler } // Work around initialization dependency -private static enum InternalStateInstance +private enum InternalStateInstance { INSTANCE; @@ -125,9 +125,7 @@ public class QueryProcessor implements QueryHandler InternalStateInstance() { -ClientState state = ClientState.forInternalCalls(); -state.setKeyspace(SchemaConstants.SYSTEM_KEYSPACE_NAME); -this.queryState = new QueryState(state); +queryState = new QueryState(ClientState.forInternalCalls(SchemaConstants.SYSTEM_KEYSPACE_NAME)); } } @@ -167,7 +165,7 @@ public class QueryProcessor implements QueryHandler Schema.instance.registerListener(new StatementInvalidatingListener()); } -public ParsedStatement.Prepared getPrepared(MD5Digest id) +public Prepared getPrepared(MD5Digest id) { return preparedStatements.getIfPresent(id); } @@ -194,7 +192,7 @@ public class QueryProcessor implements QueryHandler { logger.trace("Process {} @CL.{}", statement, options.getConsistency()); ClientState clientState = queryState.getClientState(); -statement.checkAccess(clientState); +statement.authorize(clientState); statement.validate(clientState); ResultMessage result = statement.execute(queryState, options, queryStartNanoTime); @@ -219,10 +217,9 @@ public class QueryProcessor implements QueryHandler public ResultMessage process(String queryString, QueryState queryState, QueryOptions options, long queryStartNanoTime) throws RequestExecutionException, RequestValidationException { -ParsedStatement.Prepared p = getStatement(queryString, queryState.getClientState().cloneWithKeyspaceIfSet(options.getKeyspace())); -options.prepare(p.boundNames); -CQLStatement prepared = p.statement; -if (prepared.getBoundTerms() != options.getValues().size()) +CQLStatement prepared = getStatement(queryString, queryState.getClientState().cloneWithKeyspaceIfSet(options.getKeyspace())); +options.prepare(prepared.getBindVariables()); +if (prepared.getBindVariables().size() != options.getValues().size()) throw new InvalidRequestException("Invalid amount of bind variables"); if (!queryState.getClientState().isInternal) @@ -231,7 +228,7 @@ public class QueryProcessor implements QueryHandler return processStatement(prepared, queryState, options, queryStartNanoTime); } -public static ParsedStatement.Prepared parseStatement(String queryStr, ClientState clientState) throws RequestValidationException +public static CQLStatement parseStatement(String queryStr, ClientState clientState) throws RequestValidationException { return getStatement(queryStr, clientState); } @@ -250,43 +247,45 @@ public class QueryProcessor implements QueryHandler return null; } -private static QueryOptions makeInternalOptions(ParsedStatement.Prepared prepared, Object[] values) +private static QueryOptions makeInternalOptions(CQLStatement prepared, Object[] values) { return makeInternalOptions(prepared, values, ConsistencyLevel.ONE); } -private static QueryOptions makeInternalOptions(ParsedStatement.Prepared prepared, Object[] values, ConsistencyLevel cl) +private static QueryOptions makeInternalOptions(CQLStatement prepared, Object[] values, ConsistencyLevel cl) { -if (prepared.boundNames.size() != values.length) -throw new IllegalArgumentException(Stri
[cassandra] Git Push Summary
Repository: cassandra Updated Branches: refs/heads/13426 [deleted] b30c6da2d - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[08/11] cassandra git commit: 13426: work in progress
http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/src/java/org/apache/cassandra/cql3/statements/CreateAggregateStatement.java -- diff --git a/src/java/org/apache/cassandra/cql3/statements/CreateAggregateStatement.java b/src/java/org/apache/cassandra/cql3/statements/CreateAggregateStatement.java index ade2752..878195f 100644 --- a/src/java/org/apache/cassandra/cql3/statements/CreateAggregateStatement.java +++ b/src/java/org/apache/cassandra/cql3/statements/CreateAggregateStatement.java @@ -77,7 +77,7 @@ public final class CreateAggregateStatement extends SchemaAlteringStatement this.ifNotExists = ifNotExists; } -public Prepared prepare() +public CreateAggregateStatement prepare(ClientState state) { argTypes = new ArrayList<>(argRawTypes.size()); for (CQL3Type.Raw rawType : argRawTypes) @@ -135,7 +135,7 @@ public final class CreateAggregateStatement extends SchemaAlteringStatement throw new InvalidRequestException("INITCOND must not be empty for all types except TEXT, ASCII, BLOB"); } -return super.prepare(); +return this; } private AbstractType prepareType(String typeName, CQL3Type.Raw rawType) @@ -143,16 +143,11 @@ public final class CreateAggregateStatement extends SchemaAlteringStatement if (rawType.isFrozen()) throw new InvalidRequestException(String.format("The function %s should not be frozen; remove the frozen<> modifier", typeName)); -// UDT are not supported non frozen but we do not allow the frozen keyword for argument. So for the moment we -// freeze them here -if (!rawType.canBeNonFrozen()) -rawType.freeze(); - AbstractType type = rawType.prepare(functionName.keyspace).getType(); return type; } -public void prepareKeyspace(ClientState state) throws InvalidRequestException +public void setKeyspace(ClientState state) throws InvalidRequestException { if (!functionName.hasKeyspace() && state.getRawKeyspace() != null) functionName = new FunctionName(state.getKeyspace(), functionName.name); @@ -183,19 +178,19 @@ public final class CreateAggregateStatement extends SchemaAlteringStatement } } -public void checkAccess(ClientState state) throws UnauthorizedException, InvalidRequestException +public void authorize(ClientState state) throws UnauthorizedException, InvalidRequestException { if (Schema.instance.findFunction(functionName, argTypes).isPresent() && orReplace) -state.ensureHasPermission(Permission.ALTER, FunctionResource.function(functionName.keyspace, - functionName.name, - argTypes)); +state.ensurePermission(Permission.ALTER, FunctionResource.function(functionName.keyspace, + functionName.name, + argTypes)); else -state.ensureHasPermission(Permission.CREATE, FunctionResource.keyspace(functionName.keyspace)); +state.ensurePermission(Permission.CREATE, FunctionResource.keyspace(functionName.keyspace)); -state.ensureHasPermission(Permission.EXECUTE, stateFunction); +state.ensurePermission(Permission.EXECUTE, stateFunction); if (finalFunction != null) -state.ensureHasPermission(Permission.EXECUTE, finalFunction); +state.ensurePermission(Permission.EXECUTE, finalFunction); } public void validate(ClientState state) throws InvalidRequestException http://git-wip-us.apache.org/repos/asf/cassandra/blob/aaddbd49/src/java/org/apache/cassandra/cql3/statements/CreateFunctionStatement.java -- diff --git a/src/java/org/apache/cassandra/cql3/statements/CreateFunctionStatement.java b/src/java/org/apache/cassandra/cql3/statements/CreateFunctionStatement.java index 2e1f78c..378ba9d 100644 --- a/src/java/org/apache/cassandra/cql3/statements/CreateFunctionStatement.java +++ b/src/java/org/apache/cassandra/cql3/statements/CreateFunctionStatement.java @@ -75,7 +75,7 @@ public final class CreateFunctionStatement extends SchemaAlteringStatement this.ifNotExists = ifNotExists; } -public Prepared prepare() throws InvalidRequestException +public CreateFunctionStatement prepare(ClientState state) { if (new HashSet<>(argNames).size() != argNames.size()) throw new InvalidRequestException(String.format("duplicate argument names for given function %s with argument names %s", @@ -86,10 +86,11 @@ public final class Cr
[jira] [Commented] (CASSANDRA-13544) Exceptions encountered for concurrent range deletes with mixed cluster keys
[ https://issues.apache.org/jira/browse/CASSANDRA-13544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031597#comment-16031597 ] Eric Evans commented on CASSANDRA-13544: {quote} Would you have an easy to try the tip of 3.11? I would need to look more closely to say more but we did fixed genuine range tombstone bugs recently-ish, so checking it's not fixed would be really nice. {quote} OK, I've tested 3.11 (5a860a7) and am not seeing any exceptions. > Exceptions encountered for concurrent range deletes with mixed cluster keys > --- > > Key: CASSANDRA-13544 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13544 > Project: Cassandra > Issue Type: Bug > Components: Core, Local Write-Read Paths > Environment: Cassandra 3.7, Debian Linux >Reporter: Eric Evans > > Using a schema that looks something like... > {code:sql} > CREATE TABLE data ( > key text, > rev int, > tid timeuuid, > value blob, > PRIMARY KEY (key, rev, tid) > ) WITH CLUSTERING ORDER BY (rev DESC, tid DESC) > {code} > ...we are performing range deletes using inequality operators on both {{rev}} > and {{tid}} ({{WHERE key = ? AND rev < ?}} and {{WHERE key = ? AND rev = ? > AND tid < ?}}). These range deletes are interleaved with normal writes > probabilistically, and (apparently) when two such range deletes occur > concurrently, the following exceptions result. > {noformat} > ERROR [SharedPool-Worker-18] 2017-05-19 17:30:22,426 Message.java:611 - > Unexpected exception during request; channel = [id: 0x793a853b, > L:/10.64.0.36:9042 - R:/10.64.32.112:550 > 48] > java.lang.AssertionError: null > at > org.apache.cassandra.db.ClusteringBoundOrBoundary.(ClusteringBoundOrBoundary.java:31) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.db.ClusteringBoundary.(ClusteringBoundary.java:15) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.db.ClusteringBoundOrBoundary.inclusiveCloseExclusiveOpen(ClusteringBoundOrBoundary.java:78) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.db.rows.RangeTombstoneBoundaryMarker.inclusiveCloseExclusiveOpen(RangeTombstoneBoundaryMarker.java:54) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.db.rows.RangeTombstoneMarker$Merger.merge(RangeTombstoneMarker.java:139) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator$MergeReducer.getReduced(UnfilteredRowIterators.java:521) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator$MergeReducer.getReduced(UnfilteredRowIterators.java:478) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.utils.MergeIterator$ManyToOne.consume(MergeIterator.java:217) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.utils.MergeIterator$ManyToOne.computeNext(MergeIterator.java:156) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:460) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.db.rows.UnfilteredRowIterators$UnfilteredRowMergeIterator.computeNext(UnfilteredRowIterators.java:320) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.db.transform.BaseRows.hasNext(BaseRows.java:113) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.db.transform.FilteredRows.isEmpty(FilteredRows.java:30) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.db.transform.Filter.closeIfEmpty(Filter.java:53) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.db.transform.Filter.applyToPartition(Filter.java:23) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.db.transform.Filter.applyToPartition(Filter.java:6) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.db.transform.BasePartitions.hasNext(BasePartitions.java:76) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.cql3.statements.SelectStatement.process(SelectStatement.java:735) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apache.cassandra.cql3.statements.SelectStatement.processResults(SelectStatement.java:410) > ~[apache-cassandra-3.7.3.jar:3.7.3] > at > org.apa