Rate limit ioctl failures due to region database full messages #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: dennis-c-josifovich <dennis.c.josifovich@hpe.com>
If the module load directry does not exist, then the rpm post scriptlet will fail. Create the directory. Signed-off-by: James Swaro <james.swaro@hpe.com>
|
Sample messages being seen: |
|
Additional messages that are seen that needs to be rate limited as well, |
|
Hi Servesh. Thanks for opening this. HPE is working on incorporating in on the main branch. Once landed on main, it will be cherry-picked to release/shs-12.0. |
cleanWs was removed, and checkout can be performed at a higher level within Jenkins. Remove it from the pipeline Signed-off-by: James Swaro <james.swaro@hpe.com>
Signed-off-by: dennis-c-josifovich <dennis.c.josifovich@hpe.com>
servesh
force-pushed
the
fix-ratelimit-monitor-region
branch
from
2bbdc29 to
1c8ab68
Compare
|
Noticed that the main branch didn't have further changes noted above in comments. So updated the branch with the new commit that addresses further messages identified on Aurora. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On Aurora when using kdreg2 the logs are flooded with region database full messages. This eventually causes our backend log aggregation system to be overwhelmed. So proposing to ratelimit these functions.
If there are other parts of the code such behavior is expected, would be good to ratelimit them as well.