[jira] [Created] (HBASE-21254) Need to find a way to limit the number of proc wal files

Duo Zhang created HBASE-21254: - Summary: Need to find a way to limit the number of proc wal files Key: HBASE-21254 URL: https://issues.apache.org/jira/browse/HBASE-21254 Project: HBase Issue

[jira] [Resolved] (HBASE-19418) RANGE_OF_DELAY in PeriodicMemstoreFlusher should be configurable.

[ https://issues.apache.org/jira/browse/HBASE-19418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-19418. Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.1.1

HBase developer meetup

Hi all, I'm planning to put together an HBase developer meetup at the Salesforce office (with video conference for those who cannot attend in person) in the next few weeks. If you're interested please put your name in this

Re: Are we accepting empty commits?

I think it's a bad precident but can't argue given the constraints presented. I agree a line in the commit for explaining the situation would be good. That could be an s.apache.org short URL to this thread even. > On Sep 28, 2018, at 12:08 AM, 张铎(Duo Zhang) wrote: > > OK if the empty commit

[jira] [Created] (HBASE-21253) Backport HBASE-21244 Skip persistence when retrying for assignment related procedures to branch-2.0 and branch-2.1

Allan Yang created HBASE-21253: -- Summary: Backport HBASE-21244 Skip persistence when retrying for assignment related procedures to branch-2.0 and branch-2.1 Key: HBASE-21253 URL:

Re: Are we accepting empty commits?

There was discussion on the (incubator?) lists about allowing probot/stale to close inactive PRs which I understood to not need enough commits. Can't find the discussion now from mobile, but I think the option could be available to us if we make enough noise. Mike On Fri, Sep 28, 2018, 2:09 AM

[jira] [Resolved] (HBASE-21252) Collect loadavg when gathering machine environment

[ https://issues.apache.org/jira/browse/HBASE-21252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-21252. --- Resolution: Not A Problem OK, uptime already contains the load information. Let me check. >

[jira] [Created] (HBASE-21252) Collect loadavg when gathering machine environment

Duo Zhang created HBASE-21252: - Summary: Collect loadavg when gathering machine environment Key: HBASE-21252 URL: https://issues.apache.org/jira/browse/HBASE-21252 Project: HBase Issue Type:

[jira] [Created] (HBASE-21251) Refactor RegionMover

Guanghao Zhang created HBASE-21251: -- Summary: Refactor RegionMover Key: HBASE-21251 URL: https://issues.apache.org/jira/browse/HBASE-21251 Project: HBase Issue Type: Improvement

[jira] [Created] (HBASE-21250) Refactor WALProcedureStore and add more comments for better understanding the implementation

Duo Zhang created HBASE-21250: - Summary: Refactor WALProcedureStore and add more comments for better understanding the implementation Key: HBASE-21250 URL: https://issues.apache.org/jira/browse/HBASE-21250

Re: Are we accepting empty commits?

OK if the empty commit itself is the way to close PRs then I think it is fine. Maybe we could add a line in the commit message to mention this explicitly that the commit message is the key to close the PRs, so that we will not start discussion thread like again in the future? Thanks. Sean Busbey

Re: Are we accepting empty commits?

The commit itself is the mechanism used to close PRs. If you'd like detailed information, please read the explanation I gave on the thread "move to github flow" earlier this month[1]. We already have a section in our committer guide asking folks who review PRs to make sure the needed language is