You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-user@hadoop.apache.org by Dheeren Bebortha <db...@salesforce.com> on 2013/02/15 19:28:19 UTC
Hadoop 2.0.3 namenode issue
HI,
In one of our test clusters that has Namenode HA using QJM+ YARN + HBase 0.94, namenode came down with following logs. I am trying to root cause the issue. Any help is appreciated.
=================
2013-02-13 10:18:27,521 INFO hdfs.StateChange - BLOCK*
NameSystem.fsync: file
/hbase/.logs/datanode-X.sfdomain.com,60020,1360091866476/datanode-X.sfdomain.com%2C60020%2C1360091866476.1360750706694
for DFSClient_hb_rs_datanode-X.sfdomain.com,60020,1360091866476_470800334_38
2013-02-13 10:20:01,861 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49933 got version 4 expected version 7
2013-02-13 10:20:01,884 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49935 got version 4 expected version 7
2013-02-13 10:20:02,550 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49938 got version 4 expected version 7
2013-02-13 10:20:08,210 INFO namenode.FSNamesystem - Roll Edit Log from
10.232.29.14
=====
=====
======
2013-02-13 12:14:32,879 INFO namenode.FileJournalManager - Finalizing edits file /data/hdfs/current/edits_inprogress_0000000000000065699 ->
/data/hdfs/current/edits_0000000000000065699-0000000000000065700
2013-02-13 12:14:32,879 INFO namenode.FSEditLog - Starting log segment at 65701
2013-02-13 12:15:02,507 INFO namenode.NameNode - FSCK started by sfdc
(auth:SIMPLE) from /10.232.29.4 for path / at Wed Feb 13 12:15:02
GMT+00:00 2013
2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40025 got version 4 expected version 7
2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40027 got version 4 expected version 7
2013-02-13 12:15:03,391 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40031 got version 4 expected version 7
2013-02-13 12:16:33,181 INFO namenode.FSNamesystem - Roll Edit Log from
10.232.29.14
======================
======================
Re: Hadoop 2.0.3 namenode issue
Posted by Harsh J <ha...@cloudera.com>.
I don't see a crash log in your snippets. Mind pastebinning the NN
crash log up somewhere? Did both NNs go down?
In any case, the log below is due to a client attempting to connect
with an older HDFS library. This would log such warns (and also
indicate the client IP/attempt port as you notice), but in no case
will it cause an NN crash.
> 2013-02-13 10:20:02,550 WARN ipc.Server - Incorrect header or version mismatch from10.232.29.4:49938 got version 4 expected version 7
On Fri, Feb 15, 2013 at 11:58 PM, Dheeren Bebortha
<db...@salesforce.com> wrote:
>
>
> HI,
> In one of our test clusters that has Namenode HA using QJM+ YARN + HBase 0.94, namenode came down with following logs. I am trying to root cause the issue. Any help is appreciated.
> =================
> 2013-02-13 10:18:27,521 INFO hdfs.StateChange - BLOCK*
> NameSystem.fsync: file
> /hbase/.logs/datanode-X.sfdomain.com,60020,1360091866476/datanode-X.sfdomain.com%2C60020%2C1360091866476.1360750706694
> for DFSClient_hb_rs_datanode-X.sfdomain.com,60020,1360091866476_470800334_38
> 2013-02-13 10:20:01,861 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49933 got version 4 expected version 7
> 2013-02-13 10:20:01,884 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49935 got version 4 expected version 7
> 2013-02-13 10:20:02,550 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49938 got version 4 expected version 7
> 2013-02-13 10:20:08,210 INFO namenode.FSNamesystem - Roll Edit Log from
> 10.232.29.14
> =====
> =====
> ======
> 2013-02-13 12:14:32,879 INFO namenode.FileJournalManager - Finalizing edits file /data/hdfs/current/edits_inprogress_0000000000000065699 ->
> /data/hdfs/current/edits_0000000000000065699-0000000000000065700
> 2013-02-13 12:14:32,879 INFO namenode.FSEditLog - Starting log segment at 65701
> 2013-02-13 12:15:02,507 INFO namenode.NameNode - FSCK started by sfdc
> (auth:SIMPLE) from /10.232.29.4 for path / at Wed Feb 13 12:15:02
> GMT+00:00 2013
> 2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40025 got version 4 expected version 7
> 2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40027 got version 4 expected version 7
> 2013-02-13 12:15:03,391 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40031 got version 4 expected version 7
> 2013-02-13 12:16:33,181 INFO namenode.FSNamesystem - Roll Edit Log from
> 10.232.29.14
> ======================
> ======================
--
Harsh J
Re: Hadoop 2.0.3 namenode issue
Posted by Harsh J <ha...@cloudera.com>.
I don't see a crash log in your snippets. Mind pastebinning the NN
crash log up somewhere? Did both NNs go down?
In any case, the log below is due to a client attempting to connect
with an older HDFS library. This would log such warns (and also
indicate the client IP/attempt port as you notice), but in no case
will it cause an NN crash.
> 2013-02-13 10:20:02,550 WARN ipc.Server - Incorrect header or version mismatch from10.232.29.4:49938 got version 4 expected version 7
On Fri, Feb 15, 2013 at 11:58 PM, Dheeren Bebortha
<db...@salesforce.com> wrote:
>
>
> HI,
> In one of our test clusters that has Namenode HA using QJM+ YARN + HBase 0.94, namenode came down with following logs. I am trying to root cause the issue. Any help is appreciated.
> =================
> 2013-02-13 10:18:27,521 INFO hdfs.StateChange - BLOCK*
> NameSystem.fsync: file
> /hbase/.logs/datanode-X.sfdomain.com,60020,1360091866476/datanode-X.sfdomain.com%2C60020%2C1360091866476.1360750706694
> for DFSClient_hb_rs_datanode-X.sfdomain.com,60020,1360091866476_470800334_38
> 2013-02-13 10:20:01,861 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49933 got version 4 expected version 7
> 2013-02-13 10:20:01,884 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49935 got version 4 expected version 7
> 2013-02-13 10:20:02,550 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49938 got version 4 expected version 7
> 2013-02-13 10:20:08,210 INFO namenode.FSNamesystem - Roll Edit Log from
> 10.232.29.14
> =====
> =====
> ======
> 2013-02-13 12:14:32,879 INFO namenode.FileJournalManager - Finalizing edits file /data/hdfs/current/edits_inprogress_0000000000000065699 ->
> /data/hdfs/current/edits_0000000000000065699-0000000000000065700
> 2013-02-13 12:14:32,879 INFO namenode.FSEditLog - Starting log segment at 65701
> 2013-02-13 12:15:02,507 INFO namenode.NameNode - FSCK started by sfdc
> (auth:SIMPLE) from /10.232.29.4 for path / at Wed Feb 13 12:15:02
> GMT+00:00 2013
> 2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40025 got version 4 expected version 7
> 2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40027 got version 4 expected version 7
> 2013-02-13 12:15:03,391 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40031 got version 4 expected version 7
> 2013-02-13 12:16:33,181 INFO namenode.FSNamesystem - Roll Edit Log from
> 10.232.29.14
> ======================
> ======================
--
Harsh J
Re: Hadoop 2.0.3 namenode issue
Posted by Harsh J <ha...@cloudera.com>.
I don't see a crash log in your snippets. Mind pastebinning the NN
crash log up somewhere? Did both NNs go down?
In any case, the log below is due to a client attempting to connect
with an older HDFS library. This would log such warns (and also
indicate the client IP/attempt port as you notice), but in no case
will it cause an NN crash.
> 2013-02-13 10:20:02,550 WARN ipc.Server - Incorrect header or version mismatch from10.232.29.4:49938 got version 4 expected version 7
On Fri, Feb 15, 2013 at 11:58 PM, Dheeren Bebortha
<db...@salesforce.com> wrote:
>
>
> HI,
> In one of our test clusters that has Namenode HA using QJM+ YARN + HBase 0.94, namenode came down with following logs. I am trying to root cause the issue. Any help is appreciated.
> =================
> 2013-02-13 10:18:27,521 INFO hdfs.StateChange - BLOCK*
> NameSystem.fsync: file
> /hbase/.logs/datanode-X.sfdomain.com,60020,1360091866476/datanode-X.sfdomain.com%2C60020%2C1360091866476.1360750706694
> for DFSClient_hb_rs_datanode-X.sfdomain.com,60020,1360091866476_470800334_38
> 2013-02-13 10:20:01,861 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49933 got version 4 expected version 7
> 2013-02-13 10:20:01,884 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49935 got version 4 expected version 7
> 2013-02-13 10:20:02,550 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49938 got version 4 expected version 7
> 2013-02-13 10:20:08,210 INFO namenode.FSNamesystem - Roll Edit Log from
> 10.232.29.14
> =====
> =====
> ======
> 2013-02-13 12:14:32,879 INFO namenode.FileJournalManager - Finalizing edits file /data/hdfs/current/edits_inprogress_0000000000000065699 ->
> /data/hdfs/current/edits_0000000000000065699-0000000000000065700
> 2013-02-13 12:14:32,879 INFO namenode.FSEditLog - Starting log segment at 65701
> 2013-02-13 12:15:02,507 INFO namenode.NameNode - FSCK started by sfdc
> (auth:SIMPLE) from /10.232.29.4 for path / at Wed Feb 13 12:15:02
> GMT+00:00 2013
> 2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40025 got version 4 expected version 7
> 2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40027 got version 4 expected version 7
> 2013-02-13 12:15:03,391 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40031 got version 4 expected version 7
> 2013-02-13 12:16:33,181 INFO namenode.FSNamesystem - Roll Edit Log from
> 10.232.29.14
> ======================
> ======================
--
Harsh J
Re: Hadoop 2.0.3 namenode issue
Posted by Harsh J <ha...@cloudera.com>.
I don't see a crash log in your snippets. Mind pastebinning the NN
crash log up somewhere? Did both NNs go down?
In any case, the log below is due to a client attempting to connect
with an older HDFS library. This would log such warns (and also
indicate the client IP/attempt port as you notice), but in no case
will it cause an NN crash.
> 2013-02-13 10:20:02,550 WARN ipc.Server - Incorrect header or version mismatch from10.232.29.4:49938 got version 4 expected version 7
On Fri, Feb 15, 2013 at 11:58 PM, Dheeren Bebortha
<db...@salesforce.com> wrote:
>
>
> HI,
> In one of our test clusters that has Namenode HA using QJM+ YARN + HBase 0.94, namenode came down with following logs. I am trying to root cause the issue. Any help is appreciated.
> =================
> 2013-02-13 10:18:27,521 INFO hdfs.StateChange - BLOCK*
> NameSystem.fsync: file
> /hbase/.logs/datanode-X.sfdomain.com,60020,1360091866476/datanode-X.sfdomain.com%2C60020%2C1360091866476.1360750706694
> for DFSClient_hb_rs_datanode-X.sfdomain.com,60020,1360091866476_470800334_38
> 2013-02-13 10:20:01,861 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49933 got version 4 expected version 7
> 2013-02-13 10:20:01,884 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49935 got version 4 expected version 7
> 2013-02-13 10:20:02,550 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49938 got version 4 expected version 7
> 2013-02-13 10:20:08,210 INFO namenode.FSNamesystem - Roll Edit Log from
> 10.232.29.14
> =====
> =====
> ======
> 2013-02-13 12:14:32,879 INFO namenode.FileJournalManager - Finalizing edits file /data/hdfs/current/edits_inprogress_0000000000000065699 ->
> /data/hdfs/current/edits_0000000000000065699-0000000000000065700
> 2013-02-13 12:14:32,879 INFO namenode.FSEditLog - Starting log segment at 65701
> 2013-02-13 12:15:02,507 INFO namenode.NameNode - FSCK started by sfdc
> (auth:SIMPLE) from /10.232.29.4 for path / at Wed Feb 13 12:15:02
> GMT+00:00 2013
> 2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40025 got version 4 expected version 7
> 2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40027 got version 4 expected version 7
> 2013-02-13 12:15:03,391 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40031 got version 4 expected version 7
> 2013-02-13 12:16:33,181 INFO namenode.FSNamesystem - Roll Edit Log from
> 10.232.29.14
> ======================
> ======================
--
Harsh J
Re: Hadoop 2.0.3 namenode issue
Posted by Marcos Ortiz Valmaseda <ml...@uci.cu>.
Regards, Dheeren. It seems that you are using an incompatible version of HDFS with this
version of HBase. Can you provide the exact version of your HBase package?
----- Mensaje original -----
De: "Dheeren Bebortha" <db...@salesforce.com>
Para: user@hadoop.apache.org
Enviados: Viernes, 15 de Febrero 2013 13:28:19
Asunto: Hadoop 2.0.3 namenode issue
HI,
In one of our test clusters that has Namenode HA using QJM+ YARN + HBase 0.94, namenode came down with following logs. I am trying to root cause the issue. Any help is appreciated.
=================
2013-02-13 10:18:27,521 INFO hdfs.StateChange - BLOCK*
NameSystem.fsync: file
/hbase/.logs/datanode-X.sfdomain.com,60020,1360091866476/datanode-X.sfdomain.com%2C60020%2C1360091866476.1360750706694
for DFSClient_hb_rs_datanode-X.sfdomain.com,60020,1360091866476_470800334_38
2013-02-13 10:20:01,861 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49933 got version 4 expected version 7
2013-02-13 10:20:01,884 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49935 got version 4 expected version 7
2013-02-13 10:20:02,550 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49938 got version 4 expected version 7
2013-02-13 10:20:08,210 INFO namenode.FSNamesystem - Roll Edit Log from
10.232.29.14
=====
=====
======
2013-02-13 12:14:32,879 INFO namenode.FileJournalManager - Finalizing edits file /data/hdfs/current/edits_inprogress_0000000000000065699 ->
/data/hdfs/current/edits_0000000000000065699-0000000000000065700
2013-02-13 12:14:32,879 INFO namenode.FSEditLog - Starting log segment at 65701
2013-02-13 12:15:02,507 INFO namenode.NameNode - FSCK started by sfdc
(auth:SIMPLE) from /10.232.29.4 for path / at Wed Feb 13 12:15:02
GMT+00:00 2013
2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40025 got version 4 expected version 7
2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40027 got version 4 expected version 7
2013-02-13 12:15:03,391 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40031 got version 4 expected version 7
2013-02-13 12:16:33,181 INFO namenode.FSNamesystem - Roll Edit Log from
10.232.29.14
======================
======================
--
Marcos Ortiz Valmaseda,
Product Manager && Data Scientist at UCI
Blog : http://marcosluis2186.posterous.com
LinkedIn: http://www.linkedin.com/in/marcosluis2186
Twitter : @marcosluis2186
Re: Hadoop 2.0.3 namenode issue
Posted by Marcos Ortiz Valmaseda <ml...@uci.cu>.
Regards, Dheeren. It seems that you are using an incompatible version of HDFS with this
version of HBase. Can you provide the exact version of your HBase package?
----- Mensaje original -----
De: "Dheeren Bebortha" <db...@salesforce.com>
Para: user@hadoop.apache.org
Enviados: Viernes, 15 de Febrero 2013 13:28:19
Asunto: Hadoop 2.0.3 namenode issue
HI,
In one of our test clusters that has Namenode HA using QJM+ YARN + HBase 0.94, namenode came down with following logs. I am trying to root cause the issue. Any help is appreciated.
=================
2013-02-13 10:18:27,521 INFO hdfs.StateChange - BLOCK*
NameSystem.fsync: file
/hbase/.logs/datanode-X.sfdomain.com,60020,1360091866476/datanode-X.sfdomain.com%2C60020%2C1360091866476.1360750706694
for DFSClient_hb_rs_datanode-X.sfdomain.com,60020,1360091866476_470800334_38
2013-02-13 10:20:01,861 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49933 got version 4 expected version 7
2013-02-13 10:20:01,884 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49935 got version 4 expected version 7
2013-02-13 10:20:02,550 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49938 got version 4 expected version 7
2013-02-13 10:20:08,210 INFO namenode.FSNamesystem - Roll Edit Log from
10.232.29.14
=====
=====
======
2013-02-13 12:14:32,879 INFO namenode.FileJournalManager - Finalizing edits file /data/hdfs/current/edits_inprogress_0000000000000065699 ->
/data/hdfs/current/edits_0000000000000065699-0000000000000065700
2013-02-13 12:14:32,879 INFO namenode.FSEditLog - Starting log segment at 65701
2013-02-13 12:15:02,507 INFO namenode.NameNode - FSCK started by sfdc
(auth:SIMPLE) from /10.232.29.4 for path / at Wed Feb 13 12:15:02
GMT+00:00 2013
2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40025 got version 4 expected version 7
2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40027 got version 4 expected version 7
2013-02-13 12:15:03,391 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40031 got version 4 expected version 7
2013-02-13 12:16:33,181 INFO namenode.FSNamesystem - Roll Edit Log from
10.232.29.14
======================
======================
--
Marcos Ortiz Valmaseda,
Product Manager && Data Scientist at UCI
Blog : http://marcosluis2186.posterous.com
LinkedIn: http://www.linkedin.com/in/marcosluis2186
Twitter : @marcosluis2186
Re: Hadoop 2.0.3 namenode issue
Posted by Marcos Ortiz Valmaseda <ml...@uci.cu>.
Regards, Dheeren. It seems that you are using an incompatible version of HDFS with this
version of HBase. Can you provide the exact version of your HBase package?
----- Mensaje original -----
De: "Dheeren Bebortha" <db...@salesforce.com>
Para: user@hadoop.apache.org
Enviados: Viernes, 15 de Febrero 2013 13:28:19
Asunto: Hadoop 2.0.3 namenode issue
HI,
In one of our test clusters that has Namenode HA using QJM+ YARN + HBase 0.94, namenode came down with following logs. I am trying to root cause the issue. Any help is appreciated.
=================
2013-02-13 10:18:27,521 INFO hdfs.StateChange - BLOCK*
NameSystem.fsync: file
/hbase/.logs/datanode-X.sfdomain.com,60020,1360091866476/datanode-X.sfdomain.com%2C60020%2C1360091866476.1360750706694
for DFSClient_hb_rs_datanode-X.sfdomain.com,60020,1360091866476_470800334_38
2013-02-13 10:20:01,861 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49933 got version 4 expected version 7
2013-02-13 10:20:01,884 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49935 got version 4 expected version 7
2013-02-13 10:20:02,550 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49938 got version 4 expected version 7
2013-02-13 10:20:08,210 INFO namenode.FSNamesystem - Roll Edit Log from
10.232.29.14
=====
=====
======
2013-02-13 12:14:32,879 INFO namenode.FileJournalManager - Finalizing edits file /data/hdfs/current/edits_inprogress_0000000000000065699 ->
/data/hdfs/current/edits_0000000000000065699-0000000000000065700
2013-02-13 12:14:32,879 INFO namenode.FSEditLog - Starting log segment at 65701
2013-02-13 12:15:02,507 INFO namenode.NameNode - FSCK started by sfdc
(auth:SIMPLE) from /10.232.29.4 for path / at Wed Feb 13 12:15:02
GMT+00:00 2013
2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40025 got version 4 expected version 7
2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40027 got version 4 expected version 7
2013-02-13 12:15:03,391 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40031 got version 4 expected version 7
2013-02-13 12:16:33,181 INFO namenode.FSNamesystem - Roll Edit Log from
10.232.29.14
======================
======================
--
Marcos Ortiz Valmaseda,
Product Manager && Data Scientist at UCI
Blog : http://marcosluis2186.posterous.com
LinkedIn: http://www.linkedin.com/in/marcosluis2186
Twitter : @marcosluis2186
Re: Hadoop 2.0.3 namenode issue
Posted by Marcos Ortiz Valmaseda <ml...@uci.cu>.
Regards, Dheeren. It seems that you are using an incompatible version of HDFS with this
version of HBase. Can you provide the exact version of your HBase package?
----- Mensaje original -----
De: "Dheeren Bebortha" <db...@salesforce.com>
Para: user@hadoop.apache.org
Enviados: Viernes, 15 de Febrero 2013 13:28:19
Asunto: Hadoop 2.0.3 namenode issue
HI,
In one of our test clusters that has Namenode HA using QJM+ YARN + HBase 0.94, namenode came down with following logs. I am trying to root cause the issue. Any help is appreciated.
=================
2013-02-13 10:18:27,521 INFO hdfs.StateChange - BLOCK*
NameSystem.fsync: file
/hbase/.logs/datanode-X.sfdomain.com,60020,1360091866476/datanode-X.sfdomain.com%2C60020%2C1360091866476.1360750706694
for DFSClient_hb_rs_datanode-X.sfdomain.com,60020,1360091866476_470800334_38
2013-02-13 10:20:01,861 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49933 got version 4 expected version 7
2013-02-13 10:20:01,884 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49935 got version 4 expected version 7
2013-02-13 10:20:02,550 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:49938 got version 4 expected version 7
2013-02-13 10:20:08,210 INFO namenode.FSNamesystem - Roll Edit Log from
10.232.29.14
=====
=====
======
2013-02-13 12:14:32,879 INFO namenode.FileJournalManager - Finalizing edits file /data/hdfs/current/edits_inprogress_0000000000000065699 ->
/data/hdfs/current/edits_0000000000000065699-0000000000000065700
2013-02-13 12:14:32,879 INFO namenode.FSEditLog - Starting log segment at 65701
2013-02-13 12:15:02,507 INFO namenode.NameNode - FSCK started by sfdc
(auth:SIMPLE) from /10.232.29.4 for path / at Wed Feb 13 12:15:02
GMT+00:00 2013
2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40025 got version 4 expected version 7
2013-02-13 12:15:02,663 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40027 got version 4 expected version 7
2013-02-13 12:15:03,391 WARN ipc.Server - Incorrect header or version mismatch from 10.232.29.4:40031 got version 4 expected version 7
2013-02-13 12:16:33,181 INFO namenode.FSNamesystem - Roll Edit Log from
10.232.29.14
======================
======================
--
Marcos Ortiz Valmaseda,
Product Manager && Data Scientist at UCI
Blog : http://marcosluis2186.posterous.com
LinkedIn: http://www.linkedin.com/in/marcosluis2186
Twitter : @marcosluis2186