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
Currently there's a field in the SchedulerServer for recording caller ip which sends requests to the scheduler. However, for one scheduler, there will be multiple clients. Concurrency issue may occur. It's not a good way for record the requester info in a global field. Therefore, it's better to remove it from the SchedulerServer.
We can get the requester ip from the hyper info and set it to the tonic info. Then in each tonic-based grpc interface, we can get the the requester ip from the Request.
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently there's a field in the SchedulerServer for recording caller ip which sends requests to the scheduler. However, for one scheduler, there will be multiple clients. Concurrency issue may occur. It's not a good way for record the requester info in a global field. Therefore, it's better to remove it from the SchedulerServer.
We can get the requester ip from the hyper info and set it to the tonic info. Then in each tonic-based grpc interface, we can get the the requester ip from the Request.
The text was updated successfully, but these errors were encountered: