merge master into this branch#168
Merged
vince-weka merged 39 commits intovince/os-kernel-updatesfrom Jun 23, 2025
Merged
Conversation
Raise a warning if the current NFSW FD usage is >=90% of the configured maximum.
Changes for Weka4 - OS, IOMMU and NTP & OFED
Added parallel-compare scripts
merge-conflicts
- Provide IPv6 support in FIPs sanity, mgmt IP, netmask and SBR checks - Remove jq dependency in NATS check
IPv6 updates and code cleanup
Query NFSW FD usage
Collaborator
|
@vince-weka I don't think you need us to do anything here right? Looks like you're rebasing your branch to include changes from master. |
Contributor
Author
|
Exactly
Vince Fleming
Director, Engineering at WEKA
M 848-220-0041* *E ***@***.**** *W www.weka.io
<https://www.weka.io/?utm_source=WiseStamp&utm_medium=email&utm_term=&utm_content=&utm_campaign=signature>*
* * *
<http://weka.io/4>
…On Wed, May 7, 2025 at 8:53 AM jackchallen ***@***.***> wrote:
*jackchallen* left a comment (weka/wekachecker#168)
<#168 (comment)>
@vince-weka <https://github.com/vince-weka> I don't think you need us to
do anything here right? Looks like you're rebasing your branch to include
changes from master.
—
Reply to this email directly, view it on GitHub
<#168 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK7ZJL56HQWI3AXPB36KP7D25H6ZHAVCNFSM6AAAAAB3ZKB5GSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNJYGQ3TGOJVGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Clusters with 0 hot-spare can potentially be configured to allocate and use ~100% of SSD capacity. In the case of loss of a failure domain they'll lose a proportion of FS space (known as shrinkage). The proportion lost is dependent on the number of data disks, and if "too much" is lost then writes can fail with ENOSPACE. Essentially, we should warn customers without hot spares configured
Add a very basic capacity check in the case of 0 hot-spare clusters
In https://wekaio.atlassian.net/browse/WEKAPP-482528 we saw that the link speed was lower than expected, but there were no warnings. We should check that. The only plausible way I can find of doing this is by parsing the text-based output of ethtool, until jq and "ethtool --json" get everywhere, or the kernel interface to ethtool-netlink is exposed in /sys, I can't see any other way of doing it. :(
We don't want weka cluster buckets becoming too full, or too imbalanced. Ordinarily the RAID stripe allocation takes care of this for us, but in at least https://wekaio.atlassian.net/browse/WEKAPP-488736 (for example) network interruptions led to us not being able to find free stripes. This in turn led to buckets becoming full and thus FS writes stalling.
Stupid typo fix
Add a check to examine bucket fill levels
Basic RDMA errors check as per #weka-platform Slack
Basic checker to compare current NIC link speed with maximum
+3 statistics as per internal slack channel
Check to ensure cluster drives have consistent block sizes, and if not, raise a warning.
NVME block size check
This was RCA'd down to too many connections to Ganesha, so we should start checking this.
In WEKAPP-502848 we saw that NFS service was failing over
…iners_in_gateway_check Should exclude dataservice containers from these checks
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
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.
No description provided.