[
https://issues.apache.org/jira/browse/CASSANDRA-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240524#comment-13240524
]
Brandon Williams commented on CASSANDRA-3722:
---------------------------------------------
A few things while I continue to test:
Compaction can occur before the gossiper is started (and indeed, while gossip
is deactivated):
{noformat}
ERROR 23:38:09,192 Exception in thread Thread[CompactionExecutor:1,1,main]
java.lang.AssertionError
at
org.apache.cassandra.gms.Gossiper.addLocalApplicationState(Gossiper.java:1105)
at
org.apache.cassandra.service.StorageService.reportSeverity(StorageService.java:790)
at
org.apache.cassandra.db.compaction.CompactionManager$CompactionExecutor.beginCompaction(CompactionManager.java:1021)
at
org.apache.cassandra.db.compaction.CompactionTask.execute(CompactionTask.java:136)
at
org.apache.cassandra.db.compaction.CompactionManager$1.runMayThrow(CompactionManager.java:128)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:26)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{noformat}
getConnectionManagers is unused, but I imagine that was to help with the
hashcode business that we can now remove.
> Send Hints to Dynamic Snitch when Compaction or repair is going on for a node.
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-3722
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3722
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.1.0
> Reporter: Vijay
> Assignee: Vijay
> Priority: Minor
> Attachments: 0001-CASSANDRA-3722-A1-V2.patch,
> 0001-CASSANDRA-3722-A1.patch, 0001-CASSANDRA-3723-A2-Patch.patch,
> 0001-Expose-SP-latencies-in-nodetool-proxyhistograms.txt
>
>
> Currently Dynamic snitch looks at the latency for figuring out which node
> will be better serving the requests, this works great but there is a part of
> the traffic sent to collect this data... There is also a window when Snitch
> doesn't know about some major event which are going to happen on the node
> (Node which is going to receive the data request).
> It would be great if we can send some sort hints to the Snitch so they can
> score based on known events causing higher latencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
