cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4384) HintedHandoff can begin before SS knows the hostID
Date Fri, 29 Jun 2012 16:30:44 GMT


Sylvain Lebresne commented on CASSANDRA-4384:

bq. or we could replace the existing peers entirely

I would agree with that, but going a bit further I would imagine that a natural schema for
that peers table could be something like:
  peer inet,
  tokens set<blob>,
with maybe even more info for each host but that's for CASSANDRA-4351. Of course that specific
schema means waiting for CASSANDRA-3647, but I don't see that as a big problem. This wouldn't
let use query by token but I don't think that really matter because we'll read the whole table
content at startup anyway.
> HintedHandoff can begin before SS knows the hostID
> --------------------------------------------------
>                 Key: CASSANDRA-4384
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2
>            Reporter: Brandon Williams
>            Assignee: Eric Evans
>             Fix For: 1.2
> Since HH fires from the FD, SS won't quite have the hostId yet:
> {noformat}
>  INFO 18:58:04,196 Started hinted handoff for host: null with IP: /
>  INFO 18:58:04,197 Node / state jump to normal
> ERROR 18:58:04,197 Exception in thread Thread[HintedHandoff:1,1,main]
> java.lang.NullPointerException
>         at org.apache.cassandra.utils.UUIDGen.decompose(
>         at org.apache.cassandra.db.HintedHandOffManager.deliverHintsToEndpointInternal(
>         at org.apache.cassandra.db.HintedHandOffManager.deliverHintsToEndpoint(
>         at org.apache.cassandra.db.HintedHandOffManager.access$400(
>         at org.apache.cassandra.db.HintedHandOffManager$4.runMayThrow(
>         at
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at
> {noformat}
> Simple solution seems to be getting the hostId from gossip instead.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message