Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HDFS >> mail # user >> Re: ./hdfs namenode -bootstrapStandby error


Copy link to this message
-
Re: ./hdfs namenode -bootstrapStandby error
Hi, Azuryy

Running the 'hdfs namenode -initializeSharedEdits'  command on the active
NN ,  I must to stop the Active NameNode.

I  think when  excuting the "./hdfs namenode -bootstrapStandby" command on
Standby NameNode, the Active NameNode and JournalNameNodes should  be alive,
otherwise  there is no HA.

I was a beginner  for QJM , there is something wrong, please correct me.
Thanks,

LiuLei

2013/7/19 Azuryy Yu <[EMAIL PROTECTED]>

> hi,
>
> can you using
> 'hdfs namenode -initializeSharedEdits' on the active NN, remember start
> all journal nodes before try this.
>  On Jul 19, 2013 5:17 PM, "lei liu" <[EMAIL PROTECTED]> wrote:
>
>> I  use hadoop-2.0.5 version and use QJM for HA.
>>
>>
>> I use ./hdfs namenode -bootstrapStandby for StandbyNameNode, but report
>> below error:
>>
>> ====================================================>> About to bootstrap Standby ID nn2 from:
>>            Nameservice ID: mycluster
>>         Other Namenode ID: nn1
>>   Other NN's HTTP address: 10.232.98.77:20021
>>   Other NN's IPC  address: dw77.kgb.sqa.cm4/10.232.98.77:20020
>>              Namespace ID: 1499625118
>>             Block pool ID: BP-2012507965-10.232.98.77-1372993302021
>>                Cluster ID: CID-921af0aa-b831-4828-965c-3b71a5149600
>>            Layout version: -40
>> ====================================================>> Re-format filesystem in Storage Directory
>> /home/musa.ll/hadoop2/cluster-data/name ? (Y or N) Y
>> 13/07/19 17:04:28 INFO common.Storage: Storage directory
>> /home/musa.ll/hadoop2/cluster-data/name has been successfully formatted.
>> 13/07/19 17:04:29 FATAL ha.BootstrapStandby: Unable to read transaction
>> ids 16317-16337 from the configured shared edits storage qjournal://
>> 10.232.98.61:20022;10.232.98.62:20022;10.232.98.63:20022/mycluster.
>> Please copy these logs into the shared edits storage or call saveNamespace
>> on the active node.
>> Error: Gap in transactions. Expected to be able to read up until at least
>> txid 16337 but unable to find any edit logs containing txid 16331
>> 13/07/19 17:04:29 INFO util.ExitUtil: Exiting with status 6
>>
>>
>>
>> The edit logs are below content in JournalNode:
>> -rw-r--r-- 1 musa.ll users      30 Jul 19 15:51
>> edits_0000000000000016327-0000000000000016328
>> -rw-r--r-- 1 musa.ll users      30 Jul 19 15:53
>> edits_0000000000000016329-0000000000000016330
>> -rw-r--r-- 1 musa.ll users 1048576 Jul 19 17:03
>> edits_inprogress_0000000000000016331
>>
>>
>> The edits_inprogress_0000000000000016331 should contains the 16331-16337
>> transactions, why the "./hdfs namenode -bootstrapStandby" command report
>> error? How can I initialize the StandbyNameNode?
>>
>> Thanks,
>>
>> LiuLei
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>