kudu-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pavel Martynov <mr.xk...@gmail.com>
Subject Re: Renaming hostname of tserver/master
Date Mon, 05 Feb 2018 15:52:09 GMT
Hi Todd,

My cluster still in preproduction state, so I just drop all data/metadata.
My team will try to use Kudu on production with a 20-40 TB of data, so I
will be happy to see any closed tickets about operation stuff in next
releases :).

2018-02-05 7:07 GMT+03:00 Todd Lipcon <todd@cloudera.com>:

> Hey Pavel,
> Did you find a workaround for this? As you found it's not something we
> support easily today, because each server will "remember" the old host
> names of all of its replication peers within its consensus metadata, and
> continue to try to talk to them after a restart. Renaming hosts would
> involve writing the consensus metadata files on all of the servers with the
> updated names.
> We're soon facing this same issue with one of the test clusters at
> Cloudera, so I'm guessing we'll have to write some kind of tool to get it
> back online as well :) Would be curious to hear what approach you took.
> -Todd
> On Tue, Jan 30, 2018 at 11:08 PM, Pavel Martynov <mr.xkurt@gmail.com>
> wrote:
>> Ok, I found ticket https://issues.apache.org/jira/browse/KUDU-418, which
>> fired at me.
> --
> Todd Lipcon
> Software Engineer, Cloudera

with best regards, Pavel Martynov

View raw message