https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/BGPCEP-174 bgpcep <p>To hit this bug, configure a BGP speaker to have HoldTimer set to 3 seconds and then point it to ODL. Then let the BGP speaker wait about 0.5 seconds and then send 1750 updates. If you have topology updates turned OFF in the ODL instance, you can ask the BGP speaker to send up to 5000 updates.</p> <p>The speaker won't see any KeepAlive messages coming from ODL while it is sending the updates, thus closing the connection down.</p> <p>The problem can happen with other HoldTimer values as well. If the speaker starts sending a lot of updates at the time when the HoldTimer is nearly expired, then ODL is going to miss the HoldTimer deadline.</p> <p>This may be related to <a href="https://jira.opendaylight.org/browse/YANGTOOLS-383" title="Clustering: ModifiedNodeDoesNotExistException on 1800 or more updates" class="issue-link" data-issue-key="YANGTOOLS-383"><del>YANGTOOLS-383</del></a> but I am not sure.</p> <p>Operating System: All<br/> Platform: All</p> BGPCEP-174

Keepalive not sent when updates are being processed

Bug Resolved Done Robert Varga Jozef Behran Thu, 4 Dec 2014 09:41:59 +0000 Sun, 3 Mar 2019 11:50:22 +0000 Thu, 22 Jan 2015 15:55:17 +0000 Bugzilla Migration Bugzilla Migration BGP 0 5 <p>Update: To hit this bug now (when <a href="https://jira.opendaylight.org/browse/YANGTOOLS-383" title="Clustering: ModifiedNodeDoesNotExistException on 1800 or more updates" class="issue-link" data-issue-key="YANGTOOLS-383"><del>YANGTOOLS-383</del></a> is still present) you need to switch topology off and then use a BGP speaker to push 2500 to 5000 updates all at once. With topology updating enabled <a href="https://jira.opendaylight.org/browse/YANGTOOLS-383" title="Clustering: ModifiedNodeDoesNotExistException on 1800 or more updates" class="issue-link" data-issue-key="YANGTOOLS-383"><del>YANGTOOLS-383</del></a> will hit before you can get to see this bug.</p> <p>Update: After more investigation it turned out that the problem is most likely to be big garbage collection being started during time when the BGP speaker is making the connection with 3 second Hold Timer, then ODL is not going to make it with a KeepAlive message in time.</p> <p>When I placed a wait into the test which waited one minute after seeing that BGP socket in ODL, this problem did not show up at all (but I hit <a href="https://jira.opendaylight.org/browse/YANGTOOLS-383" title="Clustering: ModifiedNodeDoesNotExistException on 1800 or more updates" class="issue-link" data-issue-key="YANGTOOLS-383"><del>YANGTOOLS-383</del></a> in that case).</p> <p>Additionally after I opened the profiler snapshot (together with Dana), we realized that clustering was still running during the test. Tt was not used at all but this still means that the possibility that the problem is due to clustering is still open.</p> <p>I also (together with Dana) started to suspect that avoiding asking the GC for big garbage collections and using -XX:+UseG1GC will improve matters a lot. I can do the test with -XX:+UseG1GC but the "avoiding asking the GC for big garbage collection" part needs to be done by somebody who can find the place where the offending GC call is made.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/13479/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/13479/</a></p> <p><a href="https://git.opendaylight.org/gerrit/#/c/13479/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/13479/</a></p> <p>Still seems to be reproducible with current master. Analysis is pending.</p> <p>master: <a href="https://git.opendaylight.org/gerrit/14380" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/14380</a><br/> helium: <a href="https://git.opendaylight.org/gerrit/14381" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/14381</a></p> Development External issue ID 2475 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02anr: