1. Is there a way via the API to force it to update the DecomHosts field with fresh data? There's a slight delay after the decommission process finishes before it is returned in the DecomHosts field of the NAMENODE, which is creating a race condition in my automation (sometimes it doesn't see the decommissioning hosts and just goes ahead and removes the DATANODE before it has finished re-replicating blocks). 2. Where in the API does the UI detect that components have stale configs and need to be restarted? I haven't been able to find that yet.
Thanks in advance. Greg
