On Fri, Mar 31, 2017 at 9:39 PM, Ted Yu wrote:
> Can you tell us which release of hbase you used ?
>
2.0.0 Snapshot
>
> Please describe values for the config parameters in hbase-site.xml
>
> The content of hbase-site.xml is shown below, but indeed this problem is
not sensitive to configuration
Thanks Misty! You are a- automation-mazing!
On Fri, Mar 31, 2017 at 3:06 PM Misty Stanley-Jones
wrote:
> And emails will now only go out if the job fails, so you won't see these
> anymore at all.
>
> On Fri, Mar 31, 2017, at 03:03 PM, Misty Stanley-Jones wrote:
> > FYI, the linked Jenkins job no
Can you tell us which release of hbase you used ?
Please describe values for the config parameters in hbase-site.xml
Do you have SSD(s) in your cluster ?
If so and the mixed workload involves writes, have you taken a look at
HBASE-12848
?
Cheers
On Fri, Mar 31, 2017 at 7:29 PM, 杨苏立 Yang Su Li
Hi,
We found that when there is a mix of CPU-intensive and I/O intensive
workload, HBase seems to slow everything down to the disk throughput level.
This is shown in the performance graph at
http://pages.cs.wisc.edu/~suli/blocking-orig.pdf : both client-1 and
client-2 are issuing 1KB Gets. From s
Looks fine.
Incorporating another public dimension probably makes the version scheme
too complex. Keep it simple.
Jerry
On Fri, Mar 31, 2017 at 5:30 PM 张铎(Duo Zhang) wrote:
> Some progress here.
>
> In HBASE-17857, a sub task of HBASE-17828, I've created a script to remove
> all the IS annot
Some progress here.
In HBASE-17857, a sub task of HBASE-17828, I've created a script to remove
all the IS annotations for the IA.Public API. And I've also changed the
IA.Public annotations for several classes which are marked as IS.Unstable
to IA.Private. We can change them back when we think they
Yeah I've already done it when sending the first email :)
Josh Elser 于2017年4月1日 周六02:27写道:
> Just checked and I don't see 'em there anymore. I assume someone else
> has already done this :)
>
> Enis Söztutar wrote:
> > Thanks for the cleanup. Indeed we should remove these from jira admin so
> > th
Umesh Agashe created HBASE-17863:
Summary: Procedure V2: Some cleanup around isFinished() and
procedure executor
Key: HBASE-17863
URL: https://issues.apache.org/jira/browse/HBASE-17863
Project: HBase
All,
We have updated the Code of Conduct to be a little more explicit about
how much we value diversity in the HBase project, and to ask for your
feedback on how we can improve. Your feedback is ALWAYS welcome, whether
on one of the public mailing lists or privately to a committer or a PMC
member
And emails will now only go out if the job fails, so you won't see these
anymore at all.
On Fri, Mar 31, 2017, at 03:03 PM, Misty Stanley-Jones wrote:
> FYI, the linked Jenkins job now automatically updates the site! No more
> need to manually push. Merry Christmas! :)
>
> - Original message
FYI, the linked Jenkins job now automatically updates the site! No more
need to manually push. Merry Christmas! :)
- Original message -
From: Apache Jenkins Server
To: dev@hbase.apache.org
Subject: Successful: HBase Generate Website
Date: Fri, 31 Mar 2017 21:32:17 + (UTC)
Build statu
Build status: Successful
If successful, the website and docs have been generated and the site has been
updated automatically.
If failed, see https://builds.apache.org/job/hbase_generate_website/562/console
YOU DO NOT NEED TO DO THE FOLLOWING ANYMORE! It is here for informational
purposes and sh
Build status: Successful
If successful, the website and docs have been generated and the site has been
updated automatically.
If failed, see https://builds.apache.org/job/hbase_generate_website/561/console
YOU DO NOT NEED TO DO THE FOLLOWING ANYMORE! It is here for informational
purposes and sh
Build status: Aborted
If successful, the website and docs have been generated and the site has been
updated automatically.
If failed, see https://builds.apache.org/job/hbase_generate_website/560/console
YOU DO NOT NEED TO DO THE FOLLOWING ANYMORE! It is here for informational
purposes and shows
Build status: Successful
If successful, the website and docs have been generated and the site has been
updated automatically.
If this failed, and you need to apply these changes by hand and update the site
manually, follow the instructions below. If the Jenkins job failed, skip to the
bottom o
JC created HBASE-17862:
--
Summary: Condition that always returns true
Key: HBASE-17862
URL: https://issues.apache.org/jira/browse/HBASE-17862
Project: HBase
Issue Type: Bug
Components: Client
Yi Liang created HBASE-17861:
Summary: Regionserver down when checking the permission of staging
dir if hbase.rootdir is on S3
Key: HBASE-17861
URL: https://issues.apache.org/jira/browse/HBASE-17861
Proje
+1 on branching (yay!)
I have EC2 resources for running ITBLL etc.
On Thu, Mar 30, 2017 at 5:07 PM, Stack wrote:
> Some notes on progress toward hbase2.
>
> Given that stability and performance are NOT emergent behaviors but rather
> projects unto themselves, my thought is that we commit all t
Build status: Aborted
If successful, the website and docs have been generated and the site has been
updated automatically.
If this failed, and you need to apply these changes by hand and update the site
manually, follow the instructions below. If the Jenkins job failed, skip to the
bottom of t
Ted Yu created HBASE-17860:
--
Summary: Implement secure native client connection
Key: HBASE-17860
URL: https://issues.apache.org/jira/browse/HBASE-17860
Project: HBase
Issue Type: Sub-task
Just checked and I don't see 'em there anymore. I assume someone else
has already done this :)
Enis Söztutar wrote:
Thanks for the cleanup. Indeed we should remove these from jira admin so
that they don't show up in auto-fill.
Enis
On Fri, Mar 31, 2017 at 8:34 AM, Stack wrote:
On Thu, Mar
Thanks for the cleanup. Indeed we should remove these from jira admin so
that they don't show up in auto-fill.
Enis
On Fri, Mar 31, 2017 at 8:34 AM, Stack wrote:
> On Thu, Mar 30, 2017 at 7:02 PM, Duo Zhang wrote:
>
> > There are plenty of issues which are assigned a version called '2.0' OR
>
On Thu, Mar 30, 2017 at 7:02 PM, Duo Zhang wrote:
> There are plenty of issues which are assigned a version called '2.0' OR
> '2.0..'.
>
> The latter one is a typo I think. And for the former one, I think we should
> claim again that the first release for 2.x release line is 2.0.0, not 2.0.
> So
On Thu, Mar 30, 2017 at 6:22 PM, Enis Söztutar wrote:
> Thanks Stack for the update. +1 on branching as soon as possible. For
> getting aforementioned stability, we need to start rejecting patches/
> features from 2.0.0. Branching early gives us the option of gradually
> working towards that, but
Chia-Ping Tsai created HBASE-17859:
--
Summary: ByteBufferUtils#compareTo is wrong
Key: HBASE-17859
URL: https://issues.apache.org/jira/browse/HBASE-17859
Project: HBase
Issue Type: Bug
Build status: Successful
If successful, the website and docs have been generated. To update the live
site, follow the instructions below. If failed, skip to the bottom of this
email.
Use the following commands to download the patch and apply it to a clean branch
based on origin/asf-site. If yo
+1 on early branch, and count me in for the coming stability/perf projects
(smile).
Best Regards,
Yu
On 31 March 2017 at 09:22, Enis Söztutar wrote:
> Thanks Stack for the update. +1 on branching as soon as possible. For
> getting aforementioned stability, we need to start rejecting patches/
>
Duo Zhang created HBASE-17858:
-
Summary: Update refguide about the IS annotation if necessary
Key: HBASE-17858
URL: https://issues.apache.org/jira/browse/HBASE-17858
Project: HBase
Issue Type: Su
Duo Zhang created HBASE-17857:
-
Summary: Remove IS annotations from IA.Public classes
Key: HBASE-17857
URL: https://issues.apache.org/jira/browse/HBASE-17857
Project: HBase
Issue Type: Sub-task
copy that. Thanks for the reminder.
On 2017-03-31 10:02 (+0800), Duo Zhang wrote:
> There are plenty of issues which are assigned a version called '2.0' OR
> '2.0..'.
>
> The latter one is a typo I think. And for the former one, I think we should
> claim again that the first release for 2.x rel
30 matches
Mail list logo