BELUGA BEHR created HBASE-20321:
---
Summary: Review of MobFileCache Class
Key: HBASE-20321
URL: https://issues.apache.org/jira/browse/HBASE-20321
Project: HBase
Issue Type: Improvement
Agreed.
Always best to build both Hadoop and HBase from source, specifying the
right version on the Maven command line as you do, and then take the extra
step to (re)package with native libs included.
On Thu, Mar 29, 2018 at 3:21 PM, rahul gidwani
wrote:
> Hi Andrew,
>
> I was thinking about do
Hi Andrew,
I was thinking about doing the same thing as you are doing now. It seems
like the safest approach, this will allow us to upgrade our hadoop binaries
independent of having to worry about doing anything with hbase.
I think this should be the recommended approach in building hbase as wel
BELUGA BEHR created HBASE-20320:
---
Summary: Review of MemcachedBlockCache
Key: HBASE-20320
URL: https://issues.apache.org/jira/browse/HBASE-20320
Project: HBase
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/HBASE-20318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-20318.
Resolution: Invalid
Fix Version/s: (was: 2.0.1)
(was: 1.5.
[
https://issues.apache.org/jira/browse/HBASE-20132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-20132.
---
Resolution: Fixed
Pushed to branch-2.0. Thanks for the patch [~andrewcheng] and for guidance
[~chia7712]
>
[
https://issues.apache.org/jira/browse/HBASE-20132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reopened HBASE-20132:
---
Reopened to backport to branch-2.0.
> Change the "KV" to "Cell" for web UI
> ---
FWIW, I build Hadoop and HBase binary tarballs. As a post build step, I
extract lib/native/ from the Hadoop tarball, extract the HBase tarball,
copy Hadoop's lib/native/ to HBase's lib/native/ e.g.
cp -a hadoop-2.7.5/lib/native hbase-1.4.2/lib/native/Linux-amd64-64
(you can learn your platfor
It was an interesting experiment but we had more active committers at that
time. Now the would-be owners are more likely to be a bottleneck (due to
limited bandwidth for review) than an aid.
On Wed, Mar 28, 2018 at 7:42 AM, Sean Busbey wrote:
> In late 2012 we tried an experiment where folks vo
stack created HBASE-20319:
-
Summary: Run a check that branch-2.0 has all it needs from branch-2
Key: HBASE-20319
URL: https://issues.apache.org/jira/browse/HBASE-20319
Project: HBase
Issue Type: Sub-
Andrew Purtell created HBASE-20318:
--
Summary: Lower "Set storagePolicy=XXX for path=YYY" INFO level
logging to DEBUG
Key: HBASE-20318
URL: https://issues.apache.org/jira/browse/HBASE-20318
Project: H
stack created HBASE-20317:
-
Summary: Backport HBASE-20261 "Table page (table.jsp) in Master UI
does not show replicaIds for hbase meta table" to branch-1
Key: HBASE-20317
URL: https://issues.apache.org/jira/browse/HBASE-2
stack created HBASE-20316:
-
Summary: Backport HBASE-20229
"ConnectionImplementation.locateRegions() returns duplicated entries when
region replication is on" to branch-1
Key: HBASE-20316
URL: https://issues.apache.org/ji
Andrew Purtell created HBASE-20315:
--
Summary: Document post release process steps for RM
Key: HBASE-20315
URL: https://issues.apache.org/jira/browse/HBASE-20315
Project: HBase
Issue Type: Ta
Filed HBASE-20314.
2018-03-29 22:21 GMT+08:00 Sean Busbey :
> please make sure there's a jira tracking the strange error so that I
> can dig into it later.
>
> On Thu, Mar 29, 2018 at 9:19 AM, 张铎(Duo Zhang)
> wrote:
> > It seems that all builds on H0 have failed with strange error. Exclude it
>
Duo Zhang created HBASE-20314:
-
Summary: Pre commit build for master branch fails
Key: HBASE-20314
URL: https://issues.apache.org/jira/browse/HBASE-20314
Project: HBase
Issue Type: Bug
Seems not related to the build machine, it also failed on H15 just now.
And seems the problem only happens for master branch, for branch-1 it works
well
https://builds.apache.org/job/PreCommit-HBASE-Build/12205/
2018-03-29 22:21 GMT+08:00 Sean Busbey :
> please make sure there's a jira tracking
I can't find anything written down; but I just did a couple of simple
mail searches.
Probably this should build on HBASE-15317. How about I try to
incorporate a note about it when implementing there and you can keep
me honest with a review?
On Thu, Mar 29, 2018 at 9:24 AM, Josh Elser wrote:
> We
Welp, the announce message got bounced anyways, so it didn't actually go
out.
Is this written down somewhere that I missed? I was just going off of
the standard ASF-release knowledge I have floating around. If not,
should I add it to the book somewhere?
Thanks Sean.
On 3/28/18 8:12 PM, Sean
please make sure there's a jira tracking the strange error so that I
can dig into it later.
On Thu, Mar 29, 2018 at 9:19 AM, 张铎(Duo Zhang) wrote:
> It seems that all builds on H0 have failed with strange error. Exclude it
> from the build machines to see if it could help.
It seems that all builds on H0 have failed with strange error. Exclude it
from the build machines to see if it could help.
Peter Somogyi created HBASE-20313:
-
Summary: Canary documentation is incorrect in reference guide
Key: HBASE-20313
URL: https://issues.apache.org/jira/browse/HBASE-20313
Project: HBase
Issue
Xiang Wang created HBASE-20312:
--
Summary: CCSMap: A faster, GC-friendly, less memory Concurrent Map
for memstore
Key: HBASE-20312
URL: https://issues.apache.org/jira/browse/HBASE-20312
Project: HBase
23 matches
Mail list logo