[NETCONF-220] Getting content from cluster from the second follower causes an "AskTimeoutException" Created: 15/Jun/16 Updated: 15/Mar/19 Resolved: 24/Oct/16 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Ernest Deák | Assignee: | Rudolf Brisuda |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 6067 |
| Description |
|
Attempting to fetch data from the second follower in a 3-node cluster when original owner is down, causes a java exception to be returned in the response text: <errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"><error><error-type>application</error-type><error-tag>operation-failed</error-tag><error-message>Problem to get data from transaction.</error-message><error-info>akka.pattern.AskTimeoutException: Ask timed out on [Actor[akka.tcp://opendaylight-cluster-data@10.29.11.243:2550/user/topology-netconf/netconf-test-device/mountpoint#1234942408]] after [5000 ms] The response code returned is 500. The request is successful when the first follower (the new owner) is querried Sandbox test results: https://jenkins.opendaylight.org/sandbox/job/netconf-csit-3node-clustering-only-beryllium/3/ Test to look for is in "Entity" suite under the name "Check_Config_Data_Before_Modification_With_Original_Owner_Down" |
| Comments |
| Comment by Jakub Morvay [ 16/Jun/16 ] |
|
Hi Ernest, This can be another symptom of |
| Comment by Rudolf Brisuda [ 05/Sep/16 ] |
|
I am unable to reproduce. At both nodes I got 200 OK with inserted data. |
| Comment by Vratko Polak [ 10/Oct/16 ] |
|
This is still happening frequently in CSIT. Recent Boron example: Created data is seen on a follower (member-1) [0], but after entity owner (member-2) is killed, data is seen as empty [1]. Compared to the original description, there is no AskTimeoutException visible in the follower karaf.log but there are several warnings visible on the new owner (member-3) karaf.log [2] during the critical 26th minute. [0] https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-boron/263/archives/log.html.gz#s1-s4-t7-k2-k1-k2 |
| Comment by Rudolf Brisuda [ 24/Oct/16 ] |
|
No longer relevant due to rewriting netconf topology clustering. If problem persists then this bug has different cause and it is not useful. There should be created new bug with proper state. |