[
https://issues.apache.org/jira/browse/CASSANDRA-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams reopened CASSANDRA-2819:
-----------------------------------------
Assignee: Jonathan Ellis (was: Melvin Wang)
The target can be null when the host is killed before it fires:
{noformat}
ERROR [EXPIRING-MAP-REAPER:1] 2012-06-21 15:55:27,708
AbstractCassandraDaemon.java (line 133) Exception in thread
Thread[EXPIRING-MAP-REAPER:1,5,main]
java.lang.NullPointerException
at
org.apache.cassandra.net.MessagingService$5.apply(MessagingService.java:326)
at
org.apache.cassandra.net.MessagingService$5.apply(MessagingService.java:322)
at org.apache.cassandra.utils.ExpiringMap$1.run(ExpiringMap.java:99)
at
org.apache.cassandra.concurrent.DebuggableScheduledThreadPoolExecutor$UncomplainingRunnable.run(DebuggableScheduledThreadPoolExecutor.java:75)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
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}
> Split rpc timeout for read and write ops
> ----------------------------------------
>
> Key: CASSANDRA-2819
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2819
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Stu Hood
> Assignee: Jonathan Ellis
> Fix For: 1.2
>
> Attachments: 2819-v4.txt, 2819-v5-rebased.txt, 2819-v8.txt,
> 2819-v9.txt, c2819-v6, c2819-v7, c2819.patch, rpc-jira.patch
>
>
> Given the vastly different latency characteristics of reads and writes, it
> makes sense for them to have independent rpc timeouts internally.
--
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
