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

Switch to Threaded View
HBase >> mail # dev >> VOTE: hbase-0.95RC1, the second "Development" Series Release is available [WAS -> VOTE: hbase-0.95.0RC0, the first "Developer Release" release candidate is available for download and vote]


Copy link to this message
-
Re: VOTE: hbase-0.95RC1, the second "Development" Series Release is available [WAS -> VOTE: hbase-0.95.0RC0, the first "Developer Release" release candidate is available for download and vote]
Thanks lads.

Vote is closed.

Let me push out 0.95.0.

St.Ack
On Fri, Apr 5, 2013 at 10:43 PM, Andrew Purtell <[EMAIL PROTECTED]> wrote:

> I see this too.
>
> +1 also.
>
>
> On Fri, Apr 5, 2013 at 10:31 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:
>
> > Installed the -hadoop1 tarball, started HBase, inserted some data,
> > flushed, compacted, scanned, inspected the UI pages, stopped it again.
> > Checked the docs.
> >
> >
> > CHANGES.txt is a bit weird as it does not contain the 0.94 issues from
> > before it was branched, but that's just a nit.
> >
> > In the logs I see:
> > 2013-04-05 22:18:03,805 WARN
> > org.apache.hadoop.hbase.regionserver.HRegionServer:
> >  error telling master we are up
> > com.google.protobuf.ServiceException: methodName=regionServerStartup
> >         at
> > org.apache.hadoop.hbase.ipc.ProtobufRpcClientEngine$Invoker.invoke(Pr
> > otobufRpcClientEngine.java:147)
> >         at sun.proxy.$Proxy8.regionServerStartup(Unknown Source)
> >         at
> >
> org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1798)
> >         at
> >
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:723)
> >         at java.lang.Thread.run(Thread.java:722)
> > Caused by:
> > org.apache.hadoop.hbase.exceptions.ServerNotRunningYetException: org.
> >
> >
> > But in the end the RS started up anyway. Again, just a nit (in local mode
> > the master does not start fast enough it seems, and the RS is too
> > impatient).
> >
> >
> > +1
> >
> > -- Lars
> >
> >
> >
> > ________________________________
> >  From: Stack <[EMAIL PROTECTED]>
> > To: HBase Dev List <[EMAIL PROTECTED]>
> > Sent: Friday, April 5, 2013 9:53 PM
> > Subject: Re: VOTE: hbase-0.95RC1, the second "Development" Series Release
> > is available [WAS -> VOTE: hbase-0.95.0RC0, the first "Developer Release"
> > release candidate is available for download and vote]
> >
> > Any chance of a few more +1s here so I can push this out?  Thanks all.
> > St.Ack
> >
> >
> > On Tue, Apr 2, 2013 at 10:12 PM, Stack <[EMAIL PROTECTED]> wrote:
> >
> > > Here is the second 0.95.0 release candidate.  Should we put this out as
> > > 0.95.0?  Please
> > > vote by friday, April 5th.
> > >
> > > See the refguide [1] for definition of what a "Development" Series
> > Release
> > > is (or read below where we call it a 'developer release").  In short,
> it
> > is
> > > a preview release, not for production, put out early so us devs start
> > > getting feedback the sooner.
> > >
> > > The release is available here:
> > >
> > >   http://people.apache.org/~stack/hbase-0.95.0RC1/
> > >
> > > Issues fixed in this release are available here:
> > >
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12324094
> > >
> > > ...including a fix for HBASE-8242, the issue that sunk the first
> release
> > > candidate.
> > >
> > > Thanks,
> > > St.Ack
> > >
> > > 1. http://hbase.apache.org/book.html#hbase.versioning
> > >
> > > On Mon, Apr 1, 2013 at 4:52 PM, Stack <[EMAIL PROTECTED]> wrote:
> > >
> > >> Here is our first 0.95.0 release candidate.  Should we put this out as
> > >> 0.95.0?
> > >>
> > >> The 0.95.x series of releases are designated "developer releases", a
> > type
> > >> of release we have done in the past -- see the 0.89.x series -- where
> we
> > >> let out 'raw', barely-tested product so developers and those generally
> > >> interested can get some early exposure to what our next stable release
> > to
> > >> follow 0.94.x will look like.  Putting out these 'rough cuts' also
> helps
> > >> to get the feedback started earlier while the release is still baking.
> > >>
> > >> These "developer release" come with no guarantees.  We make no
> > >> promises that the next release will be compatible with this one or
> even
> > >> that
> > >> you will be able to preserve data across the update (This is at an
> > >> extreme,
> > >> and highly unlikely, but could be the case).  No work has been done to