On Thu, Aug 13, 2015 at 3:11 PM, Josh Elser <[email protected]> wrote:
> Keith Turner wrote: > >> On Thu, Aug 13, 2015 at 12:03 PM, Josh Elser<[email protected]> >> wrote: >> >> > Yes, I omitted the session ID intentionally due to confusion of "what >>> the >>> > heck is that random string". I thought I had mentioned that there is a >>> > uniqueness string on there to identify instances of servers on the >>> same >>> > host and port, but maybe I dropped that out in the end. >>> > >>> > Ultimately, it's not really relevant for the assignment discussion, >>> > assignment just cares about a unique instance of a server. I'll see >>> if I >>> > can maybe clarify that. >>> > >>> > >>> >> Its important in that its used to know when a future or current location >> is >> a dead tserver and needs to be reassigned. >> >> >> > Yes, the uniqueness of identifying a server is important. The details in > how we achieve uniqueness is irrelevant for the discussion, IMO. > I agree, it doesn't matter what it is. Does not have to be ZK session ID. IMO it makes the design doc more clear if it always uses <server>:<port>:<tsiid> when needed and explains why the tsiid is needed.
