[jira] [Created] (HBASE-23023) upgrade shellcheck used to test branch-1

Sean Busbey created HBASE-23023: --- Summary: upgrade shellcheck used to test branch-1 Key: HBASE-23023 URL: https://issues.apache.org/jira/browse/HBASE-23023 Project: HBase Issue Type: Task

[jira] [Resolved] (HBASE-23022) download page should use HTTPS for links to archive.a.o

[ https://issues.apache.org/jira/browse/HBASE-23022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey resolved HBASE-23022. - Fix Version/s: 3.0.0 Resolution: Fixed > download page should use HTTPS for links to

[jira] [Created] (HBASE-23022) download page should use HTTPS for links to archive.a.o

Sean Busbey created HBASE-23022: --- Summary: download page should use HTTPS for links to archive.a.o Key: HBASE-23022 URL: https://issues.apache.org/jira/browse/HBASE-23022 Project: HBase Issue

Re: [DISCUSS] Storing images in source repository

Sounds good to me. We have been separating out resources for site and documentation from the main repo to others for a while. Let’s continue doing that. So probably the big hbtop readme and associated resources should go into the online book and the docs in the source tree should refer to the

Re: [DISCUSS] Moving towards a branch-2 line that can get the 'stable' pointer.

For what it’s worth I had previously been concerned about the disparity between hbck capability in 1.x and 2.x but after review of the recent work I believe that is no longer true. Put another way, it is reasonable to claim it on par. As for moving the stable pointer I don’t personally have

Re: [DISCUSS] Moving towards a branch-2 line that can get the 'stable' pointer.

HBASE-21745 , the issue addressing gaps between hbck1 and hbck2 was closed a few days back after a bunch of work by a kaleidoscope of folks. The release notes section tries to describe what was added by HBASE-21745. Shout if you think the claim at

Re: [VOTE] The third HBase 2.2.1 release candidate (RC2) is available

+1 IMO, CHANGES and RELEASENOTES should accumulate all changes, not just show what is in current release. Compat report looks good. Built from src. Ran a loading and verified it there across restart. Checked sigs and hash on src tgz (Duo, sign Guanghao's key and vice-versa -- key is not 'a trusted

[jira] [Resolved] (HBASE-23021) [hbase-operator-tools] README edits in prep for release

[ https://issues.apache.org/jira/browse/HBASE-23021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-23021. --- Fix Version/s: hbase-operator-tools-1.0.0 Hadoop Flags: Reviewed Assignee: stack

[jira] [Resolved] (HBASE-23003) [HBCK2/hbase-operator-tools] Release-making scripts

[ https://issues.apache.org/jira/browse/HBASE-23003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-23003. --- Fix Version/s: hbase-operator-tools-1.0.0 Hadoop Flags: Reviewed Assignee: stack

[jira] [Resolved] (HBASE-22691) [hbase-operator-tools] Move Checkstyle suppression file to different location

[ https://issues.apache.org/jira/browse/HBASE-22691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-22691. --- Fix Version/s: hbase-operator-tools-1.0.0 Resolution: Fixed This was merged. Resolving. commit

[jira] [Created] (HBASE-23021) [hbase-operator-tools] README edits in prep for release

stack created HBASE-23021: - Summary: [hbase-operator-tools] README edits in prep for release Key: HBASE-23021 URL: https://issues.apache.org/jira/browse/HBASE-23021 Project: HBase Issue Type:

Re: Documenting how to do cluster operations when things have gone wrong

Hi folks! Was chatting in the project slack earlier today with Stack and Clay about how unwieldy the hbck2 README is getting. Heads up that I'm going to try a POC where we have operator centric docs (like the thing I described in this earlier email, and the stuff for hbck2) on the hbase.a.o

[jira] [Created] (HBASE-23020) Operations docs for HBase website

Sean Busbey created HBASE-23020: --- Summary: Operations docs for HBase website Key: HBASE-23020 URL: https://issues.apache.org/jira/browse/HBASE-23020 Project: HBase Issue Type: Umbrella

Re: [DISCUSS] Storing images in source repository

Sounds good to me. Maybe a comment in the hbtop readme source with a pointer about how to update the image content since folks might not know to look at hbase-site? On Fri, Sep 13, 2019, 02:27 Peter Somogyi wrote: > Hi, > > Recently the hbtop tool (HBASE-11062) was merged and it also includes

[jira] [Resolved] (HBASE-23002) [HBCK2/hbase-operator-tools] Create an assembly that builds an hbase-operator-tools tgz

[ https://issues.apache.org/jira/browse/HBASE-23002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-23002. --- Fix Version/s: hbase-operator-tools-1.0.0 Release Note: First cut at an assembly for

[jira] [Created] (HBASE-23019) Handle --skip-errorprone on branch-1

Peter Somogyi created HBASE-23019: - Summary: Handle --skip-errorprone on branch-1 Key: HBASE-23019 URL: https://issues.apache.org/jira/browse/HBASE-23019 Project: HBase Issue Type: Bug

[DISCUSS] Storing images in source repository

Hi, Recently the hbtop tool (HBASE-11062) was merged and it also includes a nice README documentation with demos in GIF format. Although I think we should have more documentation like this, probably it is not a good idea to store the images in the source repository. The size of these GIF images

[jira] [Resolved] (HBASE-23018) [HBCK2] Add useful messages when report/fixing missing regions in meta

[ https://issues.apache.org/jira/browse/HBASE-23018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Somogyi resolved HBASE-23018. --- Resolution: Fixed > [HBCK2] Add useful messages when report/fixing missing regions in meta