[CONTROLLER-1684] OutOfOrderRequestException when removing shard replica under load Created: 17/May/17 Updated: 25/Jul/23 Resolved: 19/May/17 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | clustering |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vratko Polak | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 8486 | ||||||||
| Description |
|
This is similar to This time we have a transaction producer (module-based shard, tell-based protocol) in the same member as the shard leader, and we call remove-shard-replica. Robot sees OutOfOrderRequestException [0]. The error is in the middle of the warning, starting with: [0] https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/692/archives/log.html.gz#s1-s20-t1-k2-k9-k1 |
| Comments |
| Comment by Vratko Polak [ 17/May/17 ] |
|
The next run shows UnreachableMember (CONTROLLER-1645 in principle) in karaf.log [2] , address: akka.tcp://opendaylight-cluster-data@10.29.15.116:2550 But for some reason OutOfOrderRequestException is no longer visible in karaf.log (at least o the original leader member), only in the response [3] visible from robot. [2] https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/693/archives/odl3_karaf.log.gz |
| Comment by Vratko Polak [ 17/May/17 ] |
|
This also happened [4] after make-leader-local (still module-based shards with tell-based protocol), but there is UnreachableMember in karaf.log [5]: , address: akka.tcp://opendaylight-cluster-data@10.29.14.225:2550 [4] https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/693/archives/log.html.gz#s1-s24-t1-k2-k9-k1 |