Dave, As Uma expanded it, its Protocol Buffers (http://code.google.com/p/protobuf/), we now use it for performing all of Hadoop's internal RPCs. One good reason for the change, was to introduce (and to simplify) IPC wire compatibility so that clients can talk to different major versions of servers (which isn't possible today).
You can find more information in Sanjay's document here: https://issues.apache.org/jira/browse/HADOOP-7347 (and all its associated JIRAs) On Mon, Mar 12, 2012 at 5:47 PM, Dave Shine <dave.sh...@channelintelligence.com> wrote: > I apologize for asking a dumb question. I know what HA is, but what does PB > stand for? > > Thanks, > Dave > > > -----Original Message----- > From: Todd Lipcon [mailto:t...@cloudera.com] > Sent: Friday, March 09, 2012 8:40 PM > To: common-dev@hadoop.apache.org > Subject: Re: Release with PB and HA > > +1, I agree we should do 23.3 ASAP with HA. There are a couple JIRAs > worth resolving before we do the release, but some time in the next couple > weeks we should be ready to cut an RC. > > -Todd > > On Fri, Mar 9, 2012 at 11:58 AM, Uma Maheswara Rao G <mahesw...@huawei.com> > wrote: >> Giving release soon would be good idea. I have seen many people waiting for >> the initiaal HA release. So, that we will get the feedback soon from the >> users for more stabilization. >> Also can start Automatic fail-over with full focus. >> >> Regards, >> Uma >> ________________________________________ >> From: Eli Collins [e...@cloudera.com] >> Sent: Friday, March 09, 2012 11:41 PM >> To: common-dev@hadoop.apache.org >> Subject: Release with PB and HA >> >> Hey gang, >> >> Now that branch-23 has PB and (almost) HA checked in, it would be good >> to get these out into the wild so more people can start kicking the >> tires. >> >> How about we cut a 23.3 release soon from branch-23? Or perhaps >> re-branch 23.2 if that's easier. >> >> Thanks, >> Eli > > > > -- > Todd Lipcon > Software Engineer, Cloudera > > The information contained in this email message is considered confidential > and proprietary to the sender and is intended solely for review and use by > the named recipient. Any unauthorized review, use or distribution is strictly > prohibited. If you have received this message in error, please advise the > sender by reply email and delete the message. -- Harsh J
