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/CONTROLLER-1668 controller <p>When running with tell-based protocol transactions dont seem to abort and fail with Transaction timeout after reaching hard-time out which seems to be 60seconds.</p> <p><a href="https://logs.opendaylight.org/sandbox/jenkins091/controller-csit-3node-clustering-only-carbon-2nd/13/archives/log.html.gz#s1-s1-t1-k2-k18-k3" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/sandbox/jenkins091/controller-csit-3node-clustering-only-carbon-2nd/13/archives/log.html.gz#s1-s1-t1-k2-k18-k3</a></p> <p>This suite tries to run write-transactions on an isolated node and expects<br/> that the transactions are aborted after reaching the hard timeout, however<br/> it fails after reaching timeout of 150seconds on the robot side.</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1668

Tell based protocol doesnt time out transactions after hard-timeout.

Bug Resolved Done Robert Varga Tomas Cere Thu, 11 May 2017 13:11:56 +0000 Tue, 25 Jul 2023 08:24:36 +0000 Wed, 17 May 2017 17:04:20 +0000 clustering 0 3 <p>Upon investigating the code paths it seems like were losing track of the original enque times once requests are replayed, leading to never reaching the timeout since the timer is reset for each request.</p> <p>This is an artifact of the code structure change with the request queue. The expectation was that the original submitter would retry the request on timeout, but that is not feasible and we really need to separate the timeouts for the request (i.e. its forward progress) and reconnect-and-retry logic.</p> <p>As a first step, <a href="https://git.opendaylight.org/gerrit/56747" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/56747</a> cleans up the replay logic so that we do not lose the enqueue timers. A follow-up patch will separate out the retry logic.</p> <p>Lowering this to major as it's not a blocking issue for the Carbon release since tell-based won't be enabled by default.</p> <p>This actually affects prefix-based shards, rendering them vulnerable.</p> <p>The timer part:<br/> <a href="https://git.opendaylight.org/gerrit/56874" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/56874</a></p> <p>Can your team take a look and update the status of this bug. With the patch <a href="https://git.opendaylight.org/gerrit/#/c/56874/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/56874/</a> was successfully merged, can we mark this bug as fixed and resolved?</p> Blocks CONTROLLER-1665 CONTROLLER-1674 Development External issue ID 8422 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02rzr: