Major Description
Encountered while doing ingest with agitation-
n3 has the root tablet
1:41 - n2 dies, had sessionId 14a5b2f992e0322
1:42 - n2 comes back up, new session id 14a5b2f992e03aa
2:01 - n3 dies
2:03 - master assigns root tablet to n2, but with sessionId 14a5b2f992e0322
cluster is stuck because root tablet repeatedly fails attempts to issue reload, tablet never gets reassigned to a new server or the same server with the correct sessionId
Bouncing the master resolved this
