Enable sairedis counter thread in 3 minutes after SONiC was started #1805
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.
- What I did
Add functionality to delay starting counter thread and snmp service.
The counter thread will be enabled in 3 minutes after SONiC has been started. The snmp service will be started in 30 seconds later of the counter thread.
- How I did it
Using Sihui's changes in swss and sairedis and modifying systemd configuration.
- How to verify it
Build an image and run on DUT. Right after the start you should see that snmp is not running and
redis-cli monitor doesn't show any counter upgrades.
The counter will be started in 180 sec (you can check by redis-cli monitor) and snmp will be started in 210 sec.
You can check the timer status by
sudo systemctl list-timers --all
.You can check the services status by
sudo systemctl status snmp.service
andsudo systemctl status enable_counter.service
- Description for the changelog
Delay start of counter thread and snmp service.
- A picture of a cute animal (not mandatory but encouraged)