I have no doubt that you've run the tests locally before announcing a
release as you're always a great RM boss. And this shows one value of
verifying release, that different voter has different environments.
Now I think the failures may be kerberos related, since I possibly has
changed some
Yu Li created HBASE-22219:
-
Summary: Backport HBASE-19049 to branch-1 to prevent DIRKRB-613
Key: HBASE-22219
URL: https://issues.apache.org/jira/browse/HBASE-22219
Project: HBase
Issue Type:
“However it's good to find the issue earlier if there
really is any, before release announced.”
I run the complete unit test suite before announcing a release candidate. Just
to be clear.
Totally agree we should get these problems sorted before an actual release. My
policy is to cancel a RC
Confirmed in 1.4.7 source the listed out cases passed (all in the 1st part
of hbase-server so the result comes out quickly.)... Also confirmed the
test ran order are the same...
Will try 1.5.0 again to prevent the environment difference caused by time.
If 1.5.0 still fails, will start to do the
That sounds good.
> On Apr 11, 2019, at 9:16 PM, Yu Li wrote:
>
> Fine, let's focus on verifying whether it's a real problem rather than
> arguing about wording, after all that's not my intention...
>
> As mentioned, I participated in the 1.4.7 release vote[1] and IIRC I was
> using the same
Fine, let's focus on verifying whether it's a real problem rather than
arguing about wording, after all that's not my intention...
As mentioned, I participated in the 1.4.7 release vote[1] and IIRC I was
using the same env and all tests passed w/o issue, that's where my concern
lies and the main
And if they pass in my environment , then what should we call it then. I have
no doubt you are seeing failures. Therefore can you please file JIRAs and
attach information that can help identify a fix. Thanks.
> On Apr 11, 2019, at 8:35 PM, Yu Li wrote:
>
> I ran the test suite with the
I ran the test suite with the -Dsurefire.rerunFailingTestsCount=2 option
and on two different env separately, so it sums up to 6 times stable
failure for each case, and from my perspective this is not flaky.
IIRC last time when verifying 1.4.7 on the same env no such issue observed,
will double
[
https://issues.apache.org/jira/browse/HBASE-8549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-8549.
--
Resolution: Implemented
I'll take your word for it [~gsbiju].
Implemented by HBASE-16942
> Integrate
[
https://issues.apache.org/jira/browse/HBASE-16513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
binlijin resolved HBASE-16513.
--
Resolution: Resolved
Fix Version/s: (was: 1.5.0)
(was: 3.0.0)
>
+1
Checked sums and signatures: ok
Apache RAT check: ok (8u172)
Build from source: ok (7u80)
Unit tests pass: ok (8u172)
1M row LTT: ok (8u172)
On Sun, Apr 7, 2019 at 12:03 PM Sean Busbey wrote:
> The first release candidate for HBase 1.2.12 is available for download:
>
>
Sakthi created HBASE-22218:
--
Summary: Shell throws "Unsupported Java version" when tried with
Java 11 (run-time)
Key: HBASE-22218
URL: https://issues.apache.org/jira/browse/HBASE-22218
Project: HBase
Xu Cang created HBASE-22217:
---
Summary: HBase shell command proposal : "rit assign all"
Key: HBASE-22217
URL: https://issues.apache.org/jira/browse/HBASE-22217
Project: HBase
Issue Type: New
Xu Cang created HBASE-22216:
---
Summary: "Waiting on master failover to complete" shows 30 to 40
time per millisecond
Key: HBASE-22216
URL: https://issues.apache.org/jira/browse/HBASE-22216
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Marc Spaggiari resolved HBASE-7297.
Resolution: Duplicate
Duplicate of HBASE-11780.
> Allow load balancer to
Sorry Sean I missed this email last week. Let me check now.
On Sun, Apr 7, 2019 at 12:03 PM Sean Busbey wrote:
> The first release candidate for HBase 1.2.12 is available for download:
>
> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.2.12RC0/
>
> Maven artifacts are also available in a
[
https://issues.apache.org/jira/browse/HBASE-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-3268.
---
Resolution: Incomplete
> Run balancer when a new node is added
>
Although branch-1 (1.5.0) is stalled on unit test issues I think we can
make progress on another, overdue release, the next 1.4.x, 1.4.10. Let me
start the work on the first release candidate of 1.4.10 Monday of next
week. If you have any pending work targeting branch-1.4 please try to get
it in
Josh Elser created HBASE-22215:
--
Summary: Backport MultiRowRangeFilter does not work with reverse
scans
Key: HBASE-22215
URL: https://issues.apache.org/jira/browse/HBASE-22215
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-22214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved HBASE-22214.
Resolution: Fixed
> [2.x] Backport missing filter improvements
>
The HBase QA, didn't list out a consolidated listed of failed UTs in a
recently submitted patch of mine. Just wanted to put this out here.
On Sat, Apr 6, 2019 at 4:37 AM 张铎(Duo Zhang) wrote:
> Oh shit, the default operation for merging is create a merge commit...
>
> Sorry about that, I should
Josh Elser created HBASE-22214:
--
Summary: [2.x] Backport missing filter improvements
Key: HBASE-22214
URL: https://issues.apache.org/jira/browse/HBASE-22214
Project: HBase
Issue Type: Bug
Ok. Let me pull the last 2.2 branch, build that, deploy and retry... I
might be able to let you know tomorrow morning.
Le jeu. 11 avr. 2019 à 14:19, Sean Busbey a écrit :
> Maybe worth trying out the HEAD of branch-2.2 prior to the next RC? That
> way if you hit a blocker like your current ones
[
https://issues.apache.org/jira/browse/HBASE-22213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Marc Spaggiari resolved HBASE-22213.
-
Resolution: Later
> Create a Java based BulkLoadPartitioner
>
Pardon, that git ref I failed to include below is commit 677ed9ef89 (HEAD
-> branch-1)
On Thu, Apr 11, 2019 at 12:14 PM Andrew Purtell wrote:
> Thanks for clarifying that this is not a foundation wide policy. It is my
> personal policy to cancel a vote whenever there is a veto, if the reason is
Thanks for clarifying that this is not a foundation wide policy. It is my
personal policy to cancel a vote whenever there is a veto, if the reason is
sound and technical and, presumably, repeatable, at least in the voter's
environment(s).
Circling back to the main topic, a unit test run of latest
Jean-Marc Spaggiari created HBASE-22213:
---
Summary: Create a Java based BulkLoadPartitioner
Key: HBASE-22213
URL: https://issues.apache.org/jira/browse/HBASE-22213
Project: HBase
Issue
Maybe worth trying out the HEAD of branch-2.2 prior to the next RC? That
way if you hit a blocker like your current ones we can fix them before RC
generation happens.
On Thu, Apr 11, 2019, 13:08 Jean-Marc Spaggiari
wrote:
> Thanks Guanghao.
>
> I'm having consistant issues with RC0. I had some
Just as a point of clarification, -1 votes on releases aren't vetos. ASF
policy requires release votes to be majority.
As release manager it's your perogative to cancel a vote for whatever
reason, but I don't want future RMs thinking they have to fail the vote
once there's a -1.
On Thu, Apr 11,
Thanks Guanghao.
I'm having consistant issues with RC0. I had some issues with a table this
morning. Dropped it, recreated it, made it clean, restart my application,
and I have again some inconsistencies on the regions. There is something
wrong somewhere. I'm not able to identify where, but I can
Done, please check
On Thu, 11 Apr 2019, 23:11 Da Zhou, wrote:
> Dear HBase Community,
>
> I saw the channel "https://apache-hbase.slack.com/; shared on the HBase
> Book. May I join the HBase Slack channel for easier communication?
>
> Thanks,
> Da
>
Dear HBase Community,
I saw the channel "https://apache-hbase.slack.com/; shared on the HBase
Book. May I join the HBase Slack channel for easier communication?
Thanks,
Da
Sorry for late... I am testing the ITBLL for 2.2.0 and it passed
yesterday. See https://issues.apache.org/jira/browse/HBASE-21886. I will
generate RC1 later. Thanks.
Jean-Marc Spaggiari 于2019年4月11日周四 下午10:52写道：
> Hi all,
>
> Any chance to get an updated RC soon?
>
> JM
>
> Le mar. 12 mars
Done. Add to HBase jira CONTRIBUTORS, too.
Manjeet Singh 于2019年4月12日周五 上午12:56写道：
> Hi
>
> Request you to please add me as well for contribute to Apache HBase.
> My id is manjeet.chand...@gmail.com
>
> Thanks
> Manjeet singh
>
> On Thu, 11 Apr 2019, 19:52 Guanghao Zhang, wrote:
>
> > Done.
I put back "1.6.0" for TinyLFU backport to branch-1, which I don't think
can happen in the near term because it depends on improvements to precommit
being in place first.
On Thu, Apr 11, 2019 at 9:37 AM Andrew Purtell
wrote:
> A helpful view for tracking 1.5.0 issues is
>
[
https://issues.apache.org/jira/browse/HBASE-21758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-21758.
Resolution: Won't Fix
Assignee: (was: Andrew Purtell)
Fix Version/s:
Hi
Request you to please add me as well for contribute to Apache HBase.
My id is manjeet.chand...@gmail.com
Thanks
Manjeet singh
On Thu, 11 Apr 2019, 19:52 Guanghao Zhang, wrote:
> Done. Add to HBase jira CONTRIBUTORS. Thanks.
>
> fei wen 于2019年4月11日周四 下午7:26写道：
>
> > Hi,
> > I want to
[
https://issues.apache.org/jira/browse/HBASE-17762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-17762.
Resolution: Incomplete
Assignee: (was: churro morales)
Fix Version/s:
[
https://issues.apache.org/jira/browse/HBASE-16594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-16594.
Resolution: Incomplete
Assignee: (was: binlijin)
Fix Version/s:
[
https://issues.apache.org/jira/browse/HBASE-15677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-15677.
Resolution: Incomplete
Assignee: (was: Mikhail Antonov)
Fix Version/s:
[
https://issues.apache.org/jira/browse/HBASE-21013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-21013.
Resolution: Incomplete
Assignee: (was: Mingdao Yang)
> Backport "read part" of
Latest results look good and discussion points have been addressed.
--
Best regards,
Andrew
Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
- A23, Crosstalk
A helpful view for tracking 1.5.0 issues is
https://issues.apache.org/jira/projects/HBASE/versions/12340316 .
I deleted fixversions "1.5.1" and "1.6.0" and had JIRA rewrite them back to
"1.5.0" so you won't be confused by JIRA thinking 1.5.0 is in released
state. All open and pending branch-1
Josh Elser created HBASE-22212:
--
Summary: Backport missing filter improvements
Key: HBASE-22212
URL: https://issues.apache.org/jira/browse/HBASE-22212
Project: HBase
Issue Type: Bug
No need to renumber as it turns out because the fourth 1.5.0 RC was just
vetoed. I sent another email about the resulting pause on release attempts.
Please disregard this thread.
> On Apr 10, 2019, at 6:22 PM, Andrew Purtell wrote:
>
> I am not anticipating a 1.5.1 release unless we need a
All,
HBase submits a report to the ASF board once a quarter, to inform the board
about project health. I'm sending the report to the user@ and dev@ mailing
lists because you are the project, and for transparency. If you have any
questions about the report or the running of the project, you can
I have tried to release four 1.5.0 candidates from head of branch-1.
Some veto votes were cast for compatibility issues. This was fine.
Others are for unit test results that do not reproduce locally for me. I do not
have the ability or bandwidth to fix tests which do not fail reliably for me.
There are two failure cases it looks like. And this looks like flakes.
The wrong FS assertions are not something I see when I run these tests myself.
I am not able to investigate something I can’t reproduce. What I suggest is
since you can reproduce do a git bisect to find the commit that
Trying to bulkload a single HFile in a single region empty table on a
sleeping 2.2.0 cluster, I get this:
2019-04-11 11:22:40,594 INFO [LoadIncrementalHFiles-0] compress.CodecPool:
Got brand-new decompressor [.snappy]
2019-04-11 11:22:40,632 INFO [LoadIncrementalHFiles-0]
Scanning the tables from the shell returns this:
ERROR Java::JavaIo::IOException: Unable to find region for
\x03\x02\x03\x01\x01\x02\x01\x01\x01\x01\x04\x00\x04\x02\x00\x00\x02\x01\x00\x00\x01
in stones5
Scanning the meta table returns 22regions (which seems to be normal).
Output is there:
Build status: Still Failing
The HBase website has not been updated to incorporate HBase commit
${CURRENT_HBASE_COMMIT}.
See https://builds.apache.org/job/hbase_generate_website/1642/console
Hi all,
Any chance to get an updated RC soon?
JM
Le mar. 12 mars 2019 à 12:23, Sean Busbey a écrit :
> quick follow-up here. the full version info is in fact missing the
> revision:
>
> hbase-2.2.0 busbey$ ./bin/hbase version
> HBase 2.2.0
> Source code repository
>
Hi all,
I don't know how i ended up in this stage, but I cleared /hbase in both ZK
and HDFS 3 days ago. created 3 brand new tables, started to put some data
on them. Twice a day I run a split command, to get a better spread.
After 3 days I have a lot of regions overlaps. HBCK output is there:
Done. Add to HBase jira CONTRIBUTORS. Thanks.
fei wen 于2019年4月11日周四 下午7:26写道：
> Hi,
> I want to contribute to Apache HBase.
> Would you please give me the contributor permission?
> My JIRA ID is wen.feiyi.
>
Zheng Hu created HBASE-22211:
Summary: Remove the returnBlock method in CachingBlockReader
because we can just call HFileBlock#release directly
Key: HBASE-22211
URL: https://issues.apache.org/jira/browse/HBASE-22211
Balazs Meszaros created HBASE-22210:
---
Summary: Fix hbase-connectors-assembly to include every jar
Key: HBASE-22210
URL: https://issues.apache.org/jira/browse/HBASE-22210
Project: HBase
Hi,
I want to contribute to Apache HBase.
Would you please give me the contributor permission?
My JIRA ID is wen.feiyi.
[
https://issues.apache.org/jira/browse/HBASE-17564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel resolved HBASE-17564.
---
Resolution: Duplicate
Fix Version/s: (was: 3.0.0)
This was already solved as
[
https://issues.apache.org/jira/browse/HBASE-22209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Marc Spaggiari resolved HBASE-22209.
-
Resolution: Invalid
> sdf
> ---
>
> Key: HBASE-22209
>
leonjoe created HBASE-22209:
---
Summary: sdf
Key: HBASE-22209
URL: https://issues.apache.org/jira/browse/HBASE-22209
Project: HBase
Issue Type: Bug
Components: Admin
Affects Versions:
[
https://issues.apache.org/jira/browse/HBASE-22189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel resolved HBASE-22189.
---
Resolution: Fixed
Fix Version/s: 2.2.1
2.1.5
[
https://issues.apache.org/jira/browse/HBASE-22198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-22198.
---
Resolution: Fixed
Hadoop Flags: Reviewed
Pushed to branch-2.1+.
> Fix flakey
[
https://issues.apache.org/jira/browse/HBASE-22196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-22196.
---
Resolution: Fixed
Hadoop Flags: Reviewed
Pushed to branch-2.2+.
> Split TestRestartCluster
>
-1
Observed many UT failures when checking the source package (tried multiple
rounds on two different environments, MacOs and Linux, got the same
result), including (but not limited to):
TestBulkload:
shouldBulkLoadSingleFamilyHLog(org.apache.hadoop.hbase.regionserver.TestBulkLoad)
Time elapsed:
64 matches
Mail list logo
