Affects Version/s: 0.8.0
Fix Version/s: 0.8.0
In 0.7 if a partition was down we would just send the message elsewhere. This meant that the partitioning was really more of a "stickiness" then a hard guarantee. This made it impossible to depend on it for partitioned, stateful processing.
In 0.8 when running with replication this should not be a problem generally as the partitions are now highly available and fail over to other replicas. However in the case of replication factor = 1 no longer really works for most cases as now a dead broker will give errors for that broker.
I am not sure of the best fix. Intuitively I think this is something that should be handled by the Partitioner interface. However currently the partitioner has no knowledge of which nodes are available. So you could use a random partitioner, but that would keep going back to the down node.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|1d 2h 51m||1||Jun Rao||10/Jan/13 19:09|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Assignee||Maxime Brugidou [ brugidou ]|
|Fix Version/s||0.8 [ 12317244 ]|
|Resolution||Fixed [ 1 ]|