Skip to content

[orchagent]: Extend syncd response timeout for APPLY_VIEW - #4818

Draft
YairRaviv wants to merge 1 commit into
sonic-net:masterfrom
YairRaviv:yraviv-mlnx-extend-applyview-timeout
Draft

[orchagent]: Extend syncd response timeout for APPLY_VIEW#4818
YairRaviv wants to merge 1 commit into
sonic-net:masterfrom
YairRaviv:yraviv-mlnx-extend-applyview-timeout

Conversation

@YairRaviv

Copy link
Copy Markdown
Contributor

What I did
Extended the SAI-Redis sync operation response timeout around APPLY_VIEW in syncd_apply_view(), matching the existing long timeout used for INIT_VIEW, then restored the default 60s timeout afterward.
Moved SAI_REDIS_SYNC_OPERATION_RESPONSE_TIMEOUT from saihelper.cpp to saihelper.h so both initSaiRedis() and syncd_apply_view() can share it.

Why I did it
During warm reboot at large route / full-KVD scale, syncd's APPLY_VIEW (view comparison + full ASIC_DB rewrite) can take longer than the default 60s SAI-Redis response timeout (observed ~88s). orchagent then fails the notify and aborts warm reboot even though syncd is still progressing.

How I verified it
Warm reboot at high route scale on a build with this change

Details if related

Signed-off-by: Yair Raviv <yraviv@nvidia.com>
@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants