Re: Slack Team Invitation Request
FYI, slack participation is not at all required for community participation. This mailing list is your best bet for getting involved. You have a ticket, feature, or bug you've got your eyes on? -n On Fri, Nov 11, 2016 at 2:43 PM, Lijun Tang wrote: > Hi, > > I am interested in contributing to HBase, but I don't have access to the > Slack team for Hbase. > Can you send me an invitation? > > Thanks, > Lijun Tang >
[jira] [Created] (HBASE-17084) Delete HMerge (dead code)
Appy created HBASE-17084: Summary: Delete HMerge (dead code) Key: HBASE-17084 URL: https://issues.apache.org/jira/browse/HBASE-17084 Project: HBase Issue Type: Bug Reporter: Appy Assignee: Appy Priority: Trivial HMerge isn't used anywhere. Can we delete it? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-17083) Enable hedged reads by default in hbase-2.0.0
stack created HBASE-17083: - Summary: Enable hedged reads by default in hbase-2.0.0 Key: HBASE-17083 URL: https://issues.apache.org/jira/browse/HBASE-17083 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: stack Assignee: stack Priority: Critical Fix For: 2.0.0 Hedged reads came in in hadoop-2.4. hbase-2.0.0 requires a later version so we can expect support to be preseent. This issue is about a bit of testing to show defined benefit when hedged reads are on and then enabling them by default in hbase-2.0.0. See http://hbase.apache.org/book.html#_hedged_reads for current state of the doc. This issue came up in conversation a few of us were having Thursday and then Lars George started asking me their state in the last 24 hours. Assigning myself to do the bit of testing and enabling. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-17082) ForeignExceptionUtil isn’t packaged when building shaded protocol with -Pcompile-protocol
ChiaPing Tsai created HBASE-17082:
-
Summary: ForeignExceptionUtil isn’t packaged when building shaded
protocol with -Pcompile-protocol
Key: HBASE-17082
URL: https://issues.apache.org/jira/browse/HBASE-17082
Project: HBase
Issue Type: Bug
Reporter: ChiaPing Tsai
The source folder will be replaced from src/main/java to
project.build.directory/protoc-generated-sources when building shaded protocol
with -Pcompile-protocol, but we do not copy the ForeignExceptionUtil. So the
final jar lacks the ForeignExceptionUtil and it causes the test error for
hbase-client and hbase-server.
{noformat}
[ERROR]
/testptch/hbase/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java:[169,36]
cannot find symbol
symbol: class ForeignExceptionUtil
location: package org.apache.hadoop.hbase.util
[ERROR]
/testptch/hbase/hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterRpcServices.java:[100,36]
cannot find symbol
symbol: class ForeignExceptionUtil
location: package org.apache.hadoop.hbase.util
[ERROR]
/testptch/hbase/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java:[2144,17]
cannot find symbol
symbol: variable ForeignExceptionUtil
location: class org.apache.hadoop.hbase.regionserver.HRegionServer
[ERROR]
/testptch/hbase/hbase-server/src/main/java/org/apache/hadoop/hbase/master/MasterRpcServices.java:[938,32]
cannot find symbol
symbol: variable ForeignExceptionUtil
location: class org.apache.hadoop.hbase.master.MasterRpcServices
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: About time for another 0.98 RC - delay until early December
While reviewing branch-1 history for possible inclusion in 0.98 I found HBASE-16450 and HBASE-16947. Nice! I will have the backport of these tested early next week, but then am off on vacation without access to any computer except my phone until the beginning of December. Unless someone would like to step forward and volunteer to run a 0.98 release in my absence, let's just wait until then.I think that is fitting - one more 0.98 release in 2016, perhaps the final one. (Depends if someone wants to pick up the torch and carry it in 2017 and beyond.) So look for a 0.98 RC in early December. If at all possible I will include this nice improvement to replication tooling as well as the other applicable replication metrics/tooling improvements and bugfixes like HBASE-16870. On Wed, Nov 9, 2016 at 12:24 PM, Andrew Purtell wrote: > I will roll 0.98.24 RC0 later this week. There are 19 resolved issues > against it, a good number. I will make a pass over open issues and > relevant commits on branch-1 this week as well. > > Please consider voting on it. > > -- > Best regards, > >- Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
[jira] [Created] (HBASE-17081) Flush the entire CompactingMemStore content to disk
Anastasia Braginsky created HBASE-17081: --- Summary: Flush the entire CompactingMemStore content to disk Key: HBASE-17081 URL: https://issues.apache.org/jira/browse/HBASE-17081 Project: HBase Issue Type: Sub-task Reporter: Anastasia Braginsky Assignee: Anastasia Braginsky Part of CompactingMemStore's memory is held by an active segment, and another part is divided between immutable segments in the compacting pipeline. Upon flush-to-disk request we want to flush all of it to disk, in contrast to flushing only tail of the compacting pipeline. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [DISCUSS] No regions on Master node in 2.0
Thanks Stack and Enis. I concur, it's hard to say for those not intimate with the new code. In the absence of more information, intuition says master carries meta to avoid a whole class of problems. On Fri, Nov 11, 2016 at 3:27 PM, Enis Söztutar wrote: > Thanks Stack for reviving this. > > How to move forward here? The Pv2 master is almost done. An ITBLL bakeoff > > of new Pv2 based assign vs a Master that exclusively hosts hbase:meta? > > > > > I think we have to evaluate whether the new pv2 master works with remote > meta > updates and the fact that those updates can fail partially or succeed > without the > client getting the reply, etc. Sorry it has been some time I've looked at > the design. > Actually what would be very good is to have a design overview / write up of > the pv2 > in its current / final form so that we can evaluate. Last time I've looked > there was no > detailed design doc at all. > > > > St.Ack > > > > > > > > > > > > > > > > > > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
[jira] [Created] (HBASE-17080) rest.TestTableResource fails in master branch
Ted Yu created HBASE-17080:
--
Summary: rest.TestTableResource fails in master branch
Key: HBASE-17080
URL: https://issues.apache.org/jira/browse/HBASE-17080
Project: HBase
Issue Type: Test
Reporter: Ted Yu
The test fails consistently.
{code}
testTableInfoPB(org.apache.hadoop.hbase.rest.TestTableResource) Time elapsed:
0.118 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<192.168.0.14:5055[8]> but
was:<192.168.0.14:5055[5]>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at
org.apache.hadoop.hbase.rest.TestTableResource.checkTableInfo(TestTableResource.java:191)
at
org.apache.hadoop.hbase.rest.TestTableResource.testTableInfoPB(TestTableResource.java:272)
testTableInfoXML(org.apache.hadoop.hbase.rest.TestTableResource) Time elapsed:
0.084 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<192.168.0.14:5055[8]> but
was:<192.168.0.14:5055[5]>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at
org.apache.hadoop.hbase.rest.TestTableResource.checkTableInfo(TestTableResource.java:191)
at
org.apache.hadoop.hbase.rest.TestTableResource.testTableInfoXML(TestTableResource.java:255)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Successful: HBase Generate Website
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 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/403/artifact/website.patch.zip
| funzip > 5e91b45b166cd5a68457234f0a62ca1c2b5d9211.patch
git fetch
git checkout -b asf-site-5e91b45b166cd5a68457234f0a62ca1c2b5d9211
origin/asf-site
git am --whitespace=fix 5e91b45b166cd5a68457234f0a62ca1c2b5d9211.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-5e91b45b166cd5a68457234f0a62ca1c2b5d9211 branch.
There are lots of spurious changes, such as timestamps and CSS styles in
tables, so a generic git diff is not very useful. 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 these
commands:
git commit --allow-empty -m "Empty commit" # to work around a current ASF
INFRA bug
git push origin asf-site-5e91b45b166cd5a68457234f0a62ca1c2b5d9211:asf-site
git checkout asf-site
git branch -D asf-site-5e91b45b166cd5a68457234f0a62ca1c2b5d9211
Changes take a couple of minutes to be propagated. You can verify whether they
have been propagated by looking at the Last Published date at the bottom of
http://hbase.apache.org/. It should match the date in the index.html on the
asf-site branch in Git.
As a courtesy- reply-all to this email to let other committers know you pushed
the site.
If failed, see https://builds.apache.org/job/hbase_generate_website/403/console
[jira] [Created] (HBASE-17079) HBase buid fails on windows, hbase-archetype-builder is reason for failure
Arshad Mohammad created HBASE-17079:
---
Summary: HBase buid fails on windows, hbase-archetype-builder is
reason for failure
Key: HBASE-17079
URL: https://issues.apache.org/jira/browse/HBASE-17079
Project: HBase
Issue Type: Bug
Components: build
Environment: windows
Reporter: Arshad Mohammad
HBase buid fails on windows, hbase-archetype-builder is reason for failure.
Cygwin is installed so the shell scripts should execute successfully.
Here is build failure log
{code}
[INFO] Apache HBase - Archetype builder ... FAILURE [ 1.014 s]
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 06:13 min
[INFO] Finished at: 2016-11-12T18:12:26+05:30
[INFO] Final Memory: 235M/1012M
[INFO]
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.4.0:exec
(make-scripts-executable) on project hbase-archetype-builder: Command execution
failed. Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :hbase-archetype-builder
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-17078) hadoop.profile=3.0 profile build fails because hadoop-three-compat.xml does not exist
Arshad Mohammad created HBASE-17078:
---
Summary: hadoop.profile=3.0 profile build fails because
hadoop-three-compat.xml does not exist
Key: HBASE-17078
URL: https://issues.apache.org/jira/browse/HBASE-17078
Project: HBase
Issue Type: Bug
Components: build
Reporter: Arshad Mohammad
HBase build with hadoop.profile=3.0 is failing as
hbase-assembly\src\main\assembly\hadoop-three-compat.xml is not present.
{code}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 06:18 min
[INFO] Finished at: 2016-11-12T13:17:48+05:30
[INFO] Final Memory: 230M/1118M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default-cli) on
project hbase-assembly: Error reading assemblies: Error locating assembly
descriptor: src/main/assembly/hadoop-three-compat.xml
[ERROR]
[ERROR] [1] [INFO] Searching for file location:
D:\gitHome\hbaseMaster\hbase-assembly\src\main\assembly\hadoop-three-compat.xml
[ERROR]
[ERROR] [2] [INFO] File:
D:\gitHome\hbaseMaster\hbase-assembly\src\main\assembly\hadoop-three-compat.xml
does not exist.
[ERROR]
[ERROR] [3] [INFO] File:
D:\gitHome\hbaseMaster\src\main\assembly\hadoop-three-compat.xml does not exist.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :hbase-assembly
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
