hadoop-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harsh J <ha...@cloudera.com>
Subject Re: rack topology data update
Date Fri, 14 Sep 2012 04:28:07 GMT
Jameson,

Yes unfortunately this is the current case.

On Fri, Sep 14, 2012 at 8:58 AM, Jameson Li <hovlj.ei@gmail.com> wrote:
> Harsh J,
>
> If a new datanode has joined the cluster, and has a default rack info cached
> in the namenode, it will no way to change its cache other than restart the
> namenode.
> Am I right?
>
> 专注于Mysql,MSSQL,Oracle,Hadoop
>
>
>
> 2012/9/13 Harsh J <harsh@cloudera.com>
>>
>> Hey Steve,
>>
>> True about the decisions part, that still needs the ugly fixing of
>> re-replication.
>>
>> I think I saw it on a JIRA by Patrick A. that was trying to change the
>> way we did this. But placement is also pluggable in 2.x right? Let me
>> find that JIRA (but yeah, am unsure if it was committed).
>>
>> On Thu, Sep 13, 2012 at 2:40 PM, Steve Loughran <stevel@hortonworks.com>
>> wrote:
>> >
>> >
>> > On 13 September 2012 09:03, Harsh J <harsh@cloudera.com> wrote:
>> >>
>> >>
>> >> This should be fixed in one of the 2.x releases, where we also refresh
>> >> the cached values.
>> >>
>> >
>> > Really? Which JIRA?
>> >
>> > I've been making changes to the topology logic so you can do some
>> > preflight
>> > checking and dump the topologies, but didn't think a clear and reload
>> > was in
>> > there. Some decisions on block placement strategy (flat vs hierarchical)
>> > are
>> > made early on, so going from flat to multi-switch is not something I'd
>> > recommend.
>>
>>
>>
>> --
>> Harsh J
>
>



-- 
Harsh J

Mime
View raw message