Description
This is a tracking bug. We saw during log analysis that deploying a handler calls setSettings on all nodes while it is sufficient to call on current node and let it propagate to other nodes via ns_config updates. This will avoid unnecessary conflicting writes.