You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-user@hadoop.apache.org by ch huang <ju...@gmail.com> on 2013/07/26 09:04:48 UTC
two name node both in standby state?why?
i have no idea,why?
2013-07-26 22:55:30,772 INFO org.apache.hadoop.http.HttpServer: Jetty bound
to port 50070
2013-07-26 22:55:30,772 INFO org.mortbay.log: jetty-6.1.26.cloudera.2
2013-07-26 22:55:31,001 WARN
org.apache.hadoop.security.authentication.server.AuthenticationFilter:
'signature.secret' configuration not set, using a random value as secret
2013-07-26 22:55:31,054 INFO org.mortbay.log: Started
SelectChannelConnector@node1:50070
2013-07-26 22:55:31,054 INFO
org.apache.hadoop.hdfs.server.namenode.NameNode: Web-server up at:
node1:50070
2013-07-26 22:55:31,057 INFO org.apache.hadoop.ipc.Server: IPC Server
Responder: starting
2013-07-26 22:55:31,058 INFO org.apache.hadoop.ipc.Server: IPC Server
listener on 8020: starting
2013-07-26 22:55:31,072 INFO
org.apache.hadoop.hdfs.server.namenode.NameNode: NameNode up at: node1/
192.168.142.129:8020
2013-07-26 22:55:31,072 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Starting services
required for standby state
2013-07-26 22:55:31,074 INFO
org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Will roll logs on
active node at node2/192.168.142.130:8020 every 120 seconds.
2013-07-26 22:55:31,084 INFO
org.apache.hadoop.hdfs.server.namenode.ha.StandbyCheckpointer: Starting
standby checkpoint thread...
Checkpointing active NN at node2:50070
Serving checkpoints at node1/192.168.142.129:50070
2013-07-26 22:57:31,112 INFO
org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Triggering log
roll on remote NameNode node2/192.168.142.130:8020
2013-07-26 22:57:31,329 WARN
org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Unable to trigger
a roll of the active NN
org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
Operation category JOURNAL is not supported in state standby
at
org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
at
org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1401)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:871)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.rollEditLog(FSNamesystem.java:4577)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.rollEditLog(NameNodeRpcServer.java:756)
at
org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolServerSideTranslatorPB.rollEditLog(NamenodeProtocolServerSideTranslatorPB.java:129)
at
org.apache.hadoop.hdfs.protocol.proto.NamenodeProtocolProtos$NamenodeProtocolService$2.callBlockingMethod(NamenodeProtocolProtos.java:8762)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1701)
Re: two name node both in standby state?why?
Posted by Venkatarami Netla <ve...@cloudwick.com>.
sudo -u hdfs hdfs haadmin -failover --forceactive nn1 nn2
run this to make one is active
Thanks & Regards
Venkatram
On Fri, Jul 26, 2013 at 1:04 PM, ch huang <ju...@gmail.com> wrote:
> but i have not set autofailover,the ZKFC is really need for manual
> failover switch?
>
>
> On Fri, Jul 26, 2013 at 3:22 PM, Bing Jiang <ji...@gmail.com>wrote:
>
>> Please check whether the process of DFSZKFailoverController is open or
>> not, and each namenode should be attached with a DFSZKFailoverController.
>>
>>
>> 2013/7/26 ch huang <ju...@gmail.com>
>>
>>> i have no idea,why?
>>>
>>> 2013-07-26 22:55:30,772 INFO org.apache.hadoop.http.HttpServer: Jetty
>>> bound to port 50070
>>> 2013-07-26 22:55:30,772 INFO org.mortbay.log: jetty-6.1.26.cloudera.2
>>> 2013-07-26 22:55:31,001 WARN
>>> org.apache.hadoop.security.authentication.server.AuthenticationFilter:
>>> 'signature.secret' configuration not set, using a random value as secret
>>> 2013-07-26 22:55:31,054 INFO org.mortbay.log: Started
>>> SelectChannelConnector@node1:50070
>>> 2013-07-26 22:55:31,054 INFO
>>> org.apache.hadoop.hdfs.server.namenode.NameNode: Web-server up at:
>>> node1:50070
>>> 2013-07-26 22:55:31,057 INFO org.apache.hadoop.ipc.Server: IPC Server
>>> Responder: starting
>>> 2013-07-26 22:55:31,058 INFO org.apache.hadoop.ipc.Server: IPC Server
>>> listener on 8020: starting
>>> 2013-07-26 22:55:31,072 INFO
>>> org.apache.hadoop.hdfs.server.namenode.NameNode: NameNode up at: node1/
>>> 192.168.142.129:8020
>>> 2013-07-26 22:55:31,072 INFO
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Starting services
>>> required for standby state
>>> 2013-07-26 22:55:31,074 INFO
>>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Will roll logs on
>>> active node at node2/192.168.142.130:8020 every 120 seconds.
>>> 2013-07-26 22:55:31,084 INFO
>>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyCheckpointer: Starting
>>> standby checkpoint thread...
>>> Checkpointing active NN at node2:50070
>>> Serving checkpoints at node1/192.168.142.129:50070
>>> 2013-07-26 22:57:31,112 INFO
>>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Triggering log
>>> roll on remote NameNode node2/192.168.142.130:8020
>>> 2013-07-26 22:57:31,329 WARN
>>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Unable to trigger
>>> a roll of the active NN
>>> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
>>> Operation category JOURNAL is not supported in state standby
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1401)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:871)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.rollEditLog(FSNamesystem.java:4577)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.rollEditLog(NameNodeRpcServer.java:756)
>>> at
>>> org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolServerSideTranslatorPB.rollEditLog(NamenodeProtocolServerSideTranslatorPB.java:129)
>>> at
>>> org.apache.hadoop.hdfs.protocol.proto.NamenodeProtocolProtos$NamenodeProtocolService$2.callBlockingMethod(NamenodeProtocolProtos.java:8762)
>>> at
>>> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
>>> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
>>> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1701)
>>>
>>
>>
>>
>> --
>> Bing Jiang
>> Tel：(86)134-2619-1361
>> weibo: http://weibo.com/jiangbinglover
>> BLOG: www.binospace.com
>> BLOG: http://blog.sina.com.cn/jiangbinglover
>> Focus on distributed computing, HDFS/HBase
>>
>
>
--
N Venkata Rami Reddy
Hadoop Admin
Cloudwick Technologies
Re: two name node both in standby state?why?
Posted by Venkatarami Netla <ve...@cloudwick.com>.
sudo -u hdfs hdfs haadmin -failover --forceactive nn1 nn2
run this to make one is active
Thanks & Regards
Venkatram
On Fri, Jul 26, 2013 at 1:04 PM, ch huang <ju...@gmail.com> wrote:
> but i have not set autofailover,the ZKFC is really need for manual
> failover switch?
>
>
> On Fri, Jul 26, 2013 at 3:22 PM, Bing Jiang <ji...@gmail.com>wrote:
>
>> Please check whether the process of DFSZKFailoverController is open or
>> not, and each namenode should be attached with a DFSZKFailoverController.
>>
>>
>> 2013/7/26 ch huang <ju...@gmail.com>
>>
>>> i have no idea,why?
>>>
>>> 2013-07-26 22:55:30,772 INFO org.apache.hadoop.http.HttpServer: Jetty
>>> bound to port 50070
>>> 2013-07-26 22:55:30,772 INFO org.mortbay.log: jetty-6.1.26.cloudera.2
>>> 2013-07-26 22:55:31,001 WARN
>>> org.apache.hadoop.security.authentication.server.AuthenticationFilter:
>>> 'signature.secret' configuration not set, using a random value as secret
>>> 2013-07-26 22:55:31,054 INFO org.mortbay.log: Started
>>> SelectChannelConnector@node1:50070
>>> 2013-07-26 22:55:31,054 INFO
>>> org.apache.hadoop.hdfs.server.namenode.NameNode: Web-server up at:
>>> node1:50070
>>> 2013-07-26 22:55:31,057 INFO org.apache.hadoop.ipc.Server: IPC Server
>>> Responder: starting
>>> 2013-07-26 22:55:31,058 INFO org.apache.hadoop.ipc.Server: IPC Server
>>> listener on 8020: starting
>>> 2013-07-26 22:55:31,072 INFO
>>> org.apache.hadoop.hdfs.server.namenode.NameNode: NameNode up at: node1/
>>> 192.168.142.129:8020
>>> 2013-07-26 22:55:31,072 INFO
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Starting services
>>> required for standby state
>>> 2013-07-26 22:55:31,074 INFO
>>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Will roll logs on
>>> active node at node2/192.168.142.130:8020 every 120 seconds.
>>> 2013-07-26 22:55:31,084 INFO
>>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyCheckpointer: Starting
>>> standby checkpoint thread...
>>> Checkpointing active NN at node2:50070
>>> Serving checkpoints at node1/192.168.142.129:50070
>>> 2013-07-26 22:57:31,112 INFO
>>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Triggering log
>>> roll on remote NameNode node2/192.168.142.130:8020
>>> 2013-07-26 22:57:31,329 WARN
>>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Unable to trigger
>>> a roll of the active NN
>>> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
>>> Operation category JOURNAL is not supported in state standby
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1401)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:871)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.rollEditLog(FSNamesystem.java:4577)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.rollEditLog(NameNodeRpcServer.java:756)
>>> at
>>> org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolServerSideTranslatorPB.rollEditLog(NamenodeProtocolServerSideTranslatorPB.java:129)
>>> at
>>> org.apache.hadoop.hdfs.protocol.proto.NamenodeProtocolProtos$NamenodeProtocolService$2.callBlockingMethod(NamenodeProtocolProtos.java:8762)
>>> at
>>> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
>>> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
>>> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1701)
>>>
>>
>>
>>
>> --
>> Bing Jiang
>> Tel：(86)134-2619-1361
>> weibo: http://weibo.com/jiangbinglover
>> BLOG: www.binospace.com
>> BLOG: http://blog.sina.com.cn/jiangbinglover
>> Focus on distributed computing, HDFS/HBase
>>
>
>
--
N Venkata Rami Reddy
Hadoop Admin
Cloudwick Technologies
Re: two name node both in standby state?why?
Posted by Venkatarami Netla <ve...@cloudwick.com>.
sudo -u hdfs hdfs haadmin -failover --forceactive nn1 nn2
run this to make one is active
Thanks & Regards
Venkatram
On Fri, Jul 26, 2013 at 1:04 PM, ch huang <ju...@gmail.com> wrote:
> but i have not set autofailover,the ZKFC is really need for manual
> failover switch?
>
>
> On Fri, Jul 26, 2013 at 3:22 PM, Bing Jiang <ji...@gmail.com>wrote:
>
>> Please check whether the process of DFSZKFailoverController is open or
>> not, and each namenode should be attached with a DFSZKFailoverController.
>>
>>
>> 2013/7/26 ch huang <ju...@gmail.com>
>>
>>> i have no idea,why?
>>>
>>> 2013-07-26 22:55:30,772 INFO org.apache.hadoop.http.HttpServer: Jetty
>>> bound to port 50070
>>> 2013-07-26 22:55:30,772 INFO org.mortbay.log: jetty-6.1.26.cloudera.2
>>> 2013-07-26 22:55:31,001 WARN
>>> org.apache.hadoop.security.authentication.server.AuthenticationFilter:
>>> 'signature.secret' configuration not set, using a random value as secret
>>> 2013-07-26 22:55:31,054 INFO org.mortbay.log: Started
>>> SelectChannelConnector@node1:50070
>>> 2013-07-26 22:55:31,054 INFO
>>> org.apache.hadoop.hdfs.server.namenode.NameNode: Web-server up at:
>>> node1:50070
>>> 2013-07-26 22:55:31,057 INFO org.apache.hadoop.ipc.Server: IPC Server
>>> Responder: starting
>>> 2013-07-26 22:55:31,058 INFO org.apache.hadoop.ipc.Server: IPC Server
>>> listener on 8020: starting
>>> 2013-07-26 22:55:31,072 INFO
>>> org.apache.hadoop.hdfs.server.namenode.NameNode: NameNode up at: node1/
>>> 192.168.142.129:8020
>>> 2013-07-26 22:55:31,072 INFO
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Starting services
>>> required for standby state
>>> 2013-07-26 22:55:31,074 INFO
>>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Will roll logs on
>>> active node at node2/192.168.142.130:8020 every 120 seconds.
>>> 2013-07-26 22:55:31,084 INFO
>>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyCheckpointer: Starting
>>> standby checkpoint thread...
>>> Checkpointing active NN at node2:50070
>>> Serving checkpoints at node1/192.168.142.129:50070
>>> 2013-07-26 22:57:31,112 INFO
>>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Triggering log
>>> roll on remote NameNode node2/192.168.142.130:8020
>>> 2013-07-26 22:57:31,329 WARN
>>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Unable to trigger
>>> a roll of the active NN
>>> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
>>> Operation category JOURNAL is not supported in state standby
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1401)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:871)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.rollEditLog(FSNamesystem.java:4577)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.rollEditLog(NameNodeRpcServer.java:756)
>>> at
>>> org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolServerSideTranslatorPB.rollEditLog(NamenodeProtocolServerSideTranslatorPB.java:129)
>>> at
>>> org.apache.hadoop.hdfs.protocol.proto.NamenodeProtocolProtos$NamenodeProtocolService$2.callBlockingMethod(NamenodeProtocolProtos.java:8762)
>>> at
>>> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
>>> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
>>> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1701)
>>>
>>
>>
>>
>> --
>> Bing Jiang
>> Tel：(86)134-2619-1361
>> weibo: http://weibo.com/jiangbinglover
>> BLOG: www.binospace.com
>> BLOG: http://blog.sina.com.cn/jiangbinglover
>> Focus on distributed computing, HDFS/HBase
>>
>
>
--
N Venkata Rami Reddy
Hadoop Admin
Cloudwick Technologies
Re: two name node both in standby state?why?
Posted by Venkatarami Netla <ve...@cloudwick.com>.
sudo -u hdfs hdfs haadmin -failover --forceactive nn1 nn2
run this to make one is active
Thanks & Regards
Venkatram
On Fri, Jul 26, 2013 at 1:04 PM, ch huang <ju...@gmail.com> wrote:
> but i have not set autofailover,the ZKFC is really need for manual
> failover switch?
>
>
> On Fri, Jul 26, 2013 at 3:22 PM, Bing Jiang <ji...@gmail.com>wrote:
>
>> Please check whether the process of DFSZKFailoverController is open or
>> not, and each namenode should be attached with a DFSZKFailoverController.
>>
>>
>> 2013/7/26 ch huang <ju...@gmail.com>
>>
>>> i have no idea,why?
>>>
>>> 2013-07-26 22:55:30,772 INFO org.apache.hadoop.http.HttpServer: Jetty
>>> bound to port 50070
>>> 2013-07-26 22:55:30,772 INFO org.mortbay.log: jetty-6.1.26.cloudera.2
>>> 2013-07-26 22:55:31,001 WARN
>>> org.apache.hadoop.security.authentication.server.AuthenticationFilter:
>>> 'signature.secret' configuration not set, using a random value as secret
>>> 2013-07-26 22:55:31,054 INFO org.mortbay.log: Started
>>> SelectChannelConnector@node1:50070
>>> 2013-07-26 22:55:31,054 INFO
>>> org.apache.hadoop.hdfs.server.namenode.NameNode: Web-server up at:
>>> node1:50070
>>> 2013-07-26 22:55:31,057 INFO org.apache.hadoop.ipc.Server: IPC Server
>>> Responder: starting
>>> 2013-07-26 22:55:31,058 INFO org.apache.hadoop.ipc.Server: IPC Server
>>> listener on 8020: starting
>>> 2013-07-26 22:55:31,072 INFO
>>> org.apache.hadoop.hdfs.server.namenode.NameNode: NameNode up at: node1/
>>> 192.168.142.129:8020
>>> 2013-07-26 22:55:31,072 INFO
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Starting services
>>> required for standby state
>>> 2013-07-26 22:55:31,074 INFO
>>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Will roll logs on
>>> active node at node2/192.168.142.130:8020 every 120 seconds.
>>> 2013-07-26 22:55:31,084 INFO
>>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyCheckpointer: Starting
>>> standby checkpoint thread...
>>> Checkpointing active NN at node2:50070
>>> Serving checkpoints at node1/192.168.142.129:50070
>>> 2013-07-26 22:57:31,112 INFO
>>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Triggering log
>>> roll on remote NameNode node2/192.168.142.130:8020
>>> 2013-07-26 22:57:31,329 WARN
>>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Unable to trigger
>>> a roll of the active NN
>>> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
>>> Operation category JOURNAL is not supported in state standby
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1401)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:871)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.rollEditLog(FSNamesystem.java:4577)
>>> at
>>> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.rollEditLog(NameNodeRpcServer.java:756)
>>> at
>>> org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolServerSideTranslatorPB.rollEditLog(NamenodeProtocolServerSideTranslatorPB.java:129)
>>> at
>>> org.apache.hadoop.hdfs.protocol.proto.NamenodeProtocolProtos$NamenodeProtocolService$2.callBlockingMethod(NamenodeProtocolProtos.java:8762)
>>> at
>>> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
>>> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
>>> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1701)
>>>
>>
>>
>>
>> --
>> Bing Jiang
>> Tel：(86)134-2619-1361
>> weibo: http://weibo.com/jiangbinglover
>> BLOG: www.binospace.com
>> BLOG: http://blog.sina.com.cn/jiangbinglover
>> Focus on distributed computing, HDFS/HBase
>>
>
>
--
N Venkata Rami Reddy
Hadoop Admin
Cloudwick Technologies
Re: two name node both in standby state?why?
Posted by ch huang <ju...@gmail.com>.
but i have not set autofailover,the ZKFC is really need for manual failover
switch?
On Fri, Jul 26, 2013 at 3:22 PM, Bing Jiang <ji...@gmail.com>wrote:
> Please check whether the process of DFSZKFailoverController is open or
> not, and each namenode should be attached with a DFSZKFailoverController.
>
>
> 2013/7/26 ch huang <ju...@gmail.com>
>
>> i have no idea,why?
>>
>> 2013-07-26 22:55:30,772 INFO org.apache.hadoop.http.HttpServer: Jetty
>> bound to port 50070
>> 2013-07-26 22:55:30,772 INFO org.mortbay.log: jetty-6.1.26.cloudera.2
>> 2013-07-26 22:55:31,001 WARN
>> org.apache.hadoop.security.authentication.server.AuthenticationFilter:
>> 'signature.secret' configuration not set, using a random value as secret
>> 2013-07-26 22:55:31,054 INFO org.mortbay.log: Started
>> SelectChannelConnector@node1:50070
>> 2013-07-26 22:55:31,054 INFO
>> org.apache.hadoop.hdfs.server.namenode.NameNode: Web-server up at:
>> node1:50070
>> 2013-07-26 22:55:31,057 INFO org.apache.hadoop.ipc.Server: IPC Server
>> Responder: starting
>> 2013-07-26 22:55:31,058 INFO org.apache.hadoop.ipc.Server: IPC Server
>> listener on 8020: starting
>> 2013-07-26 22:55:31,072 INFO
>> org.apache.hadoop.hdfs.server.namenode.NameNode: NameNode up at: node1/
>> 192.168.142.129:8020
>> 2013-07-26 22:55:31,072 INFO
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Starting services
>> required for standby state
>> 2013-07-26 22:55:31,074 INFO
>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Will roll logs on
>> active node at node2/192.168.142.130:8020 every 120 seconds.
>> 2013-07-26 22:55:31,084 INFO
>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyCheckpointer: Starting
>> standby checkpoint thread...
>> Checkpointing active NN at node2:50070
>> Serving checkpoints at node1/192.168.142.129:50070
>> 2013-07-26 22:57:31,112 INFO
>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Triggering log
>> roll on remote NameNode node2/192.168.142.130:8020
>> 2013-07-26 22:57:31,329 WARN
>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Unable to trigger
>> a roll of the active NN
>> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
>> Operation category JOURNAL is not supported in state standby
>> at
>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1401)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:871)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.rollEditLog(FSNamesystem.java:4577)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.rollEditLog(NameNodeRpcServer.java:756)
>> at
>> org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolServerSideTranslatorPB.rollEditLog(NamenodeProtocolServerSideTranslatorPB.java:129)
>> at
>> org.apache.hadoop.hdfs.protocol.proto.NamenodeProtocolProtos$NamenodeProtocolService$2.callBlockingMethod(NamenodeProtocolProtos.java:8762)
>> at
>> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
>> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
>> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1701)
>>
>
>
>
> --
> Bing Jiang
> Tel：(86)134-2619-1361
> weibo: http://weibo.com/jiangbinglover
> BLOG: www.binospace.com
> BLOG: http://blog.sina.com.cn/jiangbinglover
> Focus on distributed computing, HDFS/HBase
>
Re: two name node both in standby state?why?
Posted by ch huang <ju...@gmail.com>.
but i have not set autofailover,the ZKFC is really need for manual failover
switch?
On Fri, Jul 26, 2013 at 3:22 PM, Bing Jiang <ji...@gmail.com>wrote:
> Please check whether the process of DFSZKFailoverController is open or
> not, and each namenode should be attached with a DFSZKFailoverController.
>
>
> 2013/7/26 ch huang <ju...@gmail.com>
>
>> i have no idea,why?
>>
>> 2013-07-26 22:55:30,772 INFO org.apache.hadoop.http.HttpServer: Jetty
>> bound to port 50070
>> 2013-07-26 22:55:30,772 INFO org.mortbay.log: jetty-6.1.26.cloudera.2
>> 2013-07-26 22:55:31,001 WARN
>> org.apache.hadoop.security.authentication.server.AuthenticationFilter:
>> 'signature.secret' configuration not set, using a random value as secret
>> 2013-07-26 22:55:31,054 INFO org.mortbay.log: Started
>> SelectChannelConnector@node1:50070
>> 2013-07-26 22:55:31,054 INFO
>> org.apache.hadoop.hdfs.server.namenode.NameNode: Web-server up at:
>> node1:50070
>> 2013-07-26 22:55:31,057 INFO org.apache.hadoop.ipc.Server: IPC Server
>> Responder: starting
>> 2013-07-26 22:55:31,058 INFO org.apache.hadoop.ipc.Server: IPC Server
>> listener on 8020: starting
>> 2013-07-26 22:55:31,072 INFO
>> org.apache.hadoop.hdfs.server.namenode.NameNode: NameNode up at: node1/
>> 192.168.142.129:8020
>> 2013-07-26 22:55:31,072 INFO
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Starting services
>> required for standby state
>> 2013-07-26 22:55:31,074 INFO
>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Will roll logs on
>> active node at node2/192.168.142.130:8020 every 120 seconds.
>> 2013-07-26 22:55:31,084 INFO
>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyCheckpointer: Starting
>> standby checkpoint thread...
>> Checkpointing active NN at node2:50070
>> Serving checkpoints at node1/192.168.142.129:50070
>> 2013-07-26 22:57:31,112 INFO
>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Triggering log
>> roll on remote NameNode node2/192.168.142.130:8020
>> 2013-07-26 22:57:31,329 WARN
>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Unable to trigger
>> a roll of the active NN
>> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
>> Operation category JOURNAL is not supported in state standby
>> at
>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1401)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:871)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.rollEditLog(FSNamesystem.java:4577)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.rollEditLog(NameNodeRpcServer.java:756)
>> at
>> org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolServerSideTranslatorPB.rollEditLog(NamenodeProtocolServerSideTranslatorPB.java:129)
>> at
>> org.apache.hadoop.hdfs.protocol.proto.NamenodeProtocolProtos$NamenodeProtocolService$2.callBlockingMethod(NamenodeProtocolProtos.java:8762)
>> at
>> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
>> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
>> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1701)
>>
>
>
>
> --
> Bing Jiang
> Tel：(86)134-2619-1361
> weibo: http://weibo.com/jiangbinglover
> BLOG: www.binospace.com
> BLOG: http://blog.sina.com.cn/jiangbinglover
> Focus on distributed computing, HDFS/HBase
>
Re: two name node both in standby state?why?
Posted by ch huang <ju...@gmail.com>.
but i have not set autofailover,the ZKFC is really need for manual failover
switch?
On Fri, Jul 26, 2013 at 3:22 PM, Bing Jiang <ji...@gmail.com>wrote:
> Please check whether the process of DFSZKFailoverController is open or
> not, and each namenode should be attached with a DFSZKFailoverController.
>
>
> 2013/7/26 ch huang <ju...@gmail.com>
>
>> i have no idea,why?
>>
>> 2013-07-26 22:55:30,772 INFO org.apache.hadoop.http.HttpServer: Jetty
>> bound to port 50070
>> 2013-07-26 22:55:30,772 INFO org.mortbay.log: jetty-6.1.26.cloudera.2
>> 2013-07-26 22:55:31,001 WARN
>> org.apache.hadoop.security.authentication.server.AuthenticationFilter:
>> 'signature.secret' configuration not set, using a random value as secret
>> 2013-07-26 22:55:31,054 INFO org.mortbay.log: Started
>> SelectChannelConnector@node1:50070
>> 2013-07-26 22:55:31,054 INFO
>> org.apache.hadoop.hdfs.server.namenode.NameNode: Web-server up at:
>> node1:50070
>> 2013-07-26 22:55:31,057 INFO org.apache.hadoop.ipc.Server: IPC Server
>> Responder: starting
>> 2013-07-26 22:55:31,058 INFO org.apache.hadoop.ipc.Server: IPC Server
>> listener on 8020: starting
>> 2013-07-26 22:55:31,072 INFO
>> org.apache.hadoop.hdfs.server.namenode.NameNode: NameNode up at: node1/
>> 192.168.142.129:8020
>> 2013-07-26 22:55:31,072 INFO
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Starting services
>> required for standby state
>> 2013-07-26 22:55:31,074 INFO
>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Will roll logs on
>> active node at node2/192.168.142.130:8020 every 120 seconds.
>> 2013-07-26 22:55:31,084 INFO
>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyCheckpointer: Starting
>> standby checkpoint thread...
>> Checkpointing active NN at node2:50070
>> Serving checkpoints at node1/192.168.142.129:50070
>> 2013-07-26 22:57:31,112 INFO
>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Triggering log
>> roll on remote NameNode node2/192.168.142.130:8020
>> 2013-07-26 22:57:31,329 WARN
>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Unable to trigger
>> a roll of the active NN
>> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
>> Operation category JOURNAL is not supported in state standby
>> at
>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1401)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:871)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.rollEditLog(FSNamesystem.java:4577)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.rollEditLog(NameNodeRpcServer.java:756)
>> at
>> org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolServerSideTranslatorPB.rollEditLog(NamenodeProtocolServerSideTranslatorPB.java:129)
>> at
>> org.apache.hadoop.hdfs.protocol.proto.NamenodeProtocolProtos$NamenodeProtocolService$2.callBlockingMethod(NamenodeProtocolProtos.java:8762)
>> at
>> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
>> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
>> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1701)
>>
>
>
>
> --
> Bing Jiang
> Tel：(86)134-2619-1361
> weibo: http://weibo.com/jiangbinglover
> BLOG: www.binospace.com
> BLOG: http://blog.sina.com.cn/jiangbinglover
> Focus on distributed computing, HDFS/HBase
>
Re: two name node both in standby state?why?
Posted by ch huang <ju...@gmail.com>.
but i have not set autofailover,the ZKFC is really need for manual failover
switch?
On Fri, Jul 26, 2013 at 3:22 PM, Bing Jiang <ji...@gmail.com>wrote:
> Please check whether the process of DFSZKFailoverController is open or
> not, and each namenode should be attached with a DFSZKFailoverController.
>
>
> 2013/7/26 ch huang <ju...@gmail.com>
>
>> i have no idea,why?
>>
>> 2013-07-26 22:55:30,772 INFO org.apache.hadoop.http.HttpServer: Jetty
>> bound to port 50070
>> 2013-07-26 22:55:30,772 INFO org.mortbay.log: jetty-6.1.26.cloudera.2
>> 2013-07-26 22:55:31,001 WARN
>> org.apache.hadoop.security.authentication.server.AuthenticationFilter:
>> 'signature.secret' configuration not set, using a random value as secret
>> 2013-07-26 22:55:31,054 INFO org.mortbay.log: Started
>> SelectChannelConnector@node1:50070
>> 2013-07-26 22:55:31,054 INFO
>> org.apache.hadoop.hdfs.server.namenode.NameNode: Web-server up at:
>> node1:50070
>> 2013-07-26 22:55:31,057 INFO org.apache.hadoop.ipc.Server: IPC Server
>> Responder: starting
>> 2013-07-26 22:55:31,058 INFO org.apache.hadoop.ipc.Server: IPC Server
>> listener on 8020: starting
>> 2013-07-26 22:55:31,072 INFO
>> org.apache.hadoop.hdfs.server.namenode.NameNode: NameNode up at: node1/
>> 192.168.142.129:8020
>> 2013-07-26 22:55:31,072 INFO
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Starting services
>> required for standby state
>> 2013-07-26 22:55:31,074 INFO
>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Will roll logs on
>> active node at node2/192.168.142.130:8020 every 120 seconds.
>> 2013-07-26 22:55:31,084 INFO
>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyCheckpointer: Starting
>> standby checkpoint thread...
>> Checkpointing active NN at node2:50070
>> Serving checkpoints at node1/192.168.142.129:50070
>> 2013-07-26 22:57:31,112 INFO
>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Triggering log
>> roll on remote NameNode node2/192.168.142.130:8020
>> 2013-07-26 22:57:31,329 WARN
>> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Unable to trigger
>> a roll of the active NN
>> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
>> Operation category JOURNAL is not supported in state standby
>> at
>> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1401)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:871)
>> at
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.rollEditLog(FSNamesystem.java:4577)
>> at
>> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.rollEditLog(NameNodeRpcServer.java:756)
>> at
>> org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolServerSideTranslatorPB.rollEditLog(NamenodeProtocolServerSideTranslatorPB.java:129)
>> at
>> org.apache.hadoop.hdfs.protocol.proto.NamenodeProtocolProtos$NamenodeProtocolService$2.callBlockingMethod(NamenodeProtocolProtos.java:8762)
>> at
>> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
>> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
>> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1701)
>>
>
>
>
> --
> Bing Jiang
> Tel：(86)134-2619-1361
> weibo: http://weibo.com/jiangbinglover
> BLOG: www.binospace.com
> BLOG: http://blog.sina.com.cn/jiangbinglover
> Focus on distributed computing, HDFS/HBase
>
Re: two name node both in standby state?why?
Posted by Bing Jiang <ji...@gmail.com>.
Please check whether the process of DFSZKFailoverController is open or
not, and each namenode should be attached with a DFSZKFailoverController.
2013/7/26 ch huang <ju...@gmail.com>
> i have no idea,why?
>
> 2013-07-26 22:55:30,772 INFO org.apache.hadoop.http.HttpServer: Jetty
> bound to port 50070
> 2013-07-26 22:55:30,772 INFO org.mortbay.log: jetty-6.1.26.cloudera.2
> 2013-07-26 22:55:31,001 WARN
> org.apache.hadoop.security.authentication.server.AuthenticationFilter:
> 'signature.secret' configuration not set, using a random value as secret
> 2013-07-26 22:55:31,054 INFO org.mortbay.log: Started
> SelectChannelConnector@node1:50070
> 2013-07-26 22:55:31,054 INFO
> org.apache.hadoop.hdfs.server.namenode.NameNode: Web-server up at:
> node1:50070
> 2013-07-26 22:55:31,057 INFO org.apache.hadoop.ipc.Server: IPC Server
> Responder: starting
> 2013-07-26 22:55:31,058 INFO org.apache.hadoop.ipc.Server: IPC Server
> listener on 8020: starting
> 2013-07-26 22:55:31,072 INFO
> org.apache.hadoop.hdfs.server.namenode.NameNode: NameNode up at: node1/
> 192.168.142.129:8020
> 2013-07-26 22:55:31,072 INFO
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Starting services
> required for standby state
> 2013-07-26 22:55:31,074 INFO
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Will roll logs on
> active node at node2/192.168.142.130:8020 every 120 seconds.
> 2013-07-26 22:55:31,084 INFO
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyCheckpointer: Starting
> standby checkpoint thread...
> Checkpointing active NN at node2:50070
> Serving checkpoints at node1/192.168.142.129:50070
> 2013-07-26 22:57:31,112 INFO
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Triggering log
> roll on remote NameNode node2/192.168.142.130:8020
> 2013-07-26 22:57:31,329 WARN
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Unable to trigger
> a roll of the active NN
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
> Operation category JOURNAL is not supported in state standby
> at
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1401)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:871)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.rollEditLog(FSNamesystem.java:4577)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.rollEditLog(NameNodeRpcServer.java:756)
> at
> org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolServerSideTranslatorPB.rollEditLog(NamenodeProtocolServerSideTranslatorPB.java:129)
> at
> org.apache.hadoop.hdfs.protocol.proto.NamenodeProtocolProtos$NamenodeProtocolService$2.callBlockingMethod(NamenodeProtocolProtos.java:8762)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1701)
>
--
Bing Jiang
Tel：(86)134-2619-1361
weibo: http://weibo.com/jiangbinglover
BLOG: www.binospace.com
BLOG: http://blog.sina.com.cn/jiangbinglover
Focus on distributed computing, HDFS/HBase
Re: two name node both in standby state?why?
Posted by Bing Jiang <ji...@gmail.com>.
Please check whether the process of DFSZKFailoverController is open or
not, and each namenode should be attached with a DFSZKFailoverController.
2013/7/26 ch huang <ju...@gmail.com>
> i have no idea,why?
>
> 2013-07-26 22:55:30,772 INFO org.apache.hadoop.http.HttpServer: Jetty
> bound to port 50070
> 2013-07-26 22:55:30,772 INFO org.mortbay.log: jetty-6.1.26.cloudera.2
> 2013-07-26 22:55:31,001 WARN
> org.apache.hadoop.security.authentication.server.AuthenticationFilter:
> 'signature.secret' configuration not set, using a random value as secret
> 2013-07-26 22:55:31,054 INFO org.mortbay.log: Started
> SelectChannelConnector@node1:50070
> 2013-07-26 22:55:31,054 INFO
> org.apache.hadoop.hdfs.server.namenode.NameNode: Web-server up at:
> node1:50070
> 2013-07-26 22:55:31,057 INFO org.apache.hadoop.ipc.Server: IPC Server
> Responder: starting
> 2013-07-26 22:55:31,058 INFO org.apache.hadoop.ipc.Server: IPC Server
> listener on 8020: starting
> 2013-07-26 22:55:31,072 INFO
> org.apache.hadoop.hdfs.server.namenode.NameNode: NameNode up at: node1/
> 192.168.142.129:8020
> 2013-07-26 22:55:31,072 INFO
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Starting services
> required for standby state
> 2013-07-26 22:55:31,074 INFO
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Will roll logs on
> active node at node2/192.168.142.130:8020 every 120 seconds.
> 2013-07-26 22:55:31,084 INFO
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyCheckpointer: Starting
> standby checkpoint thread...
> Checkpointing active NN at node2:50070
> Serving checkpoints at node1/192.168.142.129:50070
> 2013-07-26 22:57:31,112 INFO
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Triggering log
> roll on remote NameNode node2/192.168.142.130:8020
> 2013-07-26 22:57:31,329 WARN
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Unable to trigger
> a roll of the active NN
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
> Operation category JOURNAL is not supported in state standby
> at
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1401)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:871)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.rollEditLog(FSNamesystem.java:4577)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.rollEditLog(NameNodeRpcServer.java:756)
> at
> org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolServerSideTranslatorPB.rollEditLog(NamenodeProtocolServerSideTranslatorPB.java:129)
> at
> org.apache.hadoop.hdfs.protocol.proto.NamenodeProtocolProtos$NamenodeProtocolService$2.callBlockingMethod(NamenodeProtocolProtos.java:8762)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1701)
>
--
Bing Jiang
Tel：(86)134-2619-1361
weibo: http://weibo.com/jiangbinglover
BLOG: www.binospace.com
BLOG: http://blog.sina.com.cn/jiangbinglover
Focus on distributed computing, HDFS/HBase
Re: two name node both in standby state?why?
Posted by Bing Jiang <ji...@gmail.com>.
Please check whether the process of DFSZKFailoverController is open or
not, and each namenode should be attached with a DFSZKFailoverController.
2013/7/26 ch huang <ju...@gmail.com>
> i have no idea,why?
>
> 2013-07-26 22:55:30,772 INFO org.apache.hadoop.http.HttpServer: Jetty
> bound to port 50070
> 2013-07-26 22:55:30,772 INFO org.mortbay.log: jetty-6.1.26.cloudera.2
> 2013-07-26 22:55:31,001 WARN
> org.apache.hadoop.security.authentication.server.AuthenticationFilter:
> 'signature.secret' configuration not set, using a random value as secret
> 2013-07-26 22:55:31,054 INFO org.mortbay.log: Started
> SelectChannelConnector@node1:50070
> 2013-07-26 22:55:31,054 INFO
> org.apache.hadoop.hdfs.server.namenode.NameNode: Web-server up at:
> node1:50070
> 2013-07-26 22:55:31,057 INFO org.apache.hadoop.ipc.Server: IPC Server
> Responder: starting
> 2013-07-26 22:55:31,058 INFO org.apache.hadoop.ipc.Server: IPC Server
> listener on 8020: starting
> 2013-07-26 22:55:31,072 INFO
> org.apache.hadoop.hdfs.server.namenode.NameNode: NameNode up at: node1/
> 192.168.142.129:8020
> 2013-07-26 22:55:31,072 INFO
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Starting services
> required for standby state
> 2013-07-26 22:55:31,074 INFO
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Will roll logs on
> active node at node2/192.168.142.130:8020 every 120 seconds.
> 2013-07-26 22:55:31,084 INFO
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyCheckpointer: Starting
> standby checkpoint thread...
> Checkpointing active NN at node2:50070
> Serving checkpoints at node1/192.168.142.129:50070
> 2013-07-26 22:57:31,112 INFO
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Triggering log
> roll on remote NameNode node2/192.168.142.130:8020
> 2013-07-26 22:57:31,329 WARN
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Unable to trigger
> a roll of the active NN
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
> Operation category JOURNAL is not supported in state standby
> at
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1401)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:871)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.rollEditLog(FSNamesystem.java:4577)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.rollEditLog(NameNodeRpcServer.java:756)
> at
> org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolServerSideTranslatorPB.rollEditLog(NamenodeProtocolServerSideTranslatorPB.java:129)
> at
> org.apache.hadoop.hdfs.protocol.proto.NamenodeProtocolProtos$NamenodeProtocolService$2.callBlockingMethod(NamenodeProtocolProtos.java:8762)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1701)
>
--
Bing Jiang
Tel：(86)134-2619-1361
weibo: http://weibo.com/jiangbinglover
BLOG: www.binospace.com
BLOG: http://blog.sina.com.cn/jiangbinglover
Focus on distributed computing, HDFS/HBase
Re: two name node both in standby state?why?
Posted by Bing Jiang <ji...@gmail.com>.
Please check whether the process of DFSZKFailoverController is open or
not, and each namenode should be attached with a DFSZKFailoverController.
2013/7/26 ch huang <ju...@gmail.com>
> i have no idea,why?
>
> 2013-07-26 22:55:30,772 INFO org.apache.hadoop.http.HttpServer: Jetty
> bound to port 50070
> 2013-07-26 22:55:30,772 INFO org.mortbay.log: jetty-6.1.26.cloudera.2
> 2013-07-26 22:55:31,001 WARN
> org.apache.hadoop.security.authentication.server.AuthenticationFilter:
> 'signature.secret' configuration not set, using a random value as secret
> 2013-07-26 22:55:31,054 INFO org.mortbay.log: Started
> SelectChannelConnector@node1:50070
> 2013-07-26 22:55:31,054 INFO
> org.apache.hadoop.hdfs.server.namenode.NameNode: Web-server up at:
> node1:50070
> 2013-07-26 22:55:31,057 INFO org.apache.hadoop.ipc.Server: IPC Server
> Responder: starting
> 2013-07-26 22:55:31,058 INFO org.apache.hadoop.ipc.Server: IPC Server
> listener on 8020: starting
> 2013-07-26 22:55:31,072 INFO
> org.apache.hadoop.hdfs.server.namenode.NameNode: NameNode up at: node1/
> 192.168.142.129:8020
> 2013-07-26 22:55:31,072 INFO
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Starting services
> required for standby state
> 2013-07-26 22:55:31,074 INFO
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Will roll logs on
> active node at node2/192.168.142.130:8020 every 120 seconds.
> 2013-07-26 22:55:31,084 INFO
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyCheckpointer: Starting
> standby checkpoint thread...
> Checkpointing active NN at node2:50070
> Serving checkpoints at node1/192.168.142.129:50070
> 2013-07-26 22:57:31,112 INFO
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Triggering log
> roll on remote NameNode node2/192.168.142.130:8020
> 2013-07-26 22:57:31,329 WARN
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer: Unable to trigger
> a roll of the active NN
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
> Operation category JOURNAL is not supported in state standby
> at
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1401)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:871)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.rollEditLog(FSNamesystem.java:4577)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.rollEditLog(NameNodeRpcServer.java:756)
> at
> org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolServerSideTranslatorPB.rollEditLog(NamenodeProtocolServerSideTranslatorPB.java:129)
> at
> org.apache.hadoop.hdfs.protocol.proto.NamenodeProtocolProtos$NamenodeProtocolService$2.callBlockingMethod(NamenodeProtocolProtos.java:8762)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1701)
>
--
Bing Jiang
Tel：(86)134-2619-1361
weibo: http://weibo.com/jiangbinglover
BLOG: www.binospace.com
BLOG: http://blog.sina.com.cn/jiangbinglover
Focus on distributed computing, HDFS/HBase