Re: Failure: HBase Generate Website
this is a side effect of HBASE-24869. feel free to ignore. On 2020/08/12 05:16:42, Apache Jenkins Server wrote: > > Build status: FAILURE > > The HBase website has not been updated to incorporate recent HBase changes. > > See > https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/6/console >
Failure: HBase Generate Website
Build status: FAILURE The HBase website has not been updated to incorporate recent HBase changes. See https://ci-hadoop.apache.org/job/HBase/job/hbase_generate_website/6/console
Re: ${BUILD_STATUS}: HBase Generate Website
this is a side effect of HBASE-24869. feel free to ignore.
On 2020/08/12 04:21:24, Apache Jenkins Server
wrote:
>
> Build status: ${BUILD_STATUS}
>
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
>
> See ${BUILD_URL}console
>
${BUILD_STATUS}: HBase Generate Website
Build status: ${BUILD_STATUS}
The HBase website has not been updated to incorporate HBase commit
${CURRENT_HBASE_COMMIT}.
See ${BUILD_URL}console
[jira] [Created] (HBASE-24869) migrate website generation to new asf jenkins
Sean Busbey created HBASE-24869: --- Summary: migrate website generation to new asf jenkins Key: HBASE-24869 URL: https://issues.apache.org/jira/browse/HBASE-24869 Project: HBase Issue Type: Task Components: build, website Reporter: Sean Busbey Assignee: Sean Busbey Update our website generation so we can use it on the new jenkins ci server * needs a job name that has no spaces (or fix the script to handle paths with spaces) * needs to only run on nodes labeled git-websites (so it will have the creds to push updates) * needs to set editable email notification on failure (details in comment) Also we will need to converte to a pipeline DSL * define tools, namely maven (alternative get [Tool Environment Plugin|https://plugins.jenkins.io/toolenv/] * set timeout for 4 hours (alternative get [build timeout plugin|https://plugins.jenkins.io/build-timeout/] * needs to clean worksapce when done (haven't found an alternatiave, maybe it's a default for non-pipeline jobs now?) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24856) Fix error prone error in FlushTableSubprocedure
[
https://issues.apache.org/jira/browse/HBASE-24856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-24856.
---
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to master and branch-2.
Thanks [~vjasani] and [~janh] for reviewing.
> Fix error prone error in FlushTableSubprocedure
> ---
>
> Key: HBASE-24856
> URL: https://issues.apache.org/jira/browse/HBASE-24856
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> {noformat}
> [ERROR]
> /home/jenkins/jenkins-home/workspace/HBase_HBase_Nightly_master/component/hbase-server/src/main/java/org/apache/hadoop/hbase/procedure/flush/FlushTableSubprocedure.java:[105,30]
> error: [ArraysAsListPrimitiveArray] Arrays.asList does not autobox primitive
> arrays, as one might expect.
> (see https://errorprone.info/bugpattern/ArraysAsListPrimitiveArray)
> Did you mean 'families = Bytes.asList(Bytes.toBytes(family));'?
> [INFO] 1 error
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [DISCUSS] we need to take action if we want asf jenkins managed tests after Aug 15 2020.
And one more thing is that, due to the limited resources(infra has not migrated all the build nodes), I filtered out all the feature branches for nightly and flaky jobs. Will add them back after infra has done all the migration. And I wonder whether we really need to test all the feature branches. Thanks. Nick Dimiduk 于2020年8月12日周三 上午2:02写道： > Thank you so much for taking on these migrations! I very much appreciate > it! > > -n > > On Tue, Aug 11, 2020 at 8:08 AM 张铎(Duo Zhang) > wrote: > > > Some updates here, we have migrated most of the jobs to ci-hadoop.a.o. > > > > There is a known issue that our flaky dashboard is broken, due to this > new > > feature of jenkins > > > > > https://wiki.jenkins.io/display/JENKINS/Configuring+Content+Security+Policy > > > > Josh is contacting the infra team to see if they can relax the policy > but I > > do not think it is easy as the policy is per site, not per job... > > > > Anyway, there is a chrome plugin to temporarily disable CSP, so you can > > view the correct flaky dashboard. > > > > > > > https://chrome.google.com/webstore/detail/disable-content-security/ieelmcmcagommplceebfedjlakkhpden > > > > Thanks. > > > > Andor Molnar 于2020年7月30日周四 下午3:12写道： > > > > > https://issues.apache.org/jira/browse/INFRA-20613 > > > > > > > > > > > > > On 2020. Jul 30., at 1:47, 张铎(Duo Zhang) > > wrote: > > > > > > > > This never worked in the past... > > > > > > > > But it would be great if you can kick the infra team to get this done > > :) > > > > > > > > File an infra issue? > > > > > > > > Andor Molnar 于2020年7月29日 周三18:36写道： > > > > > > > >> You’re having the same issue with HBase Robot btw. At the end of > > console > > > >> outputs: > > > >> > > > >> "Could not update commit status, please check if your scan > credentials > > > >> belong to a member of the organization or a collaborator of the > > > repository > > > >> and repo:status scope is selected” > > > >> > > > >> ...and shortly after that: > > > >> > > > >> "GitHub has been notified of this commit’s build result” > > > >> > > > >> Whatever does it mean. > > > >> > > > >> Andor > > > >> > > > >> > > > >> > > > >>> On 2020. Jul 29., at 11:57, Andor Molnar wrote: > > > >>> > > > >>> Yep, we’ve finally received it. It’s done. > > > >>> > > > >>> Current issue is that Jenkins is unable to set Github build status. > > > I’ve > > > >> added repo:status permission, but it’s also asking to be member of > the > > > >> project/organization and not sure how to do that. > > > >>> > > > >>> Andor > > > >>> > > > >>> > > > >>> > > > On 2020. Jul 29., at 4:10, 张铎(Duo Zhang) > > > wrote: > > > > > > Seems you have already made it? > > > > > > Usually there are several moderators for the private list, you > need > > to > > > >> ask > > > them to let the GitHub registration go through. > > > > > > Andor Molnar 于2020年7月29日周三 上午1:03写道： > > > > > > > Thanks Duo, that’s very helpful. > > > > I cannot set private@zookeeper as a verified e-mail address, > > because > > > >> the > > > > verification e-mail cannot be sent to the list. Isn’t that > > restricted > > > >> for > > > > members only (by default)? > > > > > > > > Andor > > > > > > > > > > > > > > > >> On 2020. Jul 28., at 3:15, 张铎(Duo Zhang) > > > > >> wrote: > > > >> > > > >> Hi Andor, > > > >> > > > >> The Apache-HBase account is registered by me, using the > > > private@hbase > > > >> mailing list, so all the PMC members can maintain the password. > > > >> > > > >> I generated an access token and added it to our jenkins, so we > can > > > >> use it > > > >> to post comments back to GitHub. > > > >> > > > >> I think you could do the same to register an Apache-ZooKeeper > > > >> account? Or > > > >> if you want to use the hadoop-yetus account, you'd better ask > the > > > >> hadoop > > > >> PMC members or Gavin to add the token to jenkins so you can use > > it. > > > >> > > > >> Thanks. > > > >> > > > >> Andor Molnar 于2020年7月28日周二 上午3:56写道： > > > >> > > > >>> Hi Duo, > > > >>> > > > >>> I’m trying to create a similar job for Apache ZooKeeper, but > > > > unfortunately > > > >>> haven’t got too much help on the Apache builds@ list so far, > so > > > I’m > > > >>> rather asking you if you don’t mind. > > > >>> > > > >>> First, how have you set up the Hbase Github account that you > use > > in > > > >> this > > > >>> job to access the repo? > > > >>> > > > >>> Thanks, > > > >>> Andor > > > >>> > > > >>> > > > >>> > > > On 2020. Jul 27., at 2:22, 张铎(Duo Zhang) < > palomino...@gmail.com > > > > > > > wrote: > > > > > > The pre commit job has been migrated to c-hadoop.a.o. > > > > > > I have disabled periodical scan for the old job on builds.a.o, > > as > > > we > > > >>> still > > > need to view the pre
Re: EOL 1.3.x?
+1 Zach York 于2020年8月12日周三 上午2:43写道： > +1 > > Do we typically do a final release or can we just EOL as is? > > On Tue, Aug 11, 2020 at 9:43 AM Geoffrey Jacoby wrote: > > > +1 (non-binding) > > > > Geoffrey > > > > On Tue, Aug 11, 2020 at 8:19 AM Josh Elser wrote: > > > > > Sounds good to me. > > > > > > On 8/11/20 4:01 AM, 张铎(Duo Zhang) wrote: > > > > The last release for 1.3.x is 2019.10.20, which means we do not have > a > > > > release for this release line for about 10 months. > > > > > > > > Let's make it EOL and tell users to at least upgrade to 1.4.x? > > > > > > > > Thanks. > > > > > > > > > >
[jira] [Resolved] (HBASE-24843) Sort the constants in `hbase_constants.rb`
[
https://issues.apache.org/jira/browse/HBASE-24843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-24843.
--
Resolution: Fixed
Thanks for the reviews, [~vjasani], [~liuml07].
> Sort the constants in `hbase_constants.rb`
> --
>
> Key: HBASE-24843
> URL: https://issues.apache.org/jira/browse/HBASE-24843
> Project: HBase
> Issue Type: Task
> Components: shell
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> The list of constant definitions in {{hbase_constants.rb}} is a bit of a
> mess. Sort them.
> Breaks out the minor cleanup from HBASE-24627 /
> [PR#2215|https://github.com/apache/hbase/pull/2215] into it's own ticket.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24868) Send announce email
Nick Dimiduk created HBASE-24868: Summary: Send announce email Key: HBASE-24868 URL: https://issues.apache.org/jira/browse/HBASE-24868 Project: HBase Issue Type: Sub-task Reporter: Nick Dimiduk Assignee: Nick Dimiduk -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24865) Release version 2.3.1 in Jira
Nick Dimiduk created HBASE-24865: Summary: Release version 2.3.1 in Jira Key: HBASE-24865 URL: https://issues.apache.org/jira/browse/HBASE-24865 Project: HBase Issue Type: Sub-task Reporter: Nick Dimiduk Assignee: Nick Dimiduk -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24866) Update reporter tool with new release
Nick Dimiduk created HBASE-24866: Summary: Update reporter tool with new release Key: HBASE-24866 URL: https://issues.apache.org/jira/browse/HBASE-24866 Project: HBase Issue Type: Sub-task Reporter: Nick Dimiduk Assignee: Nick Dimiduk -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24867) Add 2.3.1 to the downloads page
Nick Dimiduk created HBASE-24867: Summary: Add 2.3.1 to the downloads page Key: HBASE-24867 URL: https://issues.apache.org/jira/browse/HBASE-24867 Project: HBase Issue Type: Sub-task Reporter: Nick Dimiduk Assignee: Nick Dimiduk -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24863) "Release" staged nexus repository
Nick Dimiduk created HBASE-24863: Summary: "Release" staged nexus repository Key: HBASE-24863 URL: https://issues.apache.org/jira/browse/HBASE-24863 Project: HBase Issue Type: Sub-task Reporter: Nick Dimiduk Assignee: Nick Dimiduk -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24864) Push signed release tag
Nick Dimiduk created HBASE-24864: Summary: Push signed release tag Key: HBASE-24864 URL: https://issues.apache.org/jira/browse/HBASE-24864 Project: HBase Issue Type: Sub-task Reporter: Nick Dimiduk Assignee: Nick Dimiduk -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24862) Spin RCs
Nick Dimiduk created HBASE-24862: Summary: Spin RCs Key: HBASE-24862 URL: https://issues.apache.org/jira/browse/HBASE-24862 Project: HBase Issue Type: Sub-task Reporter: Nick Dimiduk Assignee: Nick Dimiduk -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24861) Release 2.3.1
Nick Dimiduk created HBASE-24861: Summary: Release 2.3.1 Key: HBASE-24861 URL: https://issues.apache.org/jira/browse/HBASE-24861 Project: HBase Issue Type: Task Components: community Reporter: Nick Dimiduk Assignee: Nick Dimiduk -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24141) Build "what's new in 2.3.0" report
[ https://issues.apache.org/jira/browse/HBASE-24141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk resolved HBASE-24141. -- Resolution: Fixed > Build "what's new in 2.3.0" report > -- > > Key: HBASE-24141 > URL: https://issues.apache.org/jira/browse/HBASE-24141 > Project: HBase > Issue Type: Sub-task >Reporter: Nick Dimiduk >Assignee: Nick Dimiduk >Priority: Major > > Work out the set of features that are new in 2.3.0. Provide this report along > with RC artifacts, and use it to highlight RC testing and release > announcements. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24859) Remove the empty regions from the hbase mapreduce splits
[ https://issues.apache.org/jira/browse/HBASE-24859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandeep Pal resolved HBASE-24859. - Resolution: Abandoned Closing this since it may lead to data misses if new data received after table splits information get passed to MR. > Remove the empty regions from the hbase mapreduce splits > > > Key: HBASE-24859 > URL: https://issues.apache.org/jira/browse/HBASE-24859 > Project: HBase > Issue Type: Improvement > Components: mapreduce >Reporter: Sandeep Pal >Assignee: Sandeep Pal >Priority: Major > > It has been observed that when the table has too many regions, MR jobs > consume more memory in the client. This is because we keep the region level > information in memory and the memory heavy object is TableSplit because of > Scan object as a part of it. > We can optimize the memory consumption by not loading the region level > information if the region is empty. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24860) Bump copyright year in NOTICE
[ https://issues.apache.org/jira/browse/HBASE-24860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved HBASE-24860. Resolution: Fixed Pushed without review. FYI [~zhangduo], in case you have to do a 3.4.0-rc2 > Bump copyright year in NOTICE > - > > Key: HBASE-24860 > URL: https://issues.apache.org/jira/browse/HBASE-24860 > Project: HBase > Issue Type: Task > Components: thirdparty >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Trivial > Fix For: thirdparty-3.5.0 > > > year in NOTICE is 2018, should be 2020 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24860) Bump copyright year in NOTICE
Josh Elser created HBASE-24860: -- Summary: Bump copyright year in NOTICE Key: HBASE-24860 URL: https://issues.apache.org/jira/browse/HBASE-24860 Project: HBase Issue Type: Task Components: thirdparty Reporter: Josh Elser Assignee: Josh Elser -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: EOL 1.3.x?
+1 Do we typically do a final release or can we just EOL as is? On Tue, Aug 11, 2020 at 9:43 AM Geoffrey Jacoby wrote: > +1 (non-binding) > > Geoffrey > > On Tue, Aug 11, 2020 at 8:19 AM Josh Elser wrote: > > > Sounds good to me. > > > > On 8/11/20 4:01 AM, 张铎(Duo Zhang) wrote: > > > The last release for 1.3.x is 2019.10.20, which means we do not have a > > > release for this release line for about 10 months. > > > > > > Let's make it EOL and tell users to at least upgrade to 1.4.x? > > > > > > Thanks. > > > > > >
[jira] [Created] (HBASE-24859) Remove the empty regions from the hbase mapreduce splits
Sandeep Pal created HBASE-24859: --- Summary: Remove the empty regions from the hbase mapreduce splits Key: HBASE-24859 URL: https://issues.apache.org/jira/browse/HBASE-24859 Project: HBase Issue Type: Improvement Components: mapreduce Reporter: Sandeep Pal Assignee: Sandeep Pal It has been observed that when the table has too many regions, MR jobs consume more memory in the client. This is because we keep the region level information in memory and the memory heavy object is TableSplit because of Scan object as a part of it. We can optimize the memory consumption by not loading the region level information if the region is empty. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24858) Builds without a `clean` phase fail on hbase-shaded-jetty
Josh Elser created HBASE-24858:
--
Summary: Builds without a `clean` phase fail on hbase-shaded-jetty
Key: HBASE-24858
URL: https://issues.apache.org/jira/browse/HBASE-24858
Project: HBase
Issue Type: Bug
Reporter: Josh Elser
Assignee: Josh Elser
In 3.4.0-rc1 that [~zhangduo] created, I noticed that builds of the project
failed on hbase-shaded-jetty when I did not include {{clean}} in my build
command.
{noformat}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 3.604 s
[INFO] Finished at: 2020-08-11T14:38:45-04:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project
hbase-shaded-jetty: Error creating shaded jar: duplicate entry:
META-INF/services/org.apache.hbase.thirdparty.org.eclipse.jetty.http.HttpFieldPreEncoder
-> [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
{noformat}
Poking around, it appears that this is actually to do with the creating of the
shaded source jar.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [DISCUSS] we need to take action if we want asf jenkins managed tests after Aug 15 2020.
Thank you so much for taking on these migrations! I very much appreciate it! -n On Tue, Aug 11, 2020 at 8:08 AM 张铎(Duo Zhang) wrote: > Some updates here, we have migrated most of the jobs to ci-hadoop.a.o. > > There is a known issue that our flaky dashboard is broken, due to this new > feature of jenkins > > https://wiki.jenkins.io/display/JENKINS/Configuring+Content+Security+Policy > > Josh is contacting the infra team to see if they can relax the policy but I > do not think it is easy as the policy is per site, not per job... > > Anyway, there is a chrome plugin to temporarily disable CSP, so you can > view the correct flaky dashboard. > > > https://chrome.google.com/webstore/detail/disable-content-security/ieelmcmcagommplceebfedjlakkhpden > > Thanks. > > Andor Molnar 于2020年7月30日周四 下午3:12写道： > > > https://issues.apache.org/jira/browse/INFRA-20613 > > > > > > > > > On 2020. Jul 30., at 1:47, 张铎(Duo Zhang) > wrote: > > > > > > This never worked in the past... > > > > > > But it would be great if you can kick the infra team to get this done > :) > > > > > > File an infra issue? > > > > > > Andor Molnar 于2020年7月29日 周三18:36写道： > > > > > >> You’re having the same issue with HBase Robot btw. At the end of > console > > >> outputs: > > >> > > >> "Could not update commit status, please check if your scan credentials > > >> belong to a member of the organization or a collaborator of the > > repository > > >> and repo:status scope is selected” > > >> > > >> ...and shortly after that: > > >> > > >> "GitHub has been notified of this commit’s build result” > > >> > > >> Whatever does it mean. > > >> > > >> Andor > > >> > > >> > > >> > > >>> On 2020. Jul 29., at 11:57, Andor Molnar wrote: > > >>> > > >>> Yep, we’ve finally received it. It’s done. > > >>> > > >>> Current issue is that Jenkins is unable to set Github build status. > > I’ve > > >> added repo:status permission, but it’s also asking to be member of the > > >> project/organization and not sure how to do that. > > >>> > > >>> Andor > > >>> > > >>> > > >>> > > On 2020. Jul 29., at 4:10, 张铎(Duo Zhang) > > wrote: > > > > Seems you have already made it? > > > > Usually there are several moderators for the private list, you need > to > > >> ask > > them to let the GitHub registration go through. > > > > Andor Molnar 于2020年7月29日周三 上午1:03写道： > > > > > Thanks Duo, that’s very helpful. > > > I cannot set private@zookeeper as a verified e-mail address, > because > > >> the > > > verification e-mail cannot be sent to the list. Isn’t that > restricted > > >> for > > > members only (by default)? > > > > > > Andor > > > > > > > > > > > >> On 2020. Jul 28., at 3:15, 张铎(Duo Zhang) > > >> wrote: > > >> > > >> Hi Andor, > > >> > > >> The Apache-HBase account is registered by me, using the > > private@hbase > > >> mailing list, so all the PMC members can maintain the password. > > >> > > >> I generated an access token and added it to our jenkins, so we can > > >> use it > > >> to post comments back to GitHub. > > >> > > >> I think you could do the same to register an Apache-ZooKeeper > > >> account? Or > > >> if you want to use the hadoop-yetus account, you'd better ask the > > >> hadoop > > >> PMC members or Gavin to add the token to jenkins so you can use > it. > > >> > > >> Thanks. > > >> > > >> Andor Molnar 于2020年7月28日周二 上午3:56写道： > > >> > > >>> Hi Duo, > > >>> > > >>> I’m trying to create a similar job for Apache ZooKeeper, but > > > unfortunately > > >>> haven’t got too much help on the Apache builds@ list so far, so > > I’m > > >>> rather asking you if you don’t mind. > > >>> > > >>> First, how have you set up the Hbase Github account that you use > in > > >> this > > >>> job to access the repo? > > >>> > > >>> Thanks, > > >>> Andor > > >>> > > >>> > > >>> > > On 2020. Jul 27., at 2:22, 张铎(Duo Zhang) > > > > wrote: > > > > The pre commit job has been migrated to c-hadoop.a.o. > > > > I have disabled periodical scan for the old job on builds.a.o, > as > > we > > >>> still > > need to view the pre commit result on it do not delete for now. > > Will > > >>> delete > > it later, maybe after several weeks. > > > > The new job is here > > > > > > >> https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/ > > > > Thanks. > > > > 张铎(Duo Zhang) 于2020年7月25日周六 下午9:44写道： > > > > > > > > > > >>> > > > > > >> > > > https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/5/console > > > > > > > > > We successfully finished a nightly build. > > > > > > But seems the jiraComment did not work. I haven't seen the > >
Re: [VOTE] Second release candidate for hbase-thirdparty 3.4.0 is available for download
TestRESTApiClusterManager CNFE is present in pre-commit test failures on https://github.com/apache/hbase/pull/. Also, surprisingly, shadedjars check is failing with NPE. Apart from above issues, build and tests are overall good locally with 3.4.0. However, I am not sure about the issue with shadedjars and how much of an actual blocker it is and hence, keeping an eye over the PR for update before providing the vote. On 2020/08/11 16:05:46, Josh Elser wrote: > +1 (binding) > > Everything with 3.4.0 looks fine to me. I used the staged artifacts at > the URL which Viraj corrected. A couple of non-blocking issues. > > * NOTICE needs updating (2018 year) > * hbase-thirdparty build fails w/o a `clean` (see below) > * TestRESTApiClusterManager failed in the hbase build, looking for > non-shaded jersey. Not a blocker for this release (also below) > > > ``` > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on > project hbase-shaded-jetty: Error creating shaded jar: duplicate entry: > META-INF/services/org.apache.hbase.thirdparty.org.eclipse.jetty.http.HttpFieldPreEncoder > > -> [Help 1] > ``` > > ``` > [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 0.308 s <<< FAILURE! - in org.apache.hadoop.hbase.TestRESTApiClusterManager > [ERROR] > org.apache.hadoop.hbase.TestRESTApiClusterManager.isRunningPositive > Time elapsed: 0.165 s <<< ERROR! > java.lang.RuntimeException: java.lang.ClassNotFoundException: > org.glassfish.jersey.client.JerseyClientBuilder > at > org.apache.hadoop.hbase.TestRESTApiClusterManager.before(TestRESTApiClusterManager.java:63) > Caused by: java.lang.ClassNotFoundException: > org.glassfish.jersey.client.JerseyClientBuilder > at > org.apache.hadoop.hbase.TestRESTApiClusterManager.before(TestRESTApiClusterManager.java:63) > ``` > > I'll try to help out fixing these. > > On 8/8/20 11:02 AM, 张铎(Duo Zhang) wrote: > > Please vote on this Apache hbase thirdparty release candidate, > > hbase-thirdparty-3.4.0RC1 > > > > The VOTE will remain open for at least 72 hours. > > > > [ ] +1 Release this package as Apache hbase thirdparty 3.4.0 > > [ ] -1 Do not release this package because ... > > > > The tag to be voted on is 3.4.0RC1: > > > >https://github.com/apache/hbase-thirdparty/tree/3.4.0RC1 > > > > The release files, including signatures, digests, as well as CHANGES.md > > and RELEASENOTES.md included in this RC can be found at: > > > >https://dist.apache.org/repos/dist/dev/hbase/3.4.0RC1/ > > > > Maven artifacts are available in a staging repository at: > > > >https://repository.apache.org/content/repositories/orgapachehbase-1403/ > > > > Artifacts were signed with the 9AD2AE49 key which can be found in: > > > >https://dist.apache.org/repos/dist/release/hbase/KEYS > > > > We shade jetty and jersey in this version for addressing the conflicts > > between jetty 9.3 and 9.4, as hadoop recently upgraded its jetty from 9.3 > > to 9.4 in patch releases. > > > > To learn more about Apache hbase thirdparty, please see > > > >http://hbase.apache.org/ > > > > Thanks, > > Your HBase Release Manager > > >
Re: EOL 1.3.x?
+1 (non-binding) Geoffrey On Tue, Aug 11, 2020 at 8:19 AM Josh Elser wrote: > Sounds good to me. > > On 8/11/20 4:01 AM, 张铎(Duo Zhang) wrote: > > The last release for 1.3.x is 2019.10.20, which means we do not have a > > release for this release line for about 10 months. > > > > Let's make it EOL and tell users to at least upgrade to 1.4.x? > > > > Thanks. > > >
Re: [VOTE] Second release candidate for hbase-thirdparty 3.4.0 is available for download
+1 (binding) Everything with 3.4.0 looks fine to me. I used the staged artifacts at the URL which Viraj corrected. A couple of non-blocking issues. * NOTICE needs updating (2018 year) * hbase-thirdparty build fails w/o a `clean` (see below) * TestRESTApiClusterManager failed in the hbase build, looking for non-shaded jersey. Not a blocker for this release (also below) ``` [ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:3.2.4:shade (default) on project hbase-shaded-jetty: Error creating shaded jar: duplicate entry: META-INF/services/org.apache.hbase.thirdparty.org.eclipse.jetty.http.HttpFieldPreEncoder -> [Help 1] ``` ``` [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.308 s <<< FAILURE! - in org.apache.hadoop.hbase.TestRESTApiClusterManager [ERROR] org.apache.hadoop.hbase.TestRESTApiClusterManager.isRunningPositive Time elapsed: 0.165 s <<< ERROR! java.lang.RuntimeException: java.lang.ClassNotFoundException: org.glassfish.jersey.client.JerseyClientBuilder at org.apache.hadoop.hbase.TestRESTApiClusterManager.before(TestRESTApiClusterManager.java:63) Caused by: java.lang.ClassNotFoundException: org.glassfish.jersey.client.JerseyClientBuilder at org.apache.hadoop.hbase.TestRESTApiClusterManager.before(TestRESTApiClusterManager.java:63) ``` I'll try to help out fixing these. On 8/8/20 11:02 AM, 张铎(Duo Zhang) wrote: Please vote on this Apache hbase thirdparty release candidate, hbase-thirdparty-3.4.0RC1 The VOTE will remain open for at least 72 hours. [ ] +1 Release this package as Apache hbase thirdparty 3.4.0 [ ] -1 Do not release this package because ... The tag to be voted on is 3.4.0RC1: https://github.com/apache/hbase-thirdparty/tree/3.4.0RC1 The release files, including signatures, digests, as well as CHANGES.md and RELEASENOTES.md included in this RC can be found at: https://dist.apache.org/repos/dist/dev/hbase/3.4.0RC1/ Maven artifacts are available in a staging repository at: https://repository.apache.org/content/repositories/orgapachehbase-1403/ Artifacts were signed with the 9AD2AE49 key which can be found in: https://dist.apache.org/repos/dist/release/hbase/KEYS We shade jetty and jersey in this version for addressing the conflicts between jetty 9.3 and 9.4, as hadoop recently upgraded its jetty from 9.3 to 9.4 in patch releases. To learn more about Apache hbase thirdparty, please see http://hbase.apache.org/ Thanks, Your HBase Release Manager
Re: EOL 1.3.x?
Sounds good to me. On 8/11/20 4:01 AM, 张铎(Duo Zhang) wrote: The last release for 1.3.x is 2019.10.20, which means we do not have a release for this release line for about 10 months. Let's make it EOL and tell users to at least upgrade to 1.4.x? Thanks.
[jira] [Resolved] (HBASE-24834) TestReplicationSource.testWALEntryFilter failing in branch-2+
[
https://issues.apache.org/jira/browse/HBASE-24834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved HBASE-24834.
Resolution: Cannot Reproduce
Maybe fixed by HBASE-24830?
> TestReplicationSource.testWALEntryFilter failing in branch-2+
> -
>
> Key: HBASE-24834
> URL: https://issues.apache.org/jira/browse/HBASE-24834
> Project: HBase
> Issue Type: Task
> Components: Replication, test
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> {noformat}
> [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 46.497 s <<< FAILURE! - in
> org.apache.hadoop.hbase.replication.regionserver.TestReplicationSource
> [ERROR]
> org.apache.hadoop.hbase.replication.regionserver.TestReplicationSource.testWALEntryFilter
> Time elapsed: 1.405 s <<< FAILURE!
> java.lang.AssertionError
> at
> org.apache.hadoop.hbase.replication.regionserver.TestReplicationSource.testWALEntryFilter(TestReplicationSource.java:177)
> {noformat}
> Noticed this during HBASE-24779, but didn't fix it. Believe it comes from
> HBASE-24817.
> Looks to be that the edit we expect to not be filtered is actually getting
> filtered because it has no cells (thus, no change and doesn't need to be
> replicated). Should be a simple fix.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [DISCUSS] we need to take action if we want asf jenkins managed tests after Aug 15 2020.
Some updates here, we have migrated most of the jobs to ci-hadoop.a.o. There is a known issue that our flaky dashboard is broken, due to this new feature of jenkins https://wiki.jenkins.io/display/JENKINS/Configuring+Content+Security+Policy Josh is contacting the infra team to see if they can relax the policy but I do not think it is easy as the policy is per site, not per job... Anyway, there is a chrome plugin to temporarily disable CSP, so you can view the correct flaky dashboard. https://chrome.google.com/webstore/detail/disable-content-security/ieelmcmcagommplceebfedjlakkhpden Thanks. Andor Molnar 于2020年7月30日周四 下午3:12写道： > https://issues.apache.org/jira/browse/INFRA-20613 > > > > > On 2020. Jul 30., at 1:47, 张铎(Duo Zhang) wrote: > > > > This never worked in the past... > > > > But it would be great if you can kick the infra team to get this done :) > > > > File an infra issue? > > > > Andor Molnar 于2020年7月29日 周三18:36写道： > > > >> You’re having the same issue with HBase Robot btw. At the end of console > >> outputs: > >> > >> "Could not update commit status, please check if your scan credentials > >> belong to a member of the organization or a collaborator of the > repository > >> and repo:status scope is selected” > >> > >> ...and shortly after that: > >> > >> "GitHub has been notified of this commit’s build result” > >> > >> Whatever does it mean. > >> > >> Andor > >> > >> > >> > >>> On 2020. Jul 29., at 11:57, Andor Molnar wrote: > >>> > >>> Yep, we’ve finally received it. It’s done. > >>> > >>> Current issue is that Jenkins is unable to set Github build status. > I’ve > >> added repo:status permission, but it’s also asking to be member of the > >> project/organization and not sure how to do that. > >>> > >>> Andor > >>> > >>> > >>> > On 2020. Jul 29., at 4:10, 张铎(Duo Zhang) > wrote: > > Seems you have already made it? > > Usually there are several moderators for the private list, you need to > >> ask > them to let the GitHub registration go through. > > Andor Molnar 于2020年7月29日周三 上午1:03写道： > > > Thanks Duo, that’s very helpful. > > I cannot set private@zookeeper as a verified e-mail address, because > >> the > > verification e-mail cannot be sent to the list. Isn’t that restricted > >> for > > members only (by default)? > > > > Andor > > > > > > > >> On 2020. Jul 28., at 3:15, 张铎(Duo Zhang) > >> wrote: > >> > >> Hi Andor, > >> > >> The Apache-HBase account is registered by me, using the > private@hbase > >> mailing list, so all the PMC members can maintain the password. > >> > >> I generated an access token and added it to our jenkins, so we can > >> use it > >> to post comments back to GitHub. > >> > >> I think you could do the same to register an Apache-ZooKeeper > >> account? Or > >> if you want to use the hadoop-yetus account, you'd better ask the > >> hadoop > >> PMC members or Gavin to add the token to jenkins so you can use it. > >> > >> Thanks. > >> > >> Andor Molnar 于2020年7月28日周二 上午3:56写道： > >> > >>> Hi Duo, > >>> > >>> I’m trying to create a similar job for Apache ZooKeeper, but > > unfortunately > >>> haven’t got too much help on the Apache builds@ list so far, so > I’m > >>> rather asking you if you don’t mind. > >>> > >>> First, how have you set up the Hbase Github account that you use in > >> this > >>> job to access the repo? > >>> > >>> Thanks, > >>> Andor > >>> > >>> > >>> > On 2020. Jul 27., at 2:22, 张铎(Duo Zhang) > > wrote: > > The pre commit job has been migrated to c-hadoop.a.o. > > I have disabled periodical scan for the old job on builds.a.o, as > we > >>> still > need to view the pre commit result on it do not delete for now. > Will > >>> delete > it later, maybe after several weeks. > > The new job is here > > > >> https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/ > > Thanks. > > 张铎(Duo Zhang) 于2020年7月25日周六 下午9:44写道： > > > > > > >>> > > > >> > https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/5/console > > > > > > We successfully finished a nightly build. > > > > But seems the jiraComment did not work. I haven't seen the > comment > > on HBASE-24757... > > > > 张铎(Duo Zhang) 于2020年7月25日周六 下午4:51写道： > > > >> After installing two new jenkins plugins, the pre commit job > seems > > fine > >> now. > >> > >> The last failure is because of a timeout, I assume the problem > is > > that > >>> we > >> do not have enough executors so all the jobs are executed > > sequentially. > >> > >> Maybe we
[jira] [Created] (HBASE-24857) Fix several problems when starting webUI
Zhuoyue Huang created HBASE-24857: - Summary: Fix several problems when starting webUI Key: HBASE-24857 URL: https://issues.apache.org/jira/browse/HBASE-24857 Project: HBase Issue Type: Sub-task Components: canary, UI Affects Versions: 3.0.0-alpha-1 Reporter: Zhuoyue Huang Assignee: Zhuoyue Huang Fix For: 3.0.0-alpha-1 As discussed in the parent issue. There are three problems to be solved： # If we put up webUI while starting Canary, there throw a ClassNotFoundException that shaded class cannot be found # webUI should be showing up only in daemon mode # ServletException throwing when visiting the web page of Canary webUI -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24856) Fix error prone error in FlushTableSubprocedure
Duo Zhang created HBASE-24856:
-
Summary: Fix error prone error in FlushTableSubprocedure
Key: HBASE-24856
URL: https://issues.apache.org/jira/browse/HBASE-24856
Project: HBase
Issue Type: Bug
Reporter: Duo Zhang
{noformat}
[ERROR]
/home/jenkins/jenkins-home/workspace/HBase_HBase_Nightly_master/component/hbase-server/src/main/java/org/apache/hadoop/hbase/procedure/flush/FlushTableSubprocedure.java:[105,30]
error: [ArraysAsListPrimitiveArray] Arrays.asList does not autobox primitive
arrays, as one might expect.
(see https://errorprone.info/bugpattern/ArraysAsListPrimitiveArray)
Did you mean 'families = Bytes.asList(Bytes.toBytes(family));'?
[INFO] 1 error
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-24851) Override CSP in our flaky dashboard html
[
https://issues.apache.org/jira/browse/HBASE-24851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-24851.
---
Resolution: Won't Fix
https://wiki.jenkins.io/display/JENKINS/Configuring+Content+Security+Policy
This is a new jenkins feature, where the server will return a response header
of Content Security Policy, so it is impossible to override the response header
with http-equiv...
Resolve as won't fix.
Let's find other ways to fix this.
> Override CSP in our flaky dashboard html
>
>
> Key: HBASE-24851
> URL: https://issues.apache.org/jira/browse/HBASE-24851
> Project: HBase
> Issue Type: Sub-task
> Components: scripts
>Reporter: Duo Zhang
>Priority: Major
>
> We got this on the new find flaky tests job.
> {noformat}
> Refused to apply inline style because it violates the following Content
> Security Policy directive: "style-src 'self'". Either the 'unsafe-inline'
> keyword, a hash ('sha256-NSQHKKs1VuvATRi81u9VAYWYDZfJrWTnQg5Ag4MxBQU='), or a
> nonce ('nonce-...') is required to enable inline execution.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-24825) Add UncaughtExceptionHandler for NettyRpcConnection Relogin thread
[ https://issues.apache.org/jira/browse/HBASE-24825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] niuyulin resolved HBASE-24825. -- Resolution: Won't Fix [#2231|https://github.com/apache/hbase/pull/2231] has resolved this issue > Add UncaughtExceptionHandler for NettyRpcConnection Relogin thread > -- > > Key: HBASE-24825 > URL: https://issues.apache.org/jira/browse/HBASE-24825 > Project: HBase > Issue Type: Improvement > Components: Client >Reporter: niuyulin >Assignee: niuyulin >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24735) Refactor ReplicationSourceManager: move logPositionAndCleanOldLogs/cleanUpHFileRefs to ReplicationSource inside
[ https://issues.apache.org/jira/browse/HBASE-24735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang resolved HBASE-24735. Resolution: Fixed Pushed to HBASE-24666. Thanks all for reviewing. > Refactor ReplicationSourceManager: move > logPositionAndCleanOldLogs/cleanUpHFileRefs to ReplicationSource inside > --- > > Key: HBASE-24735 > URL: https://issues.apache.org/jira/browse/HBASE-24735 > Project: HBase > Issue Type: Sub-task >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang >Priority: Major > > After this, ReplicationSourceManager should only keep the methods which are > used for startup/terminate ReplicationSource. The startup/teminate releated > work will be moved to new ReplicationServer. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24855) Why Hregion's lock method is not public？
[
https://issues.apache.org/jira/browse/HBASE-24855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani resolved HBASE-24855.
--
Resolution: Invalid
> Why Hregion's lock method is not public？
> -
>
> Key: HBASE-24855
> URL: https://issues.apache.org/jira/browse/HBASE-24855
> Project: HBase
> Issue Type: Wish
>Reporter: yukunpeng
>Priority: Trivial
>
>
> {code:java}
> private void lock(final Lock lock) throws RegionTooBusyException,
> InterruptedIOException {
> lock(lock, 1);
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-24450) There was a partial failure due to IO when attempting to load
[ https://issues.apache.org/jira/browse/HBASE-24450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yukunpeng resolved HBASE-24450. --- Resolution: Not A Problem > There was a partial failure due to IO when attempting to load > - > > Key: HBASE-24450 > URL: https://issues.apache.org/jira/browse/HBASE-24450 > Project: HBase > Issue Type: Bug >Affects Versions: 2.2.4 >Reporter: yukunpeng >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24855) Why Hregion's lock method is not public？
yukunpeng created HBASE-24855:
-
Summary: Why Hregion's lock method is not public？
Key: HBASE-24855
URL: https://issues.apache.org/jira/browse/HBASE-24855
Project: HBase
Issue Type: Wish
Reporter: yukunpeng
{code:java}
private void lock(final Lock lock) throws RegionTooBusyException,
InterruptedIOException {
lock(lock, 1);
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: EOL 1.3.x?
+1 On 2020/08/11 08:38:02, Peter Somogyi wrote: > Big +1! > > On Tue, Aug 11, 2020 at 10:02 AM 张铎(Duo Zhang) > wrote: > > > The last release for 1.3.x is 2019.10.20, which means we do not have a > > release for this release line for about 10 months. > > > > Let's make it EOL and tell users to at least upgrade to 1.4.x? > > > > Thanks. > > >
[jira] [Created] (HBASE-24854) Correct the help content of assign and unassign commands in hbase shell
Zheng Wang created HBASE-24854: -- Summary: Correct the help content of assign and unassign commands in hbase shell Key: HBASE-24854 URL: https://issues.apache.org/jira/browse/HBASE-24854 Project: HBase Issue Type: Improvement Components: shell Reporter: Zheng Wang Assignee: Zheng Wang -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: EOL 1.3.x?
Big +1! On Tue, Aug 11, 2020 at 10:02 AM 张铎(Duo Zhang) wrote: > The last release for 1.3.x is 2019.10.20, which means we do not have a > release for this release line for about 10 months. > > Let's make it EOL and tell users to at least upgrade to 1.4.x? > > Thanks. >
[jira] [Created] (HBASE-24853) The archiveLogFile should be called before decreasing totalLogSize in AbstractFSWAL.cleanOldLogs
Zheng Wang created HBASE-24853: -- Summary: The archiveLogFile should be called before decreasing totalLogSize in AbstractFSWAL.cleanOldLogs Key: HBASE-24853 URL: https://issues.apache.org/jira/browse/HBASE-24853 Project: HBase Issue Type: Improvement Components: wal Reporter: Zheng Wang Assignee: Zheng Wang As discussed in HBASE-24822, if archiveLogFile failed to rename, then the totalLogSize will not correct. -- This message was sent by Atlassian Jira (v8.3.4#803005)
EOL 1.3.x?
The last release for 1.3.x is 2019.10.20, which means we do not have a release for this release line for about 10 months. Let's make it EOL and tell users to at least upgrade to 1.4.x? Thanks.
