Re: backup node question

2013-04-07 Thread Azuryy Yu
oh, got it. you are a good guy. --Send from my Sony mobile. On Apr 7, 2013 10:11 PM, "Harsh J" wrote: > StandbyNameNode is the term we use to refer to a NameNode in HA that > is currently not the active one (i.e. its state is 'Standby'). Its not > a special type of daemon (i.e. it just runs the

Re: backup node question

2013-04-07 Thread Harsh J
StandbyNameNode is the term we use to refer to a NameNode in HA that is currently not the active one (i.e. its state is 'Standby'). Its not a special type of daemon (i.e. it just runs the NameNode service), just a naming convention. On Sun, Apr 7, 2013 at 7:31 PM, Azuryy Yu wrote: > I am confused

Re: backup node question

2013-04-07 Thread Azuryy Yu
SNN=secondary name node in my last mail. --Send from my Sony mobile. On Apr 7, 2013 10:01 PM, "Azuryy Yu" wrote: > I am confused. Hadoopv2 has NN SNN DN JN(journal node), so whats > Standby Namenode? > > --Send from my Sony mobile. > On Apr 7, 2013 9:03 PM, "Harsh J" wrote: > >> BackupNameNode

Re: backup node question

2013-04-07 Thread Azuryy Yu
I am confused. Hadoopv2 has NN SNN DN JN(journal node), so whats Standby Namenode? --Send from my Sony mobile. On Apr 7, 2013 9:03 PM, "Harsh J" wrote: > BackupNameNode is not present in the maintenance 1.x releases, it is a > feature added to a higher version; you can try it out in 2.x today if

Re: backup node question

2013-04-07 Thread Harsh J
BackupNameNode is not present in the maintenance 1.x releases, it is a feature added to a higher version; you can try it out in 2.x today if you wish to. On Sun, Apr 7, 2013 at 3:12 PM, Azuryy Yu wrote: > Hi Harsh, > Do you mean BackupNameNode is Secondary NameNode in Hadoop1.x? > > > On Sun, Apr

Re: backup node question

2013-04-07 Thread Azuryy Yu
Hi Harsh, Do you mean BackupNameNode is Secondary NameNode in Hadoop1.x? On Sun, Apr 7, 2013 at 4:05 PM, Harsh J wrote: > Yes, it need not keep an edits (transactions) stream locally cause > those are passed synchronously to the BackupNameNode, which persists > it on its behalf. > > On Sun, Apr

Re: backup node question

2013-04-07 Thread Lin Ma
Thanks for answering my question, Harsh. regards, Lin On Sun, Apr 7, 2013 at 4:05 PM, Harsh J wrote: > Yes, it need not keep an edits (transactions) stream locally cause > those are passed synchronously to the BackupNameNode, which persists > it on its behalf. > > On Sun, Apr 7, 2013 at 1:21 PM

Re: backup node question

2013-04-07 Thread Harsh J
Yes, it need not keep an edits (transactions) stream locally cause those are passed synchronously to the BackupNameNode, which persists it on its behalf. On Sun, Apr 7, 2013 at 1:21 PM, Lin Ma wrote: > Thanks Harsh, > > For your comments, "What it means is that the NameNode need not store > anyth

Re: backup node question

2013-04-07 Thread Lin Ma
Thanks Harsh, For your comments, "What it means is that the NameNode need not store anything locally", you mean Primary Name Node do not need to store checkpoint/journal locally, and only need to keep memory image up-to-date for edits? regards, Lin On Sun, Apr 7, 2013 at 3:31 PM, Harsh J wrote:

Re: backup node question

2013-04-07 Thread Harsh J
Hi Lin, My reply inline. On Sun, Apr 7, 2013 at 12:36 PM, Lin Ma wrote: > Hi guys, > > I am reading from this paper to learn about backup nodes > (http://www.storageconference.org/2010/Papers/MSST/Shvachko.pdf), > > It is mentioned, "It contains all file system metadata information except > for