impala-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Balazs Jeszenszky (Code Review)" <>
Subject [Impala-ASF-CR] IMPALA-4704: Disallow client connections to imapalad until catalog is received.
Date Wed, 04 Oct 2017 17:04:20 GMT
Balazs Jeszenszky has posted comments on this change. (

Change subject: IMPALA-4704: Disallow client connections to imapalad until catalog is received.

Patch Set 1:

I think the bug report's title is a better than it's description. In particular, I'm not sure
shutting down the daemon is the best way out of situations like this since in most managed
environments they will be restarted automatically (causing another attempt to get initial
catalog update, same as if they were left alive).
If for some reason opening the ports later is not possible, I think timing out should result
in closing the connection with a more descriptive error message so that clients can retry.

However, the best solution would be to only open the frontend ports after the catalog update
is processed. With a load balancer in front of several coordinators, this setup would allow
for a seamless (i.e. not even a delay due to connections waiting for the catalog update to
be processed) experience for clients.

To view, visit
To unsubscribe, visit

Gerrit-Project: Impala-ASF
Gerrit-Branch: master
Gerrit-MessageType: comment
Gerrit-Change-Id: I52b881cba18a7e4533e21a78751c2e35c3d4c8a6
Gerrit-Change-Number: 8202
Gerrit-PatchSet: 1
Gerrit-Owner: Vuk Ercegovac <>
Gerrit-Reviewer: Balazs Jeszenszky <>
Gerrit-Reviewer: Philip Zeyliger <>
Gerrit-Reviewer: Vuk Ercegovac <>
Gerrit-Comment-Date: Wed, 04 Oct 2017 17:04:20 +0000
Gerrit-HasComments: No

  • Unnamed multipart/alternative (inline, 8-Bit, 0 bytes)
View raw message