Skip to content

[node/NodeNetworkErrs] fix some typos #54

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.

Sign up for GitHub

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

[node/NodeNetworkErrs] fix some typos #54

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a0985ba
[node/NodeNetworkTransmitErrs] fix some typos
hayk96 Jun 7, 2023
0c1c667
Merge branch 'prometheus-operator:main' into main
hayk96 Nov 12, 2023
d3ac390
[node/NodeNetworkReceiveErrs] fix typo
hayk96 Nov 12, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/runbooks/node/NodeNetworkReceiveErrs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Network attached storage performance issues or even data loss.

## Diagnosis

Investigate networkng issues on the node and to connected hardware.
Investigate networking issues on the node and to connected hardware.
Check physical cables, check networking firewall rules and so on.

## Mitigation
Expand Down
4 changes: 2 additions & 2 deletions content/runbooks/node/NodeNetworkTransmitErrs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Network attached storage performance issues or even data loss.

## Diagnosis

Investigate networkng issues on the node and to connected hardware.
Investigate networking issues on the node and to connected hardware.
Check network interface saturation.
Check CPU usage saturation.
Check physical cables, check networking firewall rules and so on.
Expand All @@ -30,5 +30,5 @@ networking.
- [Increase TX queue length](https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/ovs-dpdk_end_to_end_troubleshooting_guide/high_packet_loss_in_the_tx_queue_of_the_instance_s_tap_interface)
- Spread services to other nodes/pods.
- Replace physical cables, change ports.
- Look into introducting Quality of Service or other
- Look into introducing Quality of Service or other
[TCP congestion avoidance algorithms](https://en.wikipedia.org/wiki/TCP_congestion_control)