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
Bug 1862700: Fix ovnkube-node aggressive memory allocation to prevent memory bloating #227
Bug 1862700: Fix ovnkube-node aggressive memory allocation to prevent memory bloating #227
Conversation
@vishnoianil: No Bugzilla bug is referenced in the title of this pull request. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@vishnoianil: This pull request references Bugzilla bug 1859883, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@vishnoianil: This pull request references Bugzilla bug 1862700, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/bugzilla refresh |
@vishnoianil: This pull request references Bugzilla bug 1862700, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@dcbw PTAL |
/hold |
0d06537
to
e969892
Compare
/retest |
e969892
to
25f9442
Compare
/retest |
/retitle Bug 1862700: Fix ovnkube-node aggressive memory allocation to prevent memory bloating |
25f9442
to
a132d95
Compare
@dcbw all tests are passing on this patch. |
a132d95
to
8c33a5f
Compare
/retest |
/lgtm |
/hold cancel |
Note for the upcoming patch manager: This was meant to be approved in the last cycle but failed to get the label. PTAL. |
/retest Please review the full test history for this PR and help us cut down flakes. |
25 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@vishnoianil: All pull requests linked via external trackers have merged: Bugzilla bug 1862700 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
…memory bloating
- What this PR does and why is it needed
During the pod creation, ovnkube-node dump all the flows from br-int and grep
for the ip address of the pod to verify that pod related flows are programmed.
This can cause aggrasive and big memory allocation to store the string output
from ovs-ofctl command.
This patch optimized the ovs-ofctl dump-flow query to dump flows only related
to the pods. This will avoid dumping the massive string output and prevent
from memory bloating.
Signed-off-by: Anil Vishnoi avishnoi@redhat.com