Abhishek Rawat created IMPALA-12057: ---------------------------------------
Summary: admissiond fails to admit queued queries if coordinator's membership id changes Key: IMPALA-12057 URL: https://issues.apache.org/jira/browse/IMPALA-12057 Project: IMPALA Issue Type: Bug Reporter: Abhishek Rawat If coordinator's subscription id changes (due to a restart or reconnection with statestored), admissiond has no way of knowing if the coordinator was briefly disconnected and is again part of the cluster and has the query state preserved or coordinator got restarted and doesn't know anything about the queued query. Ideally in such cases admissiond should learn from coordinator and statestored that the queued queries are still valid and the subscription id has changed so that admission controller can submit the queued queries. Untill we support that we should at least fail these queries immediately. The current behavior is that admission controller goes into an infinite loop waiting on these queued queries: {code:java} I0411 13:52:22.694419 67 admission-controller.cc:2206] Could not dequeue query id=c748095c589ccfb6:3819937100000000 reason: Coordinator not registered with the statestore. I0411 13:52:22.795398 67 admission-controller.cc:2206] Could not dequeue query id=c748095c589ccfb6:3819937100000000 reason: Coordinator not registered with the statestore. .... I0411 15:14:11.063143 67 admission-controller.cc:2206] Could not dequeue query id=c748095c589ccfb6:3819937100000000 reason: Coordinator not registered with the statestore. I0411 15:14:11.164698 67 admission-controller.cc:2206] Could not dequeue query id=c748095c589ccfb6:3819937100000000 reason: Coordinator not registered with the statestore. {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)