-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
General mayhem #12108
General mayhem #12108
Conversation
The zclient data structure was not being cleaned up on shutdown. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Pre: staticd: showing active allocations in memory group libfrr staticd: memstats: Scripting : 16 * (variably sized) staticd: memstats: Hash : 2 * (variably sized) staticd: memstats: Hash Bucket : 8 * 32 staticd: memstats: Hash Index : 1 * (variably sized) staticd: memstats: Link List : 1 * 40 staticd: memstats: Link Node : 1 * 24 staticd: showing active allocations in memory group logging subsystem staticd: memstats: log file target : 1 * 88 staticd: showing active allocations in memory group staticd Post: staticd: showing active allocations in memory group libfrr staticd: showing active allocations in memory group logging subsystem staticd: memstats: log file target : 1 * 88 staticd: showing active allocations in memory group staticd Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
struct frrscript_codec *c = data; | ||
char *constworkaroundandihateit = (char *)c->typename; | ||
|
||
XFREE(MTYPE_SCRIPT, constworkaroundandihateit); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😄
Continuous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-PULLREQ2-7856/ This is a comment from an automated CI system. |
@Mergifyio backport dev/8.4 stable/8.3 |
✅ Backports have been created
|
General mayhem (backport #12108)
General mayhem (backport #12108)
*currently bgp schedules an event to zebra socket connect. if bgp config is processed before the socket establishment, then all the neighbor registeration will stall in bgp, as bgp doesn't handle the rnh register failure with zebra. *Added the zebra socket retry in bgp to retry for 12 times with 10 seconds interval. *This issue observed in a cluster where the storage is being put in a cross regional account. it could cause the issue as we aread the inf_config.json file in the zebra bootup. *adding the patch to dev folder for future reference. (cherry picked from commit 94aeebc)
*currently bgp schedules an event to zebra socket connect. if bgp config is processed before the socket establishment, then all the neighbor registeration will stall in bgp, as bgp doesn't handle the rnh register failure with zebra. *Added the zebra socket retry in bgp to retry for 12 times with 10 seconds interval. *This issue observed in a cluster where the storage is being put in a cross regional account. it could cause the issue as we aread the inf_config.json file in the zebra bootup. *adding the patch to dev folder for future reference. (cherry picked from commit 94aeebc)
This reverts commit a8fad43.
This reverts commit a8fad43.
*currently bgp schedules an event to zebra socket connect. if bgp config is processed before the socket establishment, then all the neighbor registeration will stall in bgp, as bgp doesn't handle the rnh register failure with zebra. *Added the zebra socket retry in bgp to retry for 12 times with 10 seconds interval. *This issue observed in a cluster where the storage is being put in a cross regional account. it could cause the issue as we aread the inf_config.json file in the zebra bootup. *adding the patch to dev folder for future reference. (cherry picked from commit 94aeebc)
*currently bgp schedules an event to zebra socket connect. if bgp config is processed before the socket establishment, then all the neighbor registeration will stall in bgp, as bgp doesn't handle the rnh register failure with zebra. *Added the zebra socket retry in bgp to retry for 12 times with 10 seconds interval. *This issue observed in a cluster where the storage is being put in a cross regional account. it could cause the issue as we aread the inf_config.json file in the zebra bootup. *adding the patch to dev folder for future reference. (cherry picked from commit 94aeebc)
Some memory leaks on shutdown being fixed