Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.4.0
-
Reviewed
Description
When using the ObserverReadProxyProvider, clients can setÂ
dfs.client.failover.observer.auto-msync-period... to periodically get the Active namenode's state. When using routers without the ObserverReadProxyProvider, this periodic update is lost.
In a busy cluster, the Router constantly gets updated with the active namenode's state when
- There is a write operation.
- There is an operation (read/write) from a new clients.
However, in the scenario when there are no new clients and no write operations, the state kept in the router can lag behind the active's. The router does update its state with responses from the Observer, but the observer may be lagging behind too.
We should have a periodic refresh in the router to serve a similar role as dfs.client.failover.observer.auto-msync-period
Attachments
Issue Links
- links to