Stephen Jiang | 27 Mar 08:14 2015
Picon

Question on HBaseFsck#checkRegionConsistency()

I am sure the following logic is a bug, but I'd like to know the rational
behind it so that I can fix it correctly.

In HBaseFsck#checkRegionConsistency(), we skip some regions that are
recently changed.  This is undesirable (at least in the situation I am
testing).

I can easily repro a problem by modifying an existing unit test -
TestHBaseFsck#testOverlapAndOrphan ()
- All unit test passed in 0 as the recently changed lagging time.  Default
is 60 seconds.  I change to default value - 60 seconds.
- then run the UT, the UT generates an orphaned HDFS region by removing
regioninfo in the dir
- the HBCK repair code creates a new region to repair the problem.
- However, it was skipped in HBaseFsck#checkRegionConsistency() and hence
the region is not assigned and added in META.
- At the end of UT, it failed because the repair did not fix the error.

{code}
private void checkRegionConsistency(final String key, final HbckInfo hbi)
    ...
    boolean recentlyModified = inHdfs && hbi.getModTime() + timelag >
System.currentTimeMillis();
    ...
    } else *if (recentlyModified) {*
*      LOG.warn("Region " + descriptiveName + " was recently modified --
skipping");*
*      return;*
    }
    ...
(Continue reading)

Ted Yu (JIRA | 27 Mar 02:35 2015
Picon

[jira] [Resolved] (HBASE-13327) Use Admin in ConnectionCache


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

Ted Yu resolved HBASE-13327.
----------------------------
    Resolution: Fixed

> Use Admin in ConnectionCache
> ----------------------------
>
>                 Key: HBASE-13327
>                 URL: https://issues.apache.org/jira/browse/HBASE-13327
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0, 1.0.1, 1.1.0
>            Reporter: Solomon Duskis
>            Assignee: Solomon Duskis
>             Fix For: 2.0.0, 1.0.1, 1.1.0
>
>         Attachments: HBASE-13327-addendum.patch, HBASE-13327.patch
>
>
> Replace HBaseAdmin usage with Admin in ConnectionCache and users of ConnectionCache.

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

(Continue reading)

Jonathan Lawlor (JIRA | 27 Mar 00:22 2015
Picon

[jira] [Reopened] (HBASE-13303) Fix size calculation of results on the region server


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

Jonathan Lawlor reopened HBASE-13303:
-------------------------------------

> Fix size calculation of results on the region server
> ----------------------------------------------------
>
>                 Key: HBASE-13303
>                 URL: https://issues.apache.org/jira/browse/HBASE-13303
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client
>            Reporter: Lars Hofhansl
>            Assignee: Andrew Purtell
>             Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.12
>
>         Attachments: HBASE-13303-0.98.patch, HBASE-13303-0.98.patch, HBASE-13303-0.98.patch,
HBASE-13303-addendum-v1.patch, HBASE-13303.patch, HBASE-13303.patch, HBASE-13303.patch, TestResultSizeEstimation.java
>
>
> One of the problems in the parent is due to different size calculation between client and server when
HFilev3 is used.
> Since tags are _never_ shipped to the client in a scan, we can have special size function (or a flag on the
current one) that does not include the tags and the tags meta information (the length is what causes the
issue), so that client and server will always calculate the same size.
> I'll make a patch within the hour, unless somebody beats me to it.
> [~apurtell], FYI.
(Continue reading)

Jerry He (JIRA | 26 Mar 22:42 2015
Picon

[jira] [Created] (HBASE-13345) Fix LocalHBaseCluster so that different region server impl can be used for different slaves

Jerry He created HBASE-13345:
--------------------------------

             Summary: Fix LocalHBaseCluster so that different region server impl can be used for different slaves
                 Key: HBASE-13345
                 URL: https://issues.apache.org/jira/browse/HBASE-13345
             Project: HBase
          Issue Type: Improvement
            Reporter: Jerry He
            Assignee: Jerry He
            Priority: Minor

LocalHBaseCluster and MiniHBaseCluster allow plugging in custom region server implementations.
This JIRA will fix a loophole so that different implementations can be used for different slaves. 
For example, MyRegionServer1 for slave1, MyRegionServer1 for slave2.
Or  MyRegionServer1 for slave1,  All other slaves use the default.

This will help targeted testing using MiniHBaseCluster.

I am working on a unit test for HBASE-13317.  This fix will be useful..

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

Sean Busbey (JIRA | 26 Mar 21:06 2015
Picon

[jira] [Created] (HBASE-13344) Add enforcer rule that matches our JDK support statement

Sean Busbey created HBASE-13344:
-----------------------------------

             Summary: Add enforcer rule that matches our JDK support statement
                 Key: HBASE-13344
                 URL: https://issues.apache.org/jira/browse/HBASE-13344
             Project: HBase
          Issue Type: Improvement
          Components: build
            Reporter: Sean Busbey
            Priority: Minor
             Fix For: 2.0.0

The [ref guide gives a list of JDKs that we expect our hbase versions to work with at runtime|].

Let's add in the extra-enforcer-rules mojo and start using [the bytecode version 
rule|http://mojo.codehaus.org/extra-enforcer-rules/enforceBytecodeVersion.html] to make sure
that the result of our builds on a given branch won't fail out because of a misconfigured target jdk version
(or a dependency that targets a later jdk).

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

Sean Busbey (JIRA | 26 Mar 20:53 2015
Picon

[jira] [Created] (HBASE-13343) Use a custom maven Enforcer rule to ban Hadoop annotations

Sean Busbey created HBASE-13343:
-----------------------------------

             Summary: Use a custom maven Enforcer rule to ban Hadoop annotations
                 Key: HBASE-13343
                 URL: https://issues.apache.org/jira/browse/HBASE-13343
             Project: HBase
          Issue Type: Improvement
          Components: build
            Reporter: Sean Busbey
            Assignee: Sean Busbey
            Priority: Minor
             Fix For: 2.0.0

Add a custom maven enforcer plugin rule that fails the build if we make use of the
org.apache.hadoop.classification annotations instead of the hbase ones.

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

Elliott Clark (JIRA | 26 Mar 18:34 2015
Picon

[jira] [Created] (HBASE-13342) Fix incorrect interface annotations

Elliott Clark created HBASE-13342:
-------------------------------------

             Summary: Fix incorrect interface annotations
                 Key: HBASE-13342
                 URL: https://issues.apache.org/jira/browse/HBASE-13342
             Project: HBase
          Issue Type: Improvement
            Reporter: Elliott Clark
            Assignee: Elliott Clark

Still some old annotations. Have slipped in. Lets remove them and add in a patch check for them.

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

Andrew Purtell | 26 Mar 18:26 2015
Picon

[ANNOUNCE] Sean Busbey joins the Apache HBase PMC

On behalf of the Apache HBase PMC I"m pleased to announce that Sean Busbey
has accepted our invitation to become a PMC member on the Apache HBase
project. Sean has been an active and positive contributor in many areas,
including on project meta-concerns such as versioning, build
infrastructure, code reviews, etc. He's a natural and we're looking forward
to many more future contributions.

Welcome to the PMC, Sean!

--

-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Andrew Purtell (JIRA | 26 Mar 18:06 2015
Picon

[jira] [Created] (HBASE-13341) Add option to disable filtering on interface annotations for the API compatibility report

Andrew Purtell created HBASE-13341:
--------------------------------------

             Summary: Add option to disable filtering on interface annotations for the API compatibility report
                 Key: HBASE-13341
                 URL: https://issues.apache.org/jira/browse/HBASE-13341
             Project: HBase
          Issue Type: Improvement
            Reporter: Andrew Purtell
            Assignee: Andrew Purtell
            Priority: Minor
             Fix For: 2.0.0

The API compatibility checker script added in HBASE-12808 passes a file containing annotations to the
JavaACC tool. When JavaACC is invoked with that option it will filter out all interfaces that do not have
that annotation. We should add a command line option to the compatibility checker which turns off this
filtering in case we want to look at the impact of changes to all interfaces, even private ones.

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

Andrew Purtell (JIRA | 26 Mar 18:06 2015
Picon

[jira] [Created] (HBASE-13340) Include LimitedPrivate interfaces in the API compatibility report

Andrew Purtell created HBASE-13340:
--------------------------------------

             Summary: Include LimitedPrivate interfaces in the API compatibility report
                 Key: HBASE-13340
                 URL: https://issues.apache.org/jira/browse/HBASE-13340
             Project: HBase
          Issue Type: Improvement
            Reporter: Andrew Purtell
            Assignee: Andrew Purtell
            Priority: Minor
             Fix For: 2.0.0

The API compatibility checker script added in HBASE-12808 passes a file containing annotations to the
JavaACC tool. When JavaACC is invoked with that option it will filter out all interfaces that do not have
that annotation. Currently only Public interfaces are checked. We should add LimitedPrivate to the
annotation list, otherwise we will miss changes that impact coprocessors and other users of those interfaces.

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

Elliott Clark (JIRA | 26 Mar 17:03 2015
Picon

[jira] [Created] (HBASE-13339) Update default Hadoop version to 2.6.0

Elliott Clark created HBASE-13339:
-------------------------------------

             Summary: Update default Hadoop version to 2.6.0
                 Key: HBASE-13339
                 URL: https://issues.apache.org/jira/browse/HBASE-13339
             Project: HBase
          Issue Type: Bug
          Components: build
    Affects Versions: 2.0.0, 1.1.0
            Reporter: Elliott Clark
            Assignee: Elliott Clark

Current default Hadoop version is getting a little long in the tooth. We should update to the latest
version. The latest version is backwards compatible with 2.5.1's dfs and mr so this should be painless.

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


Gmane