There is an issue with Master::register_server; this
methods assigns a location if not already assigned, the assigned
location always starts with "rs" (rs1, rs2, ...). This assignment
makes troubles
if a client (one process) connects (not via thrift) to more than one
hypertable
instance for which the proxy names for the range servers have not been
explicitly
defined (via hypertable.cfg). As a result the client proxy map gets
mixed up.
As a workaround I have changed the location assignment for the Windows
version to:
location = (!System::net_info().host_name.empty() ?
System::net_info().host_name : String("rs")) + m_next_server_id++;
it uses the master host name as prefix.
Does this have any negative side effects?
Is this a change which could find the way into the main branch?
-Andy
--
You received this message because you are subscribed to the Google Groups
"Hypertable Development" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/hypertable-dev?hl=en.
