cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Overton (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4384) HintedHandoff can begin before SS knows the hostID
Date Wed, 11 Jul 2012 15:20:35 GMT


Sam Overton commented on CASSANDRA-4384:

I have a branch at which
* gossips host ID on startup
* persists host IDs to the peers CF and loads them on startup

I ended up changing the peers schema to be keyed off IP address instead of UUID:
  peer inet PRIMARY KEY,
  token_bytes blob,
  ring_id uuid,

I agree with Sylvain that it seems more natural to use UUID as the key rather than by IP,
but that didn't seem as straightforward to update when tokens or hostIds change.

There is some overlap with CASSANDRA-4122 so it would be best to wait for that to go in before
changing the SystemTable again for this.

> 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