[
https://issues.apache.org/jira/browse/KUDU-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-356.
------------------------------
Resolution: Cannot Reproduce
Fix Version/s: n/a
Tried to repro this on a recent build and no longer see the FATAL described
here (should hope not, 3 years later)
> Creating a table after reformatting a TS kills the TS
> -----------------------------------------------------
>
> Key: KUDU-356
> URL: https://issues.apache.org/jira/browse/KUDU-356
> Project: Kudu
> Issue Type: Bug
> Components: master, tserver
> Affects Versions: M4
> Reporter: Todd Lipcon
> Priority: Minor
> Labels: newbie
> Fix For: n/a
>
>
> Steps to repro:
> - Start a master and TS
> - shut down the TS, rm -Rf its data dir, and start the TS again on the same
> RPC port
> - create a table
> The master then has a 50% chance of sending a "create tablet" request
> thinking it's going to the _old_ TS, so it will include a quorum with the old
> TS's permanent UUID. The new TS will then see this and trigger a CHECK
> failure in ts_tablet_manager:
> F0617 11:47:30.864171 1857 ts_tablet_manager.cc:164] Check failed:
> server_->instance_pb().permanent_uuid() == quorum.peers(0).permanent_uuid()
> (97cb01e6c96c46f98319d2d3c8884884 vs. daa1284ffb374a2a8b36a6ead695d011)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
