deterministic hash for partitioning
Bug #1745184 reported by
gordon chung
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ceilometer |
New
|
Undecided
|
Unassigned | ||
Bug Description
in notification agent, we use hash() to decide which queue to shard data to. this might not return consistent results which could cause related metrics/events to be push to different nodes. if this happens, our transformers (and batching) get screwed up.
switch away from hash()
To post a comment you must log in.
