e is already sunk according to stack's reply:
> >>
> >> -- Forwarded message --
> >> From: Stack
> >> Date: 10 January 2018 at 02:09
> >> Subject: Re: [VOTE] The second hbase-2.0.0-beta-1 Release Candidate is
> >> available
rCommandLine.
> start(
> > > > > HRegionServerCommandLine.java:66)
> > > > > at
> > > > > org.apache.hadoop.hbase.regionserver.HRegionServerCommandLine.run(
> > > > > HRegionServerCommandLine.java:85)
> > > > > at org.apach
Please see tail of the "Re: Testing and CI -- Apache Jenkins Builds (WAS ->
Re: Testing)" thread which ends with note on this disabling. These
'old-style' jobs have been disabled in favor the nightly runs.
S
On Wed, Jan 10, 2018 at 8:44 AM, Ted Yu wrote:
> Hi,
> I was looking at:
> https://build
f peeps starting contributing
> on
> > this front?
> >
> >
> > > I'd be happy to help try to track down the root causes of the flakiness
> > and
> > > try to fix these problematic tests.
> > >
> > Any help here would be great!
> > Here&#
Thanks Appy. Looks beautiful. Is Nightly now using a list of flakes? Thanks.
S
On Thu, Jan 11, 2018 at 6:10 PM, Apekshit Sharma wrote:
> https://builds.apache.org/job/HBase-Find-Flaky-Tests-
> branch2.0/lastSuccessfulBuild/artifact/dashboard.html
>
> @stack: when you branch out bra
The third release candidate for HBase 2.0.0-beta-1 is up at:
https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-1-RC2/
Maven artifacts are available from a staging directory here:
https://repository.apache.org/content/repositories/orgapachehbase-1191
All was signed with my key at
Dashboard doesn't capture timed out tests, right Appy?
Thanks,
S
On Thu, Jan 11, 2018 at 6:10 PM, Apekshit Sharma wrote:
> https://builds.apache.org/job/HBase-Find-Flaky-Tests-
> branch2.0/lastSuccessfulBuild/artifact/dashboard.html
>
> @stack: when you branch out branch-2.0,
There seem to be too many tests failing for this to pass. Just a heads up
that if you are seeing this, its not you. I'm looking at it. Will report
back.
FYI, I need to look into RC-building time too. It takes many hours to
produce one.
Thanks,
S
On Thu, Jan 11, 2018 at 10:30 PM, Stack
t that would resolve it.
>
>
Yeah. Let me add that. I find this a goodly portion but enforcer checking
and for some reason, hangs in archetypes eats up loads of time too (I'm
finding that my build machines seem to have rotted which doesn't help the
situation).
S
>
> &g
-19694 The initialization order for
a fresh cluster is incorrect". It raises a bunch of interesting issues that
we'll have to deal with in a beta-2 (that were hidden, but present
nonetheless, by the previous start order).
Pardon my trying your patience.
Yours,
St.Ack
On Thu, Jan 11, 201
The fourth release candidate for HBase 2.0.0-beta-1 is up at:
https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-1-RC3/
Maven artifacts are available from a staging directory here:
https://repository.apache.org/content/repositories/orgapachehbase-1193
All was signed with my key a
+1
Checked sig and hash.
Downloaded locally. Undid and loaded data. Logs look good.
Put on cluster. Picks up old data fine. Nothing odd in logs (too much
logging but that is another story).
St.Ack
On Fri, Jan 12, 2018 at 8:48 PM, Stack wrote:
> The fourth release candidate for HBase 2.
Anyone using it? As far as I know it goes unsupported (anyone interested in
this project?).
Building a release takes two hours, one hour of which is archetype
machinations, so its not my favorite module these times.
Purge it from hbase?
St.Ack
again for your patience/understanding.
Yours,
Your RM
1.
https://builds.apache.org/job/HBase%20Nightly/job/branch-2/183/artifact/output-jdk8-hadoop2/patch-unit-root.txt
On Fri, Jan 12, 2018 at 8:48 PM, Stack wrote:
> The fourth release candidate for HBase 2.0.0-beta-1 is up at
Yeah. HBASE-18467. Patches welcome.
S
On Sat, Jan 13, 2018 at 10:13 AM, Ted Yu wrote:
> I noticed that for JIRAs which were applied to branch-1.x , there was no
> post from Hudson about the corresponding build.
>
> It would be desirable to have such post for branch-1.x .
>
> Cheers
>
> On Wed, J
Its unassigned now.
S
On Sat, Jan 13, 2018 at 12:31 PM, Ted Yu wrote:
> That was assigned to Sean.
>
> Do you know when Sean would be back ?
>
> On Sat, Jan 13, 2018 at 12:29 PM, Stack wrote:
>
> > Yeah. HBASE-18467. Patches welcome.
> > S
> >
> >
+1
Checked hash and signature.
Downloaded bin. Checked layout and doc.
Started it up. Checked UI and logs.
Loaded data. Verified it made it in.
St.Ack
On Fri, Jan 12, 2018 at 6:14 PM, Andrew Purtell wrote:
> A snapshot of HBase 1.3.2 is available for testing in Apache's Maven or at
>
> http
More Still +1.
Downloaded src. Built a tgz. Ran it. Poked around (logs, UI).
Looks good,
S
On Sat, Jan 13, 2018 at 1:19 PM, Stack wrote:
> +1
>
> Checked hash and signature.
> Downloaded bin. Checked layout and doc.
> Started it up. Checked UI and logs.
> Loaded data. V
Thanks to all who have voted so far. It is great to see the votes coming
in. Need one more PMC-er +1 please.
Thanks,
S
On Fri, Jan 12, 2018 at 8:48 PM, Stack wrote:
> The fourth release candidate for HBase 2.0.0-beta-1 is up at:
>
> https://dist.apache.org/repos/dist/dev/hbase/hb
With 6 +1s (three binding) and none against, the vote passes. Thanks to all
who helped with this difficult delivery.
St.Ack
On Fri, Jan 12, 2018 at 8:48 PM, Stack wrote:
> The fourth release candidate for HBase 2.0.0-beta-1 is up at:
>
> https://dist.apache.org/repos/dist/dev/hb
The HBase team is happy to announce the immediate availability of Apache
HBase 2.0.0-beta-1!
Apache HBase is an open-source, distributed, versioned, non-relational
database. Apache HBase gives you low latency random access to billions of
rows with millions of columns atop non-specialized hardwar
Thanks Appy. We need this.
S
On Fri, Jan 19, 2018 at 4:25 PM, Apekshit Sharma wrote:
> Here's the job: https://builds.apache.org/job/HBase-2.0-hadoop3-tests
> (Still trying to make it work).
>
> Why do we need separate temporary job?
> - Jenkins pipeline doesn't yet support running step B if ste
Looks like Master was added a few days ago, by mistake is my guess:
https://github.com/apache/hbase/branches
Kill it after ensuring master has all its commits?
Shout if you want me to do it sir.
S
On Fri, Jan 19, 2018 at 2:50 PM, Apekshit Sharma wrote:
> I see following three branches:
> re
moves us from yetus 0.6.0 to 0.7.0 has been pushed to all
active branches and our hadoopqa up on jenkins has been configured to use
it going forward.
FYI,
S
On Fri, Dec 8, 2017 at 12:13 PM, Stack wrote:
> Thanks Andrew. I disabled the job. Use the nightly going forward. The jdk7
> builds s
Looking...
S
On Tue, Jan 30, 2018 at 2:37 AM, 张铎(Duo Zhang)
wrote:
> Seems like an infra issue. In the morning(in China) there is no available
> node under the label ubuntu...
>
> Anyone who can access the infra mailing list please send an email? I'm not
> in that list yet...
>
> Thanks.
>
> 201
Oh, concurrent, there seems to be an errant geode build process making its
way around the build boxes according to INFRA.
S
On Tue, Jan 30, 2018 at 5:01 PM, Stack wrote:
> Thanks Sean. Allen showed up on issues to report same. Trying to backfill
> his recommendation on how to up proclimit
source usage, fyi.
>
> On Jan 30, 2018 08:53, "Stack" wrote:
>
> > Looking...
> > S
> >
> > On Tue, Jan 30, 2018 at 2:37 AM, 张铎(Duo Zhang)
> > wrote:
> >
> > > Seems like an infra issue. In the morning(in China) there is no
>
Note that I reverted our yetus version last night. It discombobulated our
builds (OOMEs). Meantime, you'll have to do the patch naming trick for
another day or so. Our test runs seem to use an ungodly number of file
descriptors Stay tuned.
S
On Mon, Jan 29, 2018 at 10:56 PM, Stack
I just set hadoopqa to be 0.7.0 again with an upped proclimit to see if
this fixes our OOME failures.. HadoopQA builds numbered 11295 and later
will have this change.
Thanks
S
On Wed, Jan 31, 2018 at 6:46 AM, Stack wrote:
> Note that I reverted our yetus version last night. It discombobula
All seems to have settled now. Hadoopqa is running 'normally' again with
yetus 0.7.0 and some new configs (Thanks to Allen Wittenhauer for the
help/input...). That said, we need to work on curbing resources used during
test runs
St.Ack
On Wed, Jan 31, 2018 at 9:01 AM, Stack wrote:
On Thu, Feb 1, 2018 at 4:01 AM, Kang Minwoo wrote:
> Hello, dev users.
>
> I want to join the slack channel.
> Please invite me slack.
>
> Best regards,
> Minwoo Kang
>
Looks like an invite has been sent?
S
QEE being a DNRIOE seems right on the face of it.
But if throttling, a DNRIOE is inappropriate. Where you seeing a QEE in a
throttling scenario Huaxiang?
Thanks,
S
On Tue, Feb 6, 2018 at 4:56 PM, Huaxiang Sun wrote:
> Hi HBase devs,
>
> I found that QuotaExceededException is a DoNotRetry
On Fri, Feb 2, 2018 at 9:13 PM, Mike Drob wrote:
> Hi folks, has there been any consideration put forth toward the next
> HBaseCon? The last one was very productive for me personally, but I hadn't
> heard anything about the schedule for 2018 so figured I could ask on list.
>
> Mike
>
Is been kin
T-05:00 Bijieshan :
> >
> >> Huawei can continue to hold HBaseCon Asia 2018 :-)
> >>
> >> Best Regards,
> >> Jieshan.
> >> -Original Message-
> >> From: saint@gmail.com [mailto:saint@gmail.com] On Behalf Of
> Stack
> &
Regards,
> Yu
>
> On 8 February 2018 at 00:36, Stack wrote:
>
> > On Fri, Feb 2, 2018 at 9:13 PM, Mike Drob wrote:
> >
> > > Hi folks, has there been any consideration put forth toward the next
> > > HBaseCon? The last one was very productive for me personal
> On Feb 8, 2018 10:57 PM, "Stack" wrote:
>
> > Super sweet Yu Li!
> >
> > Between your kind offer and Bijieshan's note, we should be good in China
> > (smile).
> >
> > St.Ack
> >
> > On Thu, Feb 8, 2018 at 12:39 AM, Yu L
On Thu, Feb 15, 2018 at 11:39 AM, Sean Busbey wrote:
> Heya folks,
>
> I've been reading about underlying technologies we might use to
> improve coprocessors, with an eye towards a long term goal of better
> isolating them.
>
> Today I started reading about Apache Arrow, which is a data format an
On Wed, Feb 14, 2018 at 3:19 PM, Zach York
wrote:
> Hello,
>
> I have been trying for some time to figure out an issue where splits fail
> due to trying to cache the same key, but different value.
Whats the exception look like Mighty Zach?
...
> What I know/have observed:
> This occurs when
+1 (but one question on bottom)
Checked hash and signature.
Built tgz from src download and ran it.
Poked around. Looks good.
Loaded data. Verified it present.
Shutdown. Logs looked good.
Question: For some reason my master port was homed on 63502... anyone else
have this issue? I didn't spend m
On Tue, Feb 20, 2018 at 11:36 AM, Josh Elser wrote:
> Hi folks,
>
> Just curious where I can offer a hand on the remaining 2.0.0-beta2 work. I
> know the theme was upgrade, and I also saw the good test-fixing work that's
> also happening now.
>
> Anything still pending on the radar I can help out
On Fri, Feb 23, 2018 at 11:10 AM, Ted Yu wrote:
> Can you check whether region c15b13946fa4318a0a956e067d59ebd4 is healthy
> (via hbck) ?
>
>
hbck does not work against hbase2 [1].
S
1.
https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_ktczrlKHK8N4SZzs/edit#heading=h.3jy69yxm0gxm
On Fri, Feb 23, 2018 at 11:04 AM, Jean-Marc Spaggiari <
jean-m...@spaggiari.org> wrote:
> Hi guys,
>
> In HBase 2.0.0-beta-1, getting this:
>
> 2018-02-23 14:01:55,499 WARN [main] client.HBaseAdmin
> (HBaseAdmin.java:visit(1948)) - No serialized HRegionInfo in
> keyvalues={page_proposed,,13841980
Duo:
A bad nightly build ruined our dashboard. A bad run produced many tests for
the flakies list. The flakies list then timed out because too many tests to
run. Appy cleaned it up, mostly. It will take a few hours for the failures
to clear out (it seems to be coming along nicely).
I should have
Short Version: Please hold on making commits to branch-2. I am in the
process of cutting a hbase-2.0.0-beta-2 release candidate. It make take me
a day or so.
Long Version:
A miracle happened last night. Our nightly for branch-2 passed [1]. This
means all unit tests ran against hadoop2 and then su
o with some
exercise along any of these dimensions if any of you have a few spare
cycles. Thanks.
1. hbase-2.0.0 still has this smell to it, but we do our best.
2.
https://issues.apache.org/jira/projects/HBASE/versions/12327188#release-report-tab-body
On Wed, Dec 27, 2017 at 9:54 AM, Stack wro
The first release candidate for HBase 2.0.0-beta-2 is up at
https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-2.RC0/
Maven artifacts are available from a staging directory here:
https://repository.apache.org/content/repositories/orgapachehbase-1199
All was signed with my key at 8
iled afte...
> [ERROR] TestReplicationAdmin.testPeerExcludeNamespaces:515 »
> RetriesExhausted Failed a...
> [ERROR] TestReplicationAdmin.testPeerReplicationEndpointImpl:795 »
> RetriesExhausted Fa...
> [ERROR] TestReplicationAdmin.testSetPeerNamespaces:457 »
> RetriesExhausted
&
ied
> running TestReplicationAdmin a couple of times and can not reliably
> reproduce the problem.
>
> I am changing my vote to +1.
>
> Thanks,
> Umesh
>
>
> On Sun, Mar 4, 2018 at 2:43 PM, Stack wrote:
>
> > Thank Umesh for giving it a run.
> >
> >
r:jar:2.7.4:test
[INFO] | +- org.apache.hadoop:hadoop-common:test-jar:tests:2.7.4:test
Thanks for trying the RC Chia-Ping,
S
>
> On 2018/03/02 23:40:53, Stack wrote:
> > The first release candidate for HBase 2.0.0-beta-2 is up at
> >
> > https://dist.apache.org/repos/dis
On the vote thread for hbase-2.0.0-beta-2, it was noted that the bulk of
our convenience bin tarball size is test javadoc [1] (~ > 50%). Should our
bin tarball include all possible doc both api and dev api for both test and
user?
I could make it so we do not build dev doc by default or that we do
up on our site. They will also be available in Maven and your
> > favorite IDE should handle the automatic download and use of javadoc
> jars.
> >
> >
> > On Tue, Mar 6, 2018 at 11:29 AM, Stack wrote:
> >
> >> On the vote thread for hbase-2.0.0-beta-2, it was note
OESC[m]
> > [ESC[1;31mERRORESC[m] ESC[1;31mFailures: ESC[m
> > [ESC[1;31mERRORESC[m] ESC[1;31m
> > TestSpnegoHttpServer.testAllowedClient:243->Assert.
> > assertEquals:631->Assert.assertEquals:645->Assert.
> > failNotEquals:834->Assert.fail:88
> > expected:<
ain.
Please ping me before committing on branch-2. Trying to keep the ship
upright.
Thanks for your patience,
St.Ack
> On Thu, Mar 1, 2018 at 11:59 AM, Stack wrote:
> > Short Version: Please hold on making commits to branch-2. I am in the
> > process of cutting a hbase-2.0.0-b
After release, hopefully in morning. Thanks for reminder.
S
On Tue, Mar 6, 2018 at 4:48 PM, 张铎(Duo Zhang) wrote:
> So is it the time to cut branch-2.0?
>
> 2018-03-07 8:04 GMT+08:00 Stack :
>
> > On Tue, Mar 6, 2018 at 10:32 AM, Sean Busbey wrote:
> >
> > > Is
hoping for.
>
> sign/sums ok
> SHOULD NOT supply a MD5 checksum file (because MD5 is too broken). [1]
>
> compile src 8u151 ok
> compile src 8u151 w/ error-prone NOT OK - HBASE-19987
>
> [1]: http://www.apache.org/dev/release-distribution#sigs-and-sums
>
>
>
>
Vote passes with 4 binding +1s, 3 non-binding, and a +0.
Let me push out this release.
Thanks to all for the robust vote.
S
On Wed, Mar 7, 2018 at 9:12 AM, Stack wrote:
> Thanks Mike. I'll remove the .md5 when I post the release.
>
> I'm +1.
>
> Ran 1B ITBLL and it
The HBase team is happy to announce the immediate availability of Apache
HBase 2.0.0-beta-2!
Apache HBase is an open-source, distributed, versioned, non-relational
database. Apache HBase gives you low latency random access to billions of
rows with millions of columns atop non-specialized hardwar
Please get my approval committing to branch-2.0. I'm trying to keep the
branch stable as we head toward our first 2.0.0 release candidate.
Related, please do not treat branch-2 as a dumping ground going forward.
I'll try and keep an eye on it too (per an old Andrew Purtell suggestion
that we do a
(Moving discussion to DISCUSSION thread from "NOTICE: made branch-2.0
from..." -- my fault for starting it in wrong place)
A while back, Andrew made a PROPOSAL for 'branch RM's [1]. I like this
suggestion. I see it as a means of avoiding the hell that was 2.0.0 where
its taken near on a year to st
On Thu, Mar 8, 2018 at 6:40 PM, Sean Busbey wrote:
> Hi folks!
>
> I've been working to get the test suite back to green on branch-1.2;
> we have a lot of branches to track backport for and a non-trivial
> amount of tech debt across all of them from the nightlies being
> offline.
>
> After the st
9:20 GMT+08:00 张铎(Duo Zhang) :
>
> > If branch-2.0 will be out soon then let's target this to 2.1. No problem.
> >
> > Thanks.
> >
> > 2018-01-10 1:28 GMT+08:00 Stack :
> >
> >> On Mon, Jan 8, 2018 at 8:19 PM, 张铎(Duo Zhang)
> >> wrot
Very nice Mr. Drob.
S
On Fri, Mar 9, 2018 at 2:07 PM, Mike Drob wrote:
> Hi devs,
>
> Over on HBASE-20153[1] I put up a patch to include error-prone[2] compiler
> checks on precommit. Wanted to send out a note to the dev list to make sure
> people saw it and understood what was happening, and so
; > > +1 for master (which already happened, maybe?)
> > > +0 for branch-2 (simply because I haven't looked closely enough at
> > > changes, can read through and try to change to +1 if you need the
> votes)
> > >
> > >
> > > On 3/9/18 2:4
On Tue, Mar 13, 2018 at 6:30 PM, 张铎(Duo Zhang)
wrote:
> I would be interested to be the RM for 2.1 :)
>
>
I could help.
S
> Stack 于2018年3月14日 周三02:48写道：
>
> > I took a look. Its great. Our replication is in bad need of loving. The
> > patch does a refactor/revamp/
On Tue, Mar 13, 2018 at 8:44 PM, Stack wrote:
> On Tue, Mar 13, 2018 at 6:30 PM, 张铎(Duo Zhang)
> wrote:
>
>> I would be interested to be the RM for 2.1 :)
>>
>>
> I could help.
>
Or, I meant, good... We need more RMs. I volunteer to help smooth the
experience.
On Wed, Mar 14, 2018 at 11:55 PM, OpenInx wrote:
> Hi :
>
> (Paste from https://issues.apache.org/jira/browse/HBASE-20166?
> focusedCommentId=16399886&page=com.atlassian.jira.
> plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16399886)
>
> There's a really big problem here if we use table
On Thu, Mar 15, 2018 at 12:03 PM, Josh Elser wrote:
> I'm faced with what I think is a tricky issue. I'm trying to help folks to
> compile HBase on PPC. The protobuf community does not publish a PPC binary
> for protoc which means that the HBase build can't generate our protobuf
> files. Protobuf
row etc.
St.Ack
> 2018-03-16 3:01 GMT+08:00 Stack :
>
> > On Wed, Mar 14, 2018 at 11:55 PM, OpenInx wrote:
> >
> > > Hi :
> > >
> > > (Paste from https://issues.apache.org/jira/browse/HBASE-20166?
> > > focusedCommentId=16399886&
On Thu, Mar 15, 2018 at 8:42 PM, Guanghao Zhang wrote:
> >
> > We've done the work to make sure hbase:meta
> > is up before everything else. It has its own WALs so we can split these
> > ahead of user-space WALs, and so on. We've not done the work to for
> > hbase:replication or hbase:namespace,
Probably too risky to do at this stage in the game but protobuf? We're on
3.3.1. Latest is 3.5.1 [1]: "Various performance optimizations." And Guava
is 24.1 now. We're on 22.
St.Ack
1. https://github.com/google/protobuf/releases
On Fri, Mar 16, 2018 at 1:47 PM, Josh Elser wrote:
> Give a shout
t;> comparison perf / GC test? I can help.
>>
>> On Fri, Mar 16, 2018 at 2:41 PM, Stack wrote:
>>
>> Probably too risky to do at this stage in the game but protobuf? We're on
>>> 3.3.1. Latest is 3.5.1 [1]: "Various performance optimizations."
+1
Verified signature and hash.
I see it updates pb but not guava? No harm. Next time.
Built and installed jars locally from src tgz.
Applied the HBASE-20223 patch to branch-2 and built... all seems good.
Thanks for doing this,
S
On Mon, Mar 19, 2018 at 4:15 PM, Josh Elser wrote:
> Hi,
>
On Tue, Mar 20, 2018 at 7:51 PM, Josh Elser wrote:
> Hi all,
>
> I've published a new website for the upcoming event in June in California
> at [1][2] for the HBase and Phoenix websites, respectively. 1 & 2 are
> identical.
>
> I've not yet updated any links on either website to link to the new p
On Wed, Mar 21, 2018 at 9:26 AM, Josh Elser wrote:
>
>
> On 3/21/18 2:59 AM, Stack wrote:
>
>> On Tue, Mar 20, 2018 at 7:51 PM, Josh Elser wrote:
>>
>> Hi all,
>>>
>>> I've published a new website for the upcoming event in June in Califo
Shout if there is anything you need in it. Meantime help w/ docs, perf,
test, metrics, etc., appreciated.
Thanks.
Your RM,
S
P.S. Current list of 2.0.0 targeted items:
https://issues.apache.org/jira/projects/HBASE/versions/12327188#release-report-tab-body
On Thu, Mar 22, 2018 at 5:53 AM, 张铎(Duo Zhang)
wrote:
> I'd like to fix HBASE-19952. Before beta2 it is a bit difficult to do it
> because the 'mvn test' always fails...
>
>
Sounds good Duo. Thanks.
S
> 2018-03-22 13:44 GMT+08:00 Stack :
>
> > Sh
Purge.
My assessment is that the OWNER project failed; valiants signed-up with the
best of intentions but because of tooling, consistency, attrition, unknowns
(pick one), the project faded soon after launch.
Thanks,
St.Ack
On Wed, Mar 28, 2018 at 7:42 AM, Sean Busbey wrote:
> In late 2012 we t
On Wed, Mar 28, 2018 at 11:31 PM, Toshihiro Suzuki
wrote:
> Hi folks,
>
> We are facing “IllegalStateException: requestSeek cannot be called on
> ReversedKeyValueHeap" when using a reverse scan and the
> loadColumnFamiliesOnDemand optimization is enabled. As ReversedKeyValueHeap
> doesn't support
On Mon, Apr 2, 2018 at 1:27 PM, Mike Drob wrote:
> Duo, can you include content from
> https://issues.apache.org/jira/browse/HBASE-16689 when you are writing up
> the docs as well? Not sure if that is talking about same or different Async
> Wal option, actually.
>
>
I'll do the above.
Just reali
HBASE-20329 is first cut.
S
On Mon, Apr 2, 2018 at 2:11 PM, Stack wrote:
> On Mon, Apr 2, 2018 at 1:27 PM, Mike Drob wrote:
>
>> Duo, can you include content from
>> https://issues.apache.org/jira/browse/HBASE-16689 when you are writing up
>> the docs as well? Not sure
The first release candidate for Apache HBase 2.0.0 is available for
downloading and testing.
Artifacts are available here:
https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
Maven artifacts are available in the staging repository at:
https://repository.apache.org/content/repositorie
>
>
HBASE-18622 has current state of compatibility compare. Let me do a new run
and add it to the RC dir.
St.Ack
>
> On Tue, Apr 10, 2018 at 3:47 PM, Stack wrote:
> > The first release candidate for Apache HBase 2.0.0 is available for
> > downloading and testing.
t;
> > > not a blocker; we've been inconsistent on it in prior releases, but
> > > the trend seemed to be towards including it.
> > >
> > >
> > > On Tue, Apr 10, 2018 at 3:47 PM, Stack wrote:
> > > > The first release candidate for Apache
On Thu, Apr 12, 2018 at 1:47 PM, Stack wrote:
> On Tue, Apr 10, 2018 at 2:50 PM, Sean Busbey wrote:
>
>> no compat report in the RC directory. does that mean we won't have one
>> in the dist area?
>>
>>
>> not a blocker; we've been inconsistent on
Hot dog!
On Wed, Apr 11, 2018 at 1:03 PM, Andrew Purtell wrote:
> On behalf of the Apache HBase PMC I am pleased to announce that Francis
> Liu has accepted our invitation to become a PMC member on the Apache
> HBase project. We appreciate Francis stepping up to take more
> responsibility in the
cker
> > -- or we as a community can decide to work on it in a follow-on release
> > making perf a priority (say, 2.1.0).
> > I see, thanks for the clarification boss, makes sense.
> >
> > Best Regards,
> > Yu
> >
> > On 13 April 2018 at 06:02, Stack w
t; > callDurat...
> > > >
> > > > Thanks,
> > > >
> > > > JMS
> > > >
> > > >
> > > > 2018-04-13 0:19 GMT-04:00 Yu Li :
> > > >
> > > >> bq. I'd imagine that if the difference were large, then y
A simple
> `assign` in the shell brought them back, but I need to dig in some more to
> understand what went wrong.
>
>
Log?
HBASE-18152?
Thanks Josh,
S
>
> On 4/10/18 4:47 PM, Stack wrote:
>
>> The first release candidate for Apache HBase 2.0.0 is available for
&g
-
> OK
> start local instance from bin & CRUD from shell - OK
> LTT write, read1 million rows, 2 cols/row - OK
> check logs - OK
>
>
> On Fri, Apr 13, 2018 at 10:55 AM, Stack wrote:
>
&g
s of HBASE-20244).
St.Ack
On Tue, Apr 17, 2018 at 4:14 PM, Wei-Chiu Chuang
wrote:
> -1 (non-binding)
> Hbase 2 will break on Hadoop 3.0.1 or above, due to HBASE-20244 caused by
> the refactor in HDFS-12574.
> Is Hbase 2 on Hadoop 3 a requirement for the release?
>
> On Tue, Ap
some instances -- and then refer readers to
the perf chapter which we can fill in findings as we go (post hbase2
release even).
Thanks,
St.Ack
>
> On Tue, Apr 17, 2018 at 4:59 PM, Stack wrote:
> > Yeah, what Ashish says Umesh (and yeah, checkout HBASE-20385 for the why
> > si
081d3 HBASE-20310 Fixed false inconsistency shown by hbck -metaonly
option on HBase 2
0e8d42b HBASE-20219 An error occurs when scanning with reversed=true and
loadColumnFamiliesOnDemand=true
907b264 HBASE-20358 Fix bin/hbase thrift usage text
200afa1 HBASE-20382 If RSGroups not enabled, rsgroup.jsp p
m ports stuff tonight.
>
>
> On 4/18/18 5:35 PM, Stack wrote:
>
>> On Wed, Apr 18, 2018 at 12:58 PM, Josh Elser wrote:
>>
>> +1 (binding)
>>>
>>> There are rough edges, of course, but I think this is more than enough
>>> quality for a 2.0.0. Put
The second release candidate for Apache HBase 2.0.0 is available for
downloading and testing.
Artifacts are available here:
https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC1/
Maven artifacts are available in the staging repository at:
https://repository.apache.org/content/repositori
java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1134)
> java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:624)
> java.lang.Thread.run(Thread.java:748)
> - Thread LEAK? -, OpenFileDescriptor=237 (was 232) - OpenFileDescriptor
The third release candidate for Apache HBase 2.0.0 is available for
downloading and testing.
Artifacts are available here:
https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC2/
Maven artifacts are available in the staging repository at:
https://repository.apache.org/content/repositories
On Tue, Apr 24, 2018 at 1:25 AM, Lars Francke
wrote:
> Stack,
>
> I'm sure you'll want to slap me for bringing this up so late (I only found
> it recently) but could you take a look at the recent discussions in <
> https://issues.apache.org/jira/browse/HBASE-19746>
Thanks Lars.
S
On Wed, Apr 25, 2018 at 1:28 AM, Lars Francke
wrote:
> Thanks Stack.
>
> In that case I'm -0 on this RC.
> I'd really like to either revert that patch or at least document the
> deprecation so we can remove it in 3.0. The way it is now we can't
Agree.
If we want to torture a contributor, we can set them on fixing all
complaints.
St.Ack
On Wed, Apr 25, 2018 at 7:28 AM, Sean Busbey wrote:
> Hi folks!
>
> Given how often I see us ignoring ruby-lint feedback in precommit,
> would anyone be opposed to me changing its vote from -1 to -0?
>
1 - 100 of 6256 matches
Mail list logo
