Skip to content

Conversation

@andrijapanicsb
Copy link
Contributor

Logs:

2025-04-24 19:04:20,912 INFO [o.a.c.e.o.NetworkOrchestrator] (Network-Scavenger-1:ctx-34a60b9f) (logid:ab827a5e) NetworkGarbageCollector uses '121' seconds for GC interval.
^C

Actual values (with mgmt server restart done after the value changes):

image

@codecov
Copy link

codecov bot commented Apr 24, 2025

Codecov Report

❌ Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 16.26%. Comparing base (1300fc5) to head (ca8bb8e).

Files with missing lines Patch % Lines
...tack/engine/orchestration/NetworkOrchestrator.java 0.00% 3 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff            @@
##               4.20   #10776   +/-   ##
=========================================
  Coverage     16.26%   16.26%           
- Complexity    13420    13422    +2     
=========================================
  Files          5658     5658           
  Lines        499496   499497    +1     
  Branches      60626    60626           
=========================================
+ Hits          81234    81250   +16     
+ Misses       409214   409197   -17     
- Partials       9048     9050    +2     
Flag Coverage Δ
uitests 4.02% <ø> (ø)
unittests 17.12% <0.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

logger.info("NetworkGarbageCollector uses '{}' seconds for GC interval.", netGcWait);
final int netGcInterval = NumbersUtil.parseInt(_configDao.getValue(NetworkGcInterval.key()), 60);
logger.info("NetworkGarbageCollector uses '{}' seconds for GC wait.", netGcWait);
logger.info("NetworkGarbageCollector uses '{}' seconds for GC interval.", netGcInterval);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps these 2 lines can be unified into a single one: NetworkGarbageCollector uses '{}' seconds for GC wait and '{}' seconds for GC interval.

andrijapanicsb and others added 3 commits April 25, 2025 06:56
Update dynamic setting for the network.gc.intervla and the wrong message for wait period.
network.gc.value was mistakenly obtained from network.gc.wait
added messages for both gc.wait and gc.internval.
@nvazquez nvazquez force-pushed the network-gc-wait-dynamic branch from ee5c057 to e0e9d64 Compare April 25, 2025 09:58
@nvazquez nvazquez changed the base branch from main to 4.20 April 25, 2025 09:58
@nvazquez nvazquez changed the title Network gc wait dynamic Fix logs mismatch between Network GC wait and interval Apr 25, 2025
@nvazquez
Copy link
Contributor

@blueorangutan package

Copy link
Contributor

@sureshanaparti sureshanaparti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

clgtm

@sonarqubecloud
Copy link

"Time (in seconds) to wait before shutting down a network that's not in used", false, Scope.Global, null);
public static final ConfigKey<Integer> NetworkGcInterval = new ConfigKey<Integer>(Integer.class, "network.gc.interval", "Advanced", "600",
"Seconds to wait before checking for networks to shutdown", true, Scope.Global, null);
"Seconds to wait before checking for networks to shutdown", false, Scope.Global, null);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good 👍

btw: NetworkGcWait can be changed to Dynamic

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

true :)

@rajujith
Copy link

@andrijapanicsb Since this is for the 4.22.1 release, could you retarget the PR to the 4.22 branch?

…e/orchestration/NetworkOrchestrator.java

Co-authored-by: Wei Zhou <weizhou@apache.org>
@DaanHoogland
Copy link
Contributor

@blueorangutan package

@blueorangutan
Copy link

@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@blueorangutan
Copy link

Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 16582

@DaanHoogland
Copy link
Contributor

@blueorangutan test

@blueorangutan
Copy link

@DaanHoogland a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 40%)

See analysis details on SonarQube Cloud

@blueorangutan
Copy link

[SF] Trillian test result (tid-15320)
Environment: kvm-ol8 (x2), zone: Advanced Networking with Mgmt server ol8
Total time taken: 53079 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr10776-t15320-kvm-ol8.zip
Smoke tests completed. 140 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test Result Time (s) Test File
test_01_redundant_vpc_site2site_vpn Failure 439.04 test_vpc_vpn.py

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants