[GENIUS-141] DataTreeEventCallbackRegistrar does not work in Cluster in all scenarios Created: 29/May/18 Updated: 31/May/18 Resolved: 31/May/18 |
|
| Status: | Verified |
| Project: | genius |
| Component/s: | General |
| Affects Version/s: | Oxygen-SR2, Fluorine |
| Fix Version/s: | Oxygen-SR2, Fluorine |
| Type: | Bug | Priority: | High |
| Reporter: | Faseela K | Assignee: | Faseela K |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
In a 3 node cluster, if event A is received on node 1, and if a DataTreeEventCallback is registered at node 1, for a DataTree whose shard leader is node2, the DataTreeEvent will get fired on node2, where the callback is not available. In such scenarios, the callback handling is buggy. We have to add a clustering knob to DataTreeEventCallbackRegistrar. |
| Comments |
| Comment by Faseela K [ 31/May/18 ] |