[jira] [Comment Edited] (CASSANDRA-10190) Python 3 support for cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-10190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928785#comment-16928785
]
Patrick Bannister edited comment on CASSANDRA-10190 at 9/13/19 1:23 AM:
I'm experimenting with the {{test_cqlsh_completion}} unit tests to try to make
them faster and more like unit tests. Right now they work more like dtests (as
do most of the cqlshlib unit tests).
This is not worth holding up the ticket to do, but I'll push the results up to
the branch if I can finish something before we're ready to proceed.
was (Author: ptbannister):
I'm experimenting with changing the cqlshlib unit tests in
{{test_cqlsh_completion}}. These are the slowest part of the cqlshlib unit test
suite. They currently work by running cqlsh in a subprocess to connect to a ccm
cluster, sending partial commands to the cqlsh, and reading the completions
suggested by the cqlsh. This is slow, because we have to use a timeout to wait
for the cqlsh to accept our input and output its recommended completions.
In general, these don't really look like unit tests, they look more like
dtests. One approach would be to remove this from the unit tests and make it
part of the dtests. But I'd prefer to convert them to something more like a
unit test. We can make them run faster by using cqlshlib internals directly,
instead of running cqlsh in a subprocess. We can call {{cql_complete}} on each
partial command and assert that the completions are what we expect.
Once I've rewritten the {{test_cqlsh_completion.py}} tests like this, it'll be
up on the branch for consideration.
> Python 3 support for cqlsh
> --
>
> Key: CASSANDRA-10190
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10190
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Tools
>Reporter: Andrew Pennebaker
>Assignee: Patrick Bannister
>Priority: Normal
> Labels: cqlsh
> Fix For: 4.0, 4.0-alpha
>
> Attachments: coverage_notes.txt
>
>
> Users who operate in a Python 3 environment may have trouble launching cqlsh.
> Could we please update cqlsh's syntax to run in Python 3?
> As a workaround, users can setup pyenv, and cd to a directory with a
> .python-version containing "2.7". But it would be nice if cqlsh supported
> modern Python versions out of the box.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15301) DDL operation during backup process after made snaphot ,restore will lost data
[ https://issues.apache.org/jira/browse/CASSANDRA-15301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928807#comment-16928807 ] Romain Hardouin commented on CASSANDRA-15301: - Maybe adding incremental backups to daily snapshots could fit your needs. You can build something similar to _tablesnap_ that uploads somewhere each sstable under /backups directory and then process them to do whatever you need. See: * [https://docs.datastax.com/en/archived/cassandra/3.0/cassandra/operations/opsBackupIncremental.html] * [https://github.com/apache/cassandra/blob/cassandra-3.11/conf/cassandra.yaml#L775] * [http://cassandra.apache.org/doc/latest/tools/nodetool/enablebackup.html] * tablesnap: [https://github.com/JeremyGrosser/tablesnap] > DDL operation during backup process after made snaphot ,restore will lost > data > --- > > Key: CASSANDRA-15301 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15301 > Project: Cassandra > Issue Type: Bug >Reporter: maxwellguo >Priority: Normal > > As the document described > https://docs.datastax.com/en/archived/cassandra/3.0/cassandra/operations/opsBackupRestore.html > , the setp to do bakcup and restore, we make snapshot and do table file > export , but during thie process new keyspace / table was created ,The table > file can be export to new cluster ,but when restore snapshot and files, new > added table want't be loaded . so the new added table's data can not be get . -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-10190) Python 3 support for cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-10190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928785#comment-16928785
]
Patrick Bannister commented on CASSANDRA-10190:
---
I'm experimenting with changing the cqlshlib unit tests in
{{test_cqlsh_completion}}. These are the slowest part of the cqlshlib unit test
suite. They currently work by running cqlsh in a subprocess to connect to a ccm
cluster, sending partial commands to the cqlsh, and reading the completions
suggested by the cqlsh. This is slow, because we have to use a timeout to wait
for the cqlsh to accept our input and output its recommended completions.
In general, these don't really look like unit tests, they look more like
dtests. One approach would be to remove this from the unit tests and make it
part of the dtests. But I'd prefer to convert them to something more like a
unit test. We can make them run faster by using cqlshlib internals directly,
instead of running cqlsh in a subprocess. We can call {{cql_complete}} on each
partial command and assert that the completions are what we expect.
Once I've rewritten the {{test_cqlsh_completion.py}} tests like this, it'll be
up on the branch for consideration.
> Python 3 support for cqlsh
> --
>
> Key: CASSANDRA-10190
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10190
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Tools
>Reporter: Andrew Pennebaker
>Assignee: Patrick Bannister
>Priority: Normal
> Labels: cqlsh
> Fix For: 4.0, 4.0-alpha
>
> Attachments: coverage_notes.txt
>
>
> Users who operate in a Python 3 environment may have trouble launching cqlsh.
> Could we please update cqlsh's syntax to run in Python 3?
> As a workaround, users can setup pyenv, and cd to a directory with a
> .python-version containing "2.7". But it would be nice if cqlsh supported
> modern Python versions out of the box.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-14288) Document compaction-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-14288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928467#comment-16928467 ] Tanaka edited comment on CASSANDRA-14288 at 9/12/19 11:36 AM: -- [~hkroger] Documentation for Cassandra-stress tool is live on the website: [http://cassandra.apache.org/doc/latest/tools/cassandra_stress.html] (I did not update documentation, just verifying ticket) This ticket is ready to be resolved. was (Author: tanakarm): [~hkroger] Documentation for Cassandra-stress tool is live on the website: [http://cassandra.apache.org/doc/latest/tools/cassandra_stress.html] This ticket is ready to be resolved. > Document compaction-stress > -- > > Key: CASSANDRA-14288 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14288 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/Documentation and Website >Reporter: Hannu Kröger >Assignee: Tanaka >Priority: Normal > > Cassandra tools section should also document compaction-stress command: > [http://cassandra.apache.org/doc/latest/tools/index.html] > Currently it's not documented there. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14288) Document compaction-stress
[ https://issues.apache.org/jira/browse/CASSANDRA-14288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928467#comment-16928467 ] Tanaka commented on CASSANDRA-14288: [~hkroger] Documentation for Cassandra-stress tool is live on the website: [http://cassandra.apache.org/doc/latest/tools/cassandra_stress.html] This ticket is ready to be resolved. > Document compaction-stress > -- > > Key: CASSANDRA-14288 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14288 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/Documentation and Website >Reporter: Hannu Kröger >Assignee: Tanaka >Priority: Normal > > Cassandra tools section should also document compaction-stress command: > [http://cassandra.apache.org/doc/latest/tools/index.html] > Currently it's not documented there. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14012) Document gossip protocol
[ https://issues.apache.org/jira/browse/CASSANDRA-14012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928448#comment-16928448 ] Tanaka commented on CASSANDRA-14012: [~Wulf4096] This ticket has not been updated in almost 2 years. I found the following page about Cassandra's Gossip Protocol: [https://cwiki.apache.org/confluence/display/CASSANDRA2/ArchitectureGossip] Does the information there resolve your issue? > Document gossip protocol > > > Key: CASSANDRA-14012 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14012 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/Documentation and Website >Reporter: Jörn Heissler >Assignee: Tanaka >Priority: Low > Labels: Documentation > > I had an issue today with two nodes communicating with each other; there's a > flaw in my configuration (wrong broadcast address). > I saw a little bit of traffic on port 7000, but I couldn't understand it for > lack of documentation. > With documentation I would have understood my issue very quickly (7f 00 01 01 > is a bad broadcast address!). But I didn't recognize those 4 bytes as the bc > address. > Could you please document the gossip protocol? -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15324) Unable to compute ceiling for max when histogram
[ https://issues.apache.org/jira/browse/CASSANDRA-15324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928322#comment-16928322 ] Dinesh Joshi edited comment on CASSANDRA-15324 at 9/12/19 7:49 AM: --- Your issue is likely related to your data model. Its better to discuss it on the [user mailing list|http://cassandra.apache.org/community/]. It would also be helpful to include information about your data model and any other relevant information to help debug the issue and point you in the right direction. was (Author: djoshi3): Your issue is likely related to your data model. Its better to discuss it on the [user mailing list|http://cassandra.apache.org/community/]. > Unable to compute ceiling for max when histogram > > > Key: CASSANDRA-15324 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15324 > Project: Cassandra > Issue Type: Bug > Components: Local/Compaction, Local/Compaction/STCS >Reporter: HsuML >Priority: Normal > > I have 9 cassandra nodes. When I create a keyspace that has 15 tables and the > record count of all table are about 8.2 billion. I imported data through my > java loaders, and I found out the system.log has error message. What happened > and how can I solve the error? > Exception in thread Thread[CompactionExecutor:113041,1,main] > java.lang.IllegalStateException: Unable to compute ceiling for max when > histogram overflowed > at > org.apache.cassandra.utils.EstimatedHistogram.rawMean(EstimatedHistogram.java:231) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.utils.EstimatedHistogram.mean(EstimatedHistogram.java:220) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.io.sstable.metadata.StatsMetadata.getEstimatedDroppableTombstoneRatio(StatsMetadata.java:115) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.io.sstable.format.SSTableReader.getEstimatedDroppableTombstoneRatio(SSTableReader.java:1926) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.worthDroppingTombstones(AbstractCompactionStrategy.java:424) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy.getNextBackgroundSSTables(SizeTieredCompactionStrategy.java:99) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy.getNextBackgroundTask(SizeTieredCompactionStrategy.java:183) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.getNextBackgroundTask(CompactionStrategyManager.java:153) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionCandidate.run(CompactionManager.java:260) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ~[na:1.8.0_191] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > ~[na:1.8.0_191] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > ~[na:1.8.0_191] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [na:1.8.0_191] > at > org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81) > [apache-cassandra-3.11.4.jar:3.11.4] > at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_191] -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15324) Unable to compute ceiling for max when histogram
[ https://issues.apache.org/jira/browse/CASSANDRA-15324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-15324: - Resolution: Invalid Status: Resolved (was: Awaiting Feedback) > Unable to compute ceiling for max when histogram > > > Key: CASSANDRA-15324 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15324 > Project: Cassandra > Issue Type: Bug > Components: Local/Compaction, Local/Compaction/STCS >Reporter: HsuML >Priority: Normal > > I have 9 cassandra nodes. When I create a keyspace that has 15 tables and the > record count of all table are about 8.2 billion. I imported data through my > java loaders, and I found out the system.log has error message. What happened > and how can I solve the error? > Exception in thread Thread[CompactionExecutor:113041,1,main] > java.lang.IllegalStateException: Unable to compute ceiling for max when > histogram overflowed > at > org.apache.cassandra.utils.EstimatedHistogram.rawMean(EstimatedHistogram.java:231) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.utils.EstimatedHistogram.mean(EstimatedHistogram.java:220) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.io.sstable.metadata.StatsMetadata.getEstimatedDroppableTombstoneRatio(StatsMetadata.java:115) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.io.sstable.format.SSTableReader.getEstimatedDroppableTombstoneRatio(SSTableReader.java:1926) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.worthDroppingTombstones(AbstractCompactionStrategy.java:424) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy.getNextBackgroundSSTables(SizeTieredCompactionStrategy.java:99) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy.getNextBackgroundTask(SizeTieredCompactionStrategy.java:183) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.getNextBackgroundTask(CompactionStrategyManager.java:153) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionCandidate.run(CompactionManager.java:260) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ~[na:1.8.0_191] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > ~[na:1.8.0_191] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > ~[na:1.8.0_191] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [na:1.8.0_191] > at > org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81) > [apache-cassandra-3.11.4.jar:3.11.4] > at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_191] -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15324) Unable to compute ceiling for max when histogram
[ https://issues.apache.org/jira/browse/CASSANDRA-15324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928322#comment-16928322 ] Dinesh Joshi commented on CASSANDRA-15324: -- Your issue is likely related to your data model. Its better to discuss it on the [user mailing list|http://cassandra.apache.org/community/]. > Unable to compute ceiling for max when histogram > > > Key: CASSANDRA-15324 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15324 > Project: Cassandra > Issue Type: Bug > Components: Local/Compaction, Local/Compaction/STCS >Reporter: HsuML >Priority: Normal > > I have 9 cassandra nodes. When I create a keyspace that has 15 tables and the > record count of all table are about 8.2 billion. I imported data through my > java loaders, and I found out the system.log has error message. What happened > and how can I solve the error? > Exception in thread Thread[CompactionExecutor:113041,1,main] > java.lang.IllegalStateException: Unable to compute ceiling for max when > histogram overflowed > at > org.apache.cassandra.utils.EstimatedHistogram.rawMean(EstimatedHistogram.java:231) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.utils.EstimatedHistogram.mean(EstimatedHistogram.java:220) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.io.sstable.metadata.StatsMetadata.getEstimatedDroppableTombstoneRatio(StatsMetadata.java:115) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.io.sstable.format.SSTableReader.getEstimatedDroppableTombstoneRatio(SSTableReader.java:1926) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.worthDroppingTombstones(AbstractCompactionStrategy.java:424) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy.getNextBackgroundSSTables(SizeTieredCompactionStrategy.java:99) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy.getNextBackgroundTask(SizeTieredCompactionStrategy.java:183) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.getNextBackgroundTask(CompactionStrategyManager.java:153) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionCandidate.run(CompactionManager.java:260) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ~[na:1.8.0_191] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > ~[na:1.8.0_191] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > ~[na:1.8.0_191] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [na:1.8.0_191] > at > org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81) > [apache-cassandra-3.11.4.jar:3.11.4] > at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_191] -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15324) Unable to compute ceiling for max when histogram
[ https://issues.apache.org/jira/browse/CASSANDRA-15324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928268#comment-16928268 ] HsuML commented on CASSANDRA-15324: --- Yes, I have seen the article. But, I don't know what kind of data model is better and I try to truncate the table which has big partition size. The error doesn't stop, how can I solve it? Drop all tables and re-construct the cluster? > Unable to compute ceiling for max when histogram > > > Key: CASSANDRA-15324 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15324 > Project: Cassandra > Issue Type: Bug > Components: Local/Compaction, Local/Compaction/STCS >Reporter: HsuML >Priority: Normal > > I have 9 cassandra nodes. When I create a keyspace that has 15 tables and the > record count of all table are about 8.2 billion. I imported data through my > java loaders, and I found out the system.log has error message. What happened > and how can I solve the error? > Exception in thread Thread[CompactionExecutor:113041,1,main] > java.lang.IllegalStateException: Unable to compute ceiling for max when > histogram overflowed > at > org.apache.cassandra.utils.EstimatedHistogram.rawMean(EstimatedHistogram.java:231) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.utils.EstimatedHistogram.mean(EstimatedHistogram.java:220) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.io.sstable.metadata.StatsMetadata.getEstimatedDroppableTombstoneRatio(StatsMetadata.java:115) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.io.sstable.format.SSTableReader.getEstimatedDroppableTombstoneRatio(SSTableReader.java:1926) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.worthDroppingTombstones(AbstractCompactionStrategy.java:424) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy.getNextBackgroundSSTables(SizeTieredCompactionStrategy.java:99) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy.getNextBackgroundTask(SizeTieredCompactionStrategy.java:183) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.getNextBackgroundTask(CompactionStrategyManager.java:153) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionCandidate.run(CompactionManager.java:260) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ~[na:1.8.0_191] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > ~[na:1.8.0_191] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > ~[na:1.8.0_191] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [na:1.8.0_191] > at > org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81) > [apache-cassandra-3.11.4.jar:3.11.4] > at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_191] -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15324) Unable to compute ceiling for max when histogram
[ https://issues.apache.org/jira/browse/CASSANDRA-15324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928227#comment-16928227 ] Dinesh Joshi commented on CASSANDRA-15324: -- Have you seen CASSANDRA-11063? > Unable to compute ceiling for max when histogram > > > Key: CASSANDRA-15324 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15324 > Project: Cassandra > Issue Type: Bug > Components: Local/Compaction, Local/Compaction/STCS >Reporter: HsuML >Priority: Normal > > I have 9 cassandra nodes. When I create a keyspace that has 15 tables and the > record count of all table are about 8.2 billion. I imported data through my > java loaders, and I found out the system.log has error message. What happened > and how can I solve the error? > Exception in thread Thread[CompactionExecutor:113041,1,main] > java.lang.IllegalStateException: Unable to compute ceiling for max when > histogram overflowed > at > org.apache.cassandra.utils.EstimatedHistogram.rawMean(EstimatedHistogram.java:231) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.utils.EstimatedHistogram.mean(EstimatedHistogram.java:220) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.io.sstable.metadata.StatsMetadata.getEstimatedDroppableTombstoneRatio(StatsMetadata.java:115) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.io.sstable.format.SSTableReader.getEstimatedDroppableTombstoneRatio(SSTableReader.java:1926) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.worthDroppingTombstones(AbstractCompactionStrategy.java:424) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy.getNextBackgroundSSTables(SizeTieredCompactionStrategy.java:99) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy.getNextBackgroundTask(SizeTieredCompactionStrategy.java:183) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.getNextBackgroundTask(CompactionStrategyManager.java:153) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionCandidate.run(CompactionManager.java:260) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ~[na:1.8.0_191] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > ~[na:1.8.0_191] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > ~[na:1.8.0_191] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [na:1.8.0_191] > at > org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81) > [apache-cassandra-3.11.4.jar:3.11.4] > at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_191] -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15324) Unable to compute ceiling for max when histogram
[ https://issues.apache.org/jira/browse/CASSANDRA-15324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-15324: - Status: Awaiting Feedback (was: Triage Needed) > Unable to compute ceiling for max when histogram > > > Key: CASSANDRA-15324 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15324 > Project: Cassandra > Issue Type: Bug > Components: Local/Compaction, Local/Compaction/STCS >Reporter: HsuML >Priority: Normal > > I have 9 cassandra nodes. When I create a keyspace that has 15 tables and the > record count of all table are about 8.2 billion. I imported data through my > java loaders, and I found out the system.log has error message. What happened > and how can I solve the error? > Exception in thread Thread[CompactionExecutor:113041,1,main] > java.lang.IllegalStateException: Unable to compute ceiling for max when > histogram overflowed > at > org.apache.cassandra.utils.EstimatedHistogram.rawMean(EstimatedHistogram.java:231) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.utils.EstimatedHistogram.mean(EstimatedHistogram.java:220) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.io.sstable.metadata.StatsMetadata.getEstimatedDroppableTombstoneRatio(StatsMetadata.java:115) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.io.sstable.format.SSTableReader.getEstimatedDroppableTombstoneRatio(SSTableReader.java:1926) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.worthDroppingTombstones(AbstractCompactionStrategy.java:424) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy.getNextBackgroundSSTables(SizeTieredCompactionStrategy.java:99) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy.getNextBackgroundTask(SizeTieredCompactionStrategy.java:183) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.getNextBackgroundTask(CompactionStrategyManager.java:153) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionCandidate.run(CompactionManager.java:260) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ~[na:1.8.0_191] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > ~[na:1.8.0_191] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > ~[na:1.8.0_191] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [na:1.8.0_191] > at > org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81) > [apache-cassandra-3.11.4.jar:3.11.4] > at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_191] -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15324) Unable to compute ceiling for max when histogram
[ https://issues.apache.org/jira/browse/CASSANDRA-15324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-15324: - Component/s: (was: Documentation/Blog) Local/Compaction/STCS Local/Compaction > Unable to compute ceiling for max when histogram > > > Key: CASSANDRA-15324 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15324 > Project: Cassandra > Issue Type: Bug > Components: Local/Compaction, Local/Compaction/STCS >Reporter: HsuML >Priority: Normal > > I have 9 cassandra nodes. When I create a keyspace that has 15 tables and the > record count of all table are about 8.2 billion. I imported data through my > java loaders, and I found out the system.log has error message. What happened > and how can I solve the error? > Exception in thread Thread[CompactionExecutor:113041,1,main] > java.lang.IllegalStateException: Unable to compute ceiling for max when > histogram overflowed > at > org.apache.cassandra.utils.EstimatedHistogram.rawMean(EstimatedHistogram.java:231) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.utils.EstimatedHistogram.mean(EstimatedHistogram.java:220) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.io.sstable.metadata.StatsMetadata.getEstimatedDroppableTombstoneRatio(StatsMetadata.java:115) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.io.sstable.format.SSTableReader.getEstimatedDroppableTombstoneRatio(SSTableReader.java:1926) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.AbstractCompactionStrategy.worthDroppingTombstones(AbstractCompactionStrategy.java:424) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy.getNextBackgroundSSTables(SizeTieredCompactionStrategy.java:99) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy.getNextBackgroundTask(SizeTieredCompactionStrategy.java:183) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.CompactionStrategyManager.getNextBackgroundTask(CompactionStrategyManager.java:153) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionCandidate.run(CompactionManager.java:260) > ~[apache-cassandra-3.11.4.jar:3.11.4] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > ~[na:1.8.0_191] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > ~[na:1.8.0_191] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > ~[na:1.8.0_191] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [na:1.8.0_191] > at > org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81) > [apache-cassandra-3.11.4.jar:3.11.4] > at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_191] -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
