but I saw something in your log that was easy to lookup in the code.
>
> -Ray
>
>
> On Thu, Dec 4, 2014 at 8:17 PM, mail list wrote:
> Hi ,Ray
>
> How can I know the standby name node become active and done the recovery job
> and can work in log?
> Is there som
Hi ,Ray
How can I know the standby name node become active and done the recovery job
and can work in log?
Is there some obvious mark in name node log?
On Dec 5, 2014, at 9:55, mail list wrote:
> Thanks Ray, I will try this options.
>
> On Dec 5, 2014, at 5:50, Ray Chiang wrote:
27;m not certain if that will affect other services besides HDFS.
>
> -Ray
>
>
> On Wed, Dec 3, 2014 at 2:51 AM, mail list wrote:
> hadoop-2.3.0-cdh5.1.0
>
> hi, i move QJM from the l-hbase1.dba.dev.cn0 to another machine, and the
> down time reduced to
> 5 mins, an
org.apache.hadoop.hdfs.server.blockmanagement.CacheReplicationMonitor,
what is hadoop doing? how can i reduce the time cause 5 mins is too long!
On Dec 3, 2014, at 16:31, Harsh J wrote:
> What is your Hadoop version?
>
> On Wed, Dec 3, 2014 at 12:55 PM, mail list wrote:
>> hi all,
>>
>> Attach log
Hi,all
we are testing QJM NAMENODE HA, and when the active name node down,it cost
about 5 mins to work normal.
Log on the standby name node as below:
{log}
014-12-03 15:55:51,307 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Will take over writing
edit logs at txnid 6797
2014-12-
Hi all,
I deploy the hadoop with 3 machines:
l-hbase1.dba.dev.cn0 (namenode active and QJM)
l-hbase2.dba.dev.cn0 (namenode standby and datanode and QJM)
l-hbase3.dba.dev.cn0 (datanode and QJM)
Above the hadoop, i deploy a hbase:
l-hbase1.dba.dev.cn0 (HMaster active)
l-hbase2.dba.dev.cn0 (HMaster
Hi,
please attach your log when the problem happened!!
On Nov 28, 2014, at 14:32, 聪聪 <175998...@qq.com> wrote:
> hi,there:
> I encount a problem,it let me upset.
>
> I use version of hadoop is hadoop-2.3.0-cdh5.1.0,namenode HA use the Quorum
> Journal Manager (QJM) feature ,dfs.ha.fencing.met
hi, all
I am using the name node HA feature(zkfc), and there is a configuration:
ha.health-monitor.rpc-timeout.ms,
There are two situation:
1. Active name node is down
if the zkfc will wait ha.health-monitor.rpc-timeout.ms, then call the failover
? Or not wait?
2. Active name node is too busy
hi all,
We are testing the zkfc for name node HA. And I see the design of the zkfc,
there is a monitor thread which will monitor the healthy of name node and the
design
mention that the RPC timeout option, i want to know how to configure this
option and
if the option is used just used when the
hi todd,
Recently we use the QJM for HA, and i read the zkfc_design. I have a
question,
IMO, each zkfc hold a connection to zookeeper with an ephemeral node,
And i worry about the network between zkfc and zookeeper node
is not very stable(lost at a moment and recovery soon), whic
tion, or dissemination)
> by persons other than the intended recipient(s) is prohibited. If you receive
> this e-mail in error, please notify the sender by phone or email immediately
> and delete it!
>
> From: mail list [mailto:louis.hust...@gmail.com]
> Sent: 23 October 201
11 matches
Mail list logo