Alexey Serbin has uploaded this change for review. (
http://gerrit.cloudera.org:8080/15261
Change subject: [master] call Shutdown() in destructor
......................................................................
[master] call Shutdown() in destructor
Master was reported crashing in tests with stack like below when
catalog manager failed to initialize:
F0220 11:54:37.240003 1700 master.cc:128] Check failed: kRunning != state_
(2 vs. 2)
*** Check failure stack trace: ***
@ 0x7ff77ba68202 google::LogMessage::Flush()
@ 0x7ff77ba6c93b google::LogMessageFatal::~LogMessageFatal()
@ 0x7ff7876ed9ac kudu::master::Master::~Master()
@ 0x7ff78770f797 kudu::master::RunMasterServer()
@ 0x4dd00f kudu::master::MasterMain()
I took a quick look into the code and if my understanding is correct,
nothing prevents us calling Shutdown() in destructor, like TabletServer
does.
This patch updates Master's destructor to call Shutdown() to avoid
unneeded crashes like above and unify the behavior of Master and
TabletServer objects.
Change-Id: Icc3c5d0b183175ec6a5f288a30fb8a24bd983962
---
M src/kudu/master/master.cc
1 file changed, 2 insertions(+), 2 deletions(-)
git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/61/15261/1
--
To view, visit http://gerrit.cloudera.org:8080/15261
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-MessageType: newchange
Gerrit-Change-Id: Icc3c5d0b183175ec6a5f288a30fb8a24bd983962
Gerrit-Change-Number: 15261
Gerrit-PatchSet: 1
Gerrit-Owner: Alexey Serbin <[email protected]>
