-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: not to use blocking get_all() after keys() #255
Conversation
In a dynamic environment, it is possible that some of the keys may disappear between invoking keys() and get_all().
Going ahead, how do we figure out if we have to use blocking call or not for a given Table in DB? |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
In a dynamic environment, it is possible that some of the keys may disappear between invoking keys() and get_all(). Prevent unnecessary timeout of blocking get_all().
Follow up #255. If route change too fast between keys/hgetall, the original implementation will throw exception and lead to ERR in syslog.
Follow up sonic-net#255. If route change too fast between keys/hgetall, the original implementation will throw exception and lead to ERR in syslog.
In a dynamic environment, it is possible that some of the keys may disappear between invoking keys() and get_all(). Prevent unnecessary timeout of blocking get_all().
Follow up #255. If route change too fast between keys/hgetall, the original implementation will throw exception and lead to ERR in syslog.
Follow up #255. If route change too fast between keys/hgetall, the original implementation will throw exception and lead to ERR in syslog.
In a dynamic environment, it is possible that some of the keys may disappear between invoking keys() and get_all(). Prevent unnecessary timeout of blocking get_all().
In a dynamic environment, it is possible that some of the keys may disappear between invoking keys() and get_all(). Prevent unnecessary timeout of blocking get_all(). Add more snmp no blocking fix for sonic-net#255 - How I did it Modify the blocking mode from True to False - How to verify it Use server to send with 1000 requests/second. Keep test for weekend and it do not happen.
In a dynamic environment, it is possible that some of the keys may disappear between invoking keys() and get_all(). Prevent unnecessary timeout of blocking get_all(). Add more snmp no blocking fix for sonic-net#255 - How I did it Modify the blocking mode from True to False - How to verify it Use server to send with 1000 requests/second. Keep test for weekend and it do not happen.
- What I did
In a dynamic environment, it is possible that some of the keys may
disappear between invoking keys() and get_all().
Prevent unnecessary timeout of blocking get_all().
- How I did it
- How to verify it
- Description for the changelog