You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the DSIP and found no similar DSIP.
Motivation
Right now, the log is stored at worker/master and remote storage.
The query logic look like below
The LogService is duplicate at worker/master, we need to maintain two service implementation which have the same code.
And once the master/worker is not active, then we can not fetch the log, this problem may occur frequently in k8s.
So it's better to create a LogClient at API side to manage the log fetch logic, and create a LogServer to response for the client request, the LogServer will be imported at master/worker.
Design Detail
We will fetch the log from master/worker firstly.
If the master/worker not exist or we cannot find the log file from master/worker then we will try to fetch from remote log storage.
Search before asking
Motivation
Right now, the log is stored at worker/master and remote storage.
The query logic look like below
The LogService is duplicate at worker/master, we need to maintain two service implementation which have the same code.
And once the master/worker is not active, then we can not fetch the log, this problem may occur frequently in k8s.
So it's better to create a LogClient at API side to manage the log fetch logic, and create a LogServer to response for the client request, the LogServer will be imported at master/worker.
Design Detail
Compatibility, Deprecation, and Migration Plan
Compatibility with previous version.
Test Plan
Test by manual.
Code of Conduct
The text was updated successfully, but these errors were encountered: