Wenzhe Zhou has submitted this change and it was merged. ( 
http://gerrit.cloudera.org:8080/21051 )

Change subject: IMPALA-12833: Enabled 'catalogd_ha_reset_metadata_on_failover' 
by default
......................................................................

IMPALA-12833: Enabled 'catalogd_ha_reset_metadata_on_failover' by default

The standby catalogd may have stale metadata for some reason, like
event processor could have hung or could be just behind in processing
events. Also the standby catalogd doesn't get invalidate requests from
coordinators so we should probably reset its metadata when it becomes
active to avoid stale metadata.

This patch set the default value of catalog server starting flag
'catalogd_ha_reset_metadata_on_failover' as true so that catalogd
will reset its metadata when it becomes active. Also makes the flag
as hidden option.

Testing:
 - Looped to run unit-tests for catalog HA and statestore HA without
   failure.
 - Passed core tests

Change-Id: Ibc7c529f34b70734a700ac0d9d58b7e5b0215f8d
Reviewed-on: http://gerrit.cloudera.org:8080/21051
Tested-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Michael Smith <[email protected]>
Reviewed-by: Abhishek Rawat <[email protected]>
---
M be/src/catalog/catalog-server.cc
M tests/custom_cluster/test_catalogd_ha.py
2 files changed, 10 insertions(+), 2 deletions(-)

Approvals:
  Impala Public Jenkins: Verified
  Michael Smith: Looks good to me, but someone else must approve
  Abhishek Rawat: Looks good to me, approved

--
To view, visit http://gerrit.cloudera.org:8080/21051
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-Project: Impala-ASF
Gerrit-Branch: master
Gerrit-MessageType: merged
Gerrit-Change-Id: Ibc7c529f34b70734a700ac0d9d58b7e5b0215f8d
Gerrit-Change-Number: 21051
Gerrit-PatchSet: 4
Gerrit-Owner: Wenzhe Zhou <[email protected]>
Gerrit-Reviewer: Abhishek Rawat <[email protected]>
Gerrit-Reviewer: Impala Public Jenkins <[email protected]>
Gerrit-Reviewer: Michael Smith <[email protected]>
Gerrit-Reviewer: Wenzhe Zhou <[email protected]>

Reply via email to