Bobby,
What do you mean by client here? In this context, do you consider hdfsbolt
a client? If yes, then which configuration you are referring to? I've seen
the following, but I am not sure if I follow.
- *dfs.client.failover.proxy.provider.[nameservice ID]* - the Java class
that HDFS clients use to contact the Active NameNode
Configure the name of the Java class which will be used by the DFS
Client to determine which NameNode is the current Active, and therefore
which NameNode is currently serving client requests. The only
implementation which currently ships with Hadoop is the
*ConfiguredFailoverProxyProvider*, so use this unless you are using a
custom one. For example:
<property>
<name>dfs.client.failover.proxy.provider.mycluster</name>
<value>org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider</value>
</property>
thanks,
Clay
On Thu, Feb 19, 2015 at 8:38 AM, Bobby Evans <[email protected]>
wrote:
> HDFS HA provides fail-over for the name node and the client determines
> which name node is the active one but should be completely transparent to
> you if the client is configured correctly.
> - Bobby
>
>
> On Thursday, February 19, 2015 6:47 AM, clay teahouse <
> [email protected]> wrote:
>
>
> Hi All,
> Has anyone used HdfsBolt with hdfs in HA mode? How would you determine
> which hdfs node is the active node?
>
> thanks
> Clay
>
>
>
>
