Skip to content
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

NSFS Fixes | handling too many forks exits + cleaning unwrap error in log #7807

Merged
merged 1 commit into from
Feb 19, 2024

Conversation

jackyalbo
Copy link
Contributor

@jackyalbo jackyalbo commented Feb 8, 2024

Explain the changes

  1. adding special handling in case of getting too many forks exits in a given time frame
  2. adding read_bucket_sdk_config_info to remove errors when running nsfs in simple mode

Issues: Fixed #xxx / Gap #xxx

Testing Instructions:

  • Doc added/updated
  • Tests added

src/util/fork_utils.js Outdated Show resolved Hide resolved
src/util/fork_utils.js Outdated Show resolved Hide resolved
src/util/fork_utils.js Outdated Show resolved Hide resolved
@jackyalbo jackyalbo force-pushed the jacky-nsfs-fixes branch 2 times, most recently from 8614140 to c9f50f3 Compare February 14, 2024 15:52
@jackyalbo jackyalbo changed the title NSFS Fixes | handling SIGABRT + cleanning unwrap error in log NSFS Fixes | handling too many forks exits + cleaning unwrap error in log Feb 14, 2024
@jackyalbo jackyalbo requested a review from romayalon February 14, 2024 15:54
@guymguym guymguym added NS-FS Non Containerized Non containerized labels Feb 15, 2024
src/util/fork_utils.js Show resolved Hide resolved
adding special handling in case of getting too many forks exits in a given time frame
adding read_bucket_sdk_config_info to remove errors when running nsfs in simple mode

Signed-off-by: jackyalbo <jacky.albo@gmail.com>
@jackyalbo jackyalbo merged commit cd50553 into noobaa:master Feb 19, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants