[jira] [Created] (HBASE-15829) hbase.client.retries.number has different meanings in branch-1 and master

[Guanghao Zhang (JIRA)]

Guanghao Zhang created HBASE-15829:
--

 Summary: hbase.client.retries.number has different meanings in 
branch-1 and master
 Key: HBASE-15829
 URL: https://issues.apache.org/jira/browse/HBASE-15829
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 2.0.0
Reporter: Guanghao Zhang
Priority: Minor


The comment of hbase.client.retries.number is:
{code}
  /**  
   * Parameter name for maximum retries, used as maximum for all retryable
   * operations such as fetching of the root region from root region server,
   * getting a cell's value, starting a row update, etc.
   */
  public static final String HBASE_CLIENT_RETRIES_NUMBER = 
"hbase.client.retries.number";
{code}

In branch-1, the max attempts number equals with hbase.client.retries.number. 
But in master, the max attempts number equals with hbase.client.retries.number 
+ 1.

For RpcRetryingCaller.
{code}
this.retries = retries; // branch-1
{code}
{code}
this.maxAttempts = retries + 1; // master
{code}

For AsyncProcess:
{code}
this.numTries = conf.getInt(HConstants.HBASE_CLIENT_RETRIES_NUMBER,
HConstants.DEFAULT_HBASE_CLIENT_RETRIES_NUMBER); // branch-1
{code}
{code}
// how many times we could try in total, one more than retry number
this.numTries = conf.getInt(HConstants.HBASE_CLIENT_RETRIES_NUMBER,
HConstants.DEFAULT_HBASE_CLIENT_RETRIES_NUMBER) + 1; // master
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-15828) fix extant findbug

[Mikhail Antonov (JIRA)]

Mikhail Antonov created HBASE-15828:
---

 Summary: fix extant findbug
 Key: HBASE-15828
 URL: https://issues.apache.org/jira/browse/HBASE-15828
 Project: HBase
  Issue Type: Bug
  Components: findbugs
Affects Versions: 1.3.0
 Environment: 
https://builds.apache.org/job/PreCommit-HBASE-Build/1889/artifact/patchprocess/branch-findbugs-hbase-client-warnings.html
Reporter: Mikhail Antonov
 Fix For: 1.3.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (HBASE-13783) Improve error message "Could not seek StoreFileScanner" to indicate that issue could be a bad disk

[Appy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-13783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Appy resolved HBASE-13783.
--
Resolution: Duplicate

> Improve error message "Could not seek StoreFileScanner" to indicate that 
> issue could be a bad disk
> --
>
> Key: HBASE-13783
> URL: https://issues.apache.org/jira/browse/HBASE-13783
> Project: HBase
>  Issue Type: Improvement
>Reporter: Appy
>Priority: Minor
> Attachments: HBASE-13783.patch
>
>
> Feedback from customers.
> Following error could mean that a disk has gone bad. We have seen many users 
> confused by this error. 
> java.io.IOException: Could not seek StoreFileScanner[HFileScanner for reader 
> reader=hdfs:///843914879034b56117dfa6b7f3c8383d/content/b6f5e9961d2d4578aea3917c0637bb7c



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-15827) Backport HBASE-15125 'HBaseFsck's adoptHdfsOrphan function creates region with wrong end key boundary' to 1.1 and 1.2

[Ted Yu (JIRA)]

Ted Yu created HBASE-15827:
--

 Summary: Backport HBASE-15125 'HBaseFsck's adoptHdfsOrphan 
function creates region with wrong end key boundary' to 1.1 and 1.2
 Key: HBASE-15827
 URL: https://issues.apache.org/jira/browse/HBASE-15827
 Project: HBase
  Issue Type: Bug
Reporter: Ted Yu


There is a bug in HBaseFsck's adoptHdfsOrphan function.At the last of this 
function will create a region,which want to cover all the orphan regions.But 
the end key of this new region was set incorrectly.Correct region's boundary 
should be [startKey,endKey),but this function create a region with boundary of 
[startKey,endKey],this bug will leads to scan operation omit some data.
I think we should create the region like bellow,
{code}
// create new region on hdfs. move data into place.
HRegionInfo hri = new HRegionInfo(template.getTableName(), 
orphanRegionRange.getFirst(),
Bytes.add(orphanRegionRange.getSecond(), new byte[1]));
{code}

This is to backport to branch-1.1 and branch-1.2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-15826) Clean up ASF license issues

[Elliott Clark (JIRA)]

Elliott Clark created HBASE-15826:
-

 Summary: Clean up ASF license issues
 Key: HBASE-15826
 URL: https://issues.apache.org/jira/browse/HBASE-15826
 Project: HBase
  Issue Type: Sub-task
Reporter: Elliott Clark






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-15825) Fix the null pointer in DynamicLogicExpressionSuite

[Zhan Zhang (JIRA)]

Zhan Zhang created HBASE-15825:
--

 Summary: Fix the null pointer in DynamicLogicExpressionSuite
 Key: HBASE-15825
 URL: https://issues.apache.org/jira/browse/HBASE-15825
 Project: HBase
  Issue Type: Sub-task
Reporter: Zhan Zhang


It only happens in test cases. Not sure why it is not caught. Will submit patch 
soon



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-15824) LocalHBaseCluster gets bind exception in master info port

[Enis Soztutar (JIRA)]

Enis Soztutar created HBASE-15824:
-

 Summary: LocalHBaseCluster gets bind exception in master info port
 Key: HBASE-15824
 URL: https://issues.apache.org/jira/browse/HBASE-15824
 Project: HBase
  Issue Type: Bug
Reporter: Enis Soztutar


This is seen from Phoenix, since we already configure the ports in 
hbase-site.xml under hbase-server/src/test/resources. 

But this is also important for other {{hbase-testing-util}} consumers. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-15823) Use call once for user util

[Elliott Clark (JIRA)]

Elliott Clark created HBASE-15823:
-

 Summary: Use call once for user util
 Key: HBASE-15823
 URL: https://issues.apache.org/jira/browse/HBASE-15823
 Project: HBase
  Issue Type: Sub-task
Reporter: Elliott Clark
Assignee: Elliott Clark


Faster less locking and more correct.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-15822) Move to the latest docker base image

[Elliott Clark (JIRA)]

Elliott Clark created HBASE-15822:
-

 Summary: Move to the latest docker base image
 Key: HBASE-15822
 URL: https://issues.apache.org/jira/browse/HBASE-15822
 Project: HBase
  Issue Type: Sub-task
Reporter: Elliott Clark


The base docker image got an update to use chef to set everything up. It 
changes some locations but should be pretty easy to migrate to.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] First release candidate for HBase 1.1.5 (RC0) is available

[Sean Busbey]

On Fri, May 13, 2016 at 9:18 AM, Nick Dimiduk  wrote:
> On Thu, May 12, 2016 at 7:03 PM, Sean Busbey  wrote:
>
>> [1]:
>>
>> I now realize the issue with using gpg printed md5: the md5 files end up in
>> a different format for dist.apache than the md5 files pushed into
>> repository.apache.
>> the latter match md5sum / md5 -r output.
>>
>> It's not a big deal, just some added noise in the scripting I use to
>> go through checking
>> all of the checksum files.
>>
>
> Shall we have a follow-on to HBASE-15738 for using md5sum / md5 -r? Might
> as well make it simpler for folks consuming our stuff, and the gnupg format
> output is in the mds file for those who prefer that.
>
>

Maybe. So we'd essentially say something like "this is how you verify
using only gpg for signatures and for a couple of example hash algos"
and then a different "this is how you verify using md5sum"?

I dunno if it's worth having two verification instructions for
downloads just so verification of RCs is slightly simpler, since
hopefully the former is much more common than the latter.

[RESULT] [VOTE] First release candidate for HBase 1.1.5 (RC0) is available

[Nick Dimiduk]

With 4 binding +1's and 5 +1's total, no -0 and no -1, this vote passes.

Thanks to everyone who took the time to vote on this release. Hope to see
you all again next month.

-n


On Fri, May 13, 2016 at 9:18 AM, Nick Dimiduk  wrote:

> On Thu, May 12, 2016 at 7:03 PM, Sean Busbey  wrote:
>
>> [1]:
>>
>> I now realize the issue with using gpg printed md5: the md5 files end up
>> in
>> a different format for dist.apache than the md5 files pushed into
>> repository.apache.
>> the latter match md5sum / md5 -r output.
>>
>> It's not a big deal, just some added noise in the scripting I use to
>> go through checking
>> all of the checksum files.
>>
>
> Shall we have a follow-on to HBASE-15738 for using md5sum / md5 -r? Might
> as well make it simpler for folks consuming our stuff, and the gnupg format
> output is in the mds file for those who prefer that.
>
> On Sun, May 8, 2016 at 9:23 PM, Nick Dimiduk  wrote:
>> > *** Please note that my key expired since the previous release. I have
>> > updated its expiration, pushed to pgp.mit.edu, updated the KEYS file
>> linked
>> > below, and attempted to force an update on id.apache.org. I don't know
>> how
>> > long it will take for people.apache.org to refresh. ***
>> >
>> > *** Please note that this voting window is slightly shorter than the
>> > customary one week so that we have time for an RC1 before HBaseCon, if
>> > necessary. ***
>> >
>> > I'm happy to announce the first release candidate of HBase 1.1.5
>> (HBase-1.1
>> > .5RC0) is available for download at
>> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.5RC0/
>> >
>> > Maven artifacts are also available in the staging repository
>> > https://repository.apache.org/content/repositories/orgapachehbase-1136/
>> >
>> > Artifacts are signed with my code signing subkey 0xAD9039071C3489BD,
>> > available in the Apache keys directory
>> > https://people.apache.org/keys/committer/ndimiduk.asc and in our KEYS
>> file
>> > http://www-us.apache.org/dist/hbase/KEYS.
>> >
>> > There's also a signed tag for this release at
>> >
>> https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=tag;h=92323e8e630e46d277ab2e8ebd34b91ab5d597d5
>> >
>> > The detailed source and binary compatibility report vs 1.1.4 has been
>> > published for your review, at
>> > http://home.apache.org/~ndimiduk/1.1.4_1.1.5RC0_compat_report.html
>> >
>> > HBase 1.1.5 is the fifth patch release in the HBase 1.1 line,
>> continuing on
>> > the theme of bringing a stable, reliable database to the Hadoop and
>> NoSQL
>> > communities. This release includes over 20 bug fixes since the 1.1.4
>> > release. Notable correctness fixes
>> > include HBASE-15234, HBASE-15295, HBASE-15325, HBASE-15622, and
>> HBASE-15645.
>> >
>> > The full list of fixes included in this release is available at
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753=12335058
>> > and and in the CHANGES.txt file included in the distribution.
>> >
>> > Please try out this candidate and vote +/-1 by 23:59 Pacific time on
>> > Thursday, 2016-05-12 as to whether we should release these artifacts as
>> > HBase 1.1.5.
>> >
>> > Thanks,
>> > Nick
>>
>
>

Re: [VOTE] First release candidate for HBase 1.1.5 (RC0) is available

[Nick Dimiduk]

On Thu, May 12, 2016 at 7:03 PM, Sean Busbey  wrote:

> [1]:
>
> I now realize the issue with using gpg printed md5: the md5 files end up in
> a different format for dist.apache than the md5 files pushed into
> repository.apache.
> the latter match md5sum / md5 -r output.
>
> It's not a big deal, just some added noise in the scripting I use to
> go through checking
> all of the checksum files.
>

Shall we have a follow-on to HBASE-15738 for using md5sum / md5 -r? Might
as well make it simpler for folks consuming our stuff, and the gnupg format
output is in the mds file for those who prefer that.

On Sun, May 8, 2016 at 9:23 PM, Nick Dimiduk  wrote:
> > *** Please note that my key expired since the previous release. I have
> > updated its expiration, pushed to pgp.mit.edu, updated the KEYS file
> linked
> > below, and attempted to force an update on id.apache.org. I don't know
> how
> > long it will take for people.apache.org to refresh. ***
> >
> > *** Please note that this voting window is slightly shorter than the
> > customary one week so that we have time for an RC1 before HBaseCon, if
> > necessary. ***
> >
> > I'm happy to announce the first release candidate of HBase 1.1.5
> (HBase-1.1
> > .5RC0) is available for download at
> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.1.5RC0/
> >
> > Maven artifacts are also available in the staging repository
> > https://repository.apache.org/content/repositories/orgapachehbase-1136/
> >
> > Artifacts are signed with my code signing subkey 0xAD9039071C3489BD,
> > available in the Apache keys directory
> > https://people.apache.org/keys/committer/ndimiduk.asc and in our KEYS
> file
> > http://www-us.apache.org/dist/hbase/KEYS.
> >
> > There's also a signed tag for this release at
> >
> https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=tag;h=92323e8e630e46d277ab2e8ebd34b91ab5d597d5
> >
> > The detailed source and binary compatibility report vs 1.1.4 has been
> > published for your review, at
> > http://home.apache.org/~ndimiduk/1.1.4_1.1.5RC0_compat_report.html
> >
> > HBase 1.1.5 is the fifth patch release in the HBase 1.1 line, continuing
> on
> > the theme of bringing a stable, reliable database to the Hadoop and NoSQL
> > communities. This release includes over 20 bug fixes since the 1.1.4
> > release. Notable correctness fixes
> > include HBASE-15234, HBASE-15295, HBASE-15325, HBASE-15622, and
> HBASE-15645.
> >
> > The full list of fixes included in this release is available at
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753=12335058
> > and and in the CHANGES.txt file included in the distribution.
> >
> > Please try out this candidate and vote +/-1 by 23:59 Pacific time on
> > Thursday, 2016-05-12 as to whether we should release these artifacts as
> > HBase 1.1.5.
> >
> > Thanks,
> > Nick
>

Re: [DISCUSS] Using the new 'help wanted' tool from comdev

[Sean Busbey]

On Thu, May 12, 2016 at 10:10 PM, Stack  wrote:
> On Thu, May 12, 2016 at 8:37 PM, Daniel Vimont  wrote:
>
>
>
>> With regard to recruiting new contributors, I'll just toss out a question
>> which I hope does not give offense: What can be done to encourage more
>> gender-diversity in this project (and projects like it)?
>>
>>
> Thank you for raising this 'awkward' question up here on the dev list.
>
> Our ratio is awful. I'm ashamed to cite numbers.
>
> I don't know what we can do to encourage participation. I'd be interested
> in any ideas others might have and would be up for acting them to try and
> make redress.
>


Yes, thank you Daniel. This is an issue that weighs on me. The ASF in
general has a demographic problem, and our particular corner of it
seems particularly homogenous.

I'm a firm believer in "can't fix what you don't measure." Stack do
you have numbers from somewhere? I was looking at ways we could run an
opt-in poll to get an idea of how our community looks outside of what
I can already see in the committer  and PMC ranks from meetups.

I don't think there are any fast answers to this issue, but I think
there are some things we could try doing that would help the project
generally:

1) We could use better student outreach. Presuming we come up with
some materials for trying to get students involved overall, we should
get a few folks go out of our way to present those materials to
student groups that try to provide space for folks who aren't in our
dominant demographic.

2) Similar to #1, there are meetups (at least in my area) that try to
make things accessible and comfortable for e.g. women. We could make a
habit of presenting to these meetups in addition to our normal "big
data" themed groups.

3) I've noticed that none of the meetups or conferences where I see
HBase stuff have child care options. This doesn't only impact women,
but it disproportionately impacts them due to societal expectations.
We the community could start pushing folks to have something and we
the PMC could perhaps push this a little harder, like we do the need
for a Code of Conduct.

Successful: HBase Generate Website

[Apache Jenkins Server]

Build status: Successful

If successful, the website and docs have been generated. 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 you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/228/artifact/website.patch.zip
 | funzip > b353e388bb6bf315818fcde81f11131d6d539c70.patch
  git fetch
  git checkout -b asf-site-b353e388bb6bf315818fcde81f11131d6d539c70 
origin/asf-site
  git am --whitespace=fix b353e388bb6bf315818fcde81f11131d6d539c70.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local 
asf-site-b353e388bb6bf315818fcde81f11131d6d539c70 branch, and you can review 
the differences by running:

  git diff origin/asf-site

There are lots of spurious changes, such as timestamps and CSS styles in 
tables. To see a list of files that have been added, deleted, renamed, changed 
type, or are otherwise interesting, use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using this 
command:

  git push origin asf-site-b353e388bb6bf315818fcde81f11131d6d539c70:asf-site

Changes take a couple of minutes to be propagated. You can then remove your 
asf-site-b353e388bb6bf315818fcde81f11131d6d539c70 branch:

  git checkout asf-site && git branch -d 
asf-site-b353e388bb6bf315818fcde81f11131d6d539c70



If failed, see https://builds.apache.org/job/hbase_generate_website/228/console