[
https://issues.apache.org/jira/browse/CASSANDRA-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-3440.
---------------------------------------
Resolution: Fixed
Updated to use this instead and committed:
{code}
. private static final Map<InetAddress, AtomicInteger> hintsInProgress = new
MapMaker().concurrencyLevel(1).makeComputingMap(new Function<InetAddress,
AtomicInteger>()
{
public AtomicInteger apply(InetAddress inetAddress)
{
return new AtomicInteger(0);
}
});
{code}
> local writes timing out cause attempt to hint to self
> -----------------------------------------------------
>
> Key: CASSANDRA-3440
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3440
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Labels: hintedhandoff
> Fix For: 1.0.4
>
> Attachments: 3440-v2.txt, 3440.txt
>
>
> As reported by Ramash Natarajan on the mailing list:
> {noformat}
> We have a 8 node cassandra cluster running 1.0.1. After running a load
> test for a day we are seeing this exception in system.log file.
> ERROR [EXPIRING-MAP-TIMER-1] 2011-11-01 13:20:45,350
> AbstractCassandraDaemon.java (line 133) Fatal exception in thread
> Thread[EXPIRING-MAP-TIMER-1,5,main]
> java.lang.AssertionError: /10.19.102.12
> at
> org.apache.cassandra.service.StorageProxy.scheduleLocalHint(StorageProxy.java:339)
> at
> org.apache.cassandra.net.MessagingService.scheduleMutationHint(MessagingService.java:201)
> at
> org.apache.cassandra.net.MessagingService.access$500(MessagingService.java:64)
> at
> org.apache.cassandra.net.MessagingService$2.apply(MessagingService.java:175)
> at
> org.apache.cassandra.net.MessagingService$2.apply(MessagingService.java:152)
> at org.apache.cassandra.utils.ExpiringMap$1.run(ExpiringMap.java:89)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> {noformat}
--
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
