On Wed, Jul 22, 2020 at 17:28 Tak-Lon (Stephen) Wu
wrote:
> just a dummy question on how we contribute, should we have a feature
> branch? or can we stream into the master if we don't break anything ?
>
I would prefer a feature branch that is regularly rebased onto master. The
feature branch
Having high-level milestones nail down on the umbrella JIRA
HBASE-24749 should be good and should be the next step after we gather
all the feedback.
just a dummy question on how we contribute, should we have a feature
branch? or can we stream into the master if we don't break anything ?
-Stephen
[
https://issues.apache.org/jira/browse/HBASE-24295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk reopened HBASE-24295:
--
Reopen for branch-1 backport.
> [Chaos Monkey] abstract logging through the class hierarchy
>
[
https://issues.apache.org/jira/browse/HBASE-24696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk reopened HBASE-24696:
--
Oops. We missed 2.2.x. Reopening.
> Include JVM information on Web UI under "Software
Yeah, that's the struggle with the multiple branches -- we want to see
our changes in a version of HBase we're using, but that may not be the
right place to land the changes :)
Since this is an "opt-in" and you obviously have _something_ working
(given the benchmarks), I'd suggest breaking
Wellington Chevreuil created HBASE-24758:
Summary: Avoid flooding replication source RSes logs when no sinks
are available
Key: HBASE-24758
URL: https://issues.apache.org/jira/browse/HBASE-24758
Viraj Jasani created HBASE-24757:
Summary: ReplicationSink should limit the batch size for batch
mutations based on hbase.rpc.rows.warning.threshold
Key: HBASE-24757
URL:
Please start a new, dedicated mail thread with an appropriate [DISCUSS]
subject if you want to move the stable pointer to a new minor release line.
On Tue, Jul 21, 2020, 19:56 Guanghao Zhang wrote:
> >
> > Maybe some of the work that went into
> > stabilizing branch-2.3 can be applied?
> >
>
>
Pankaj Kumar created HBASE-24756:
Summary: Backport HBASE-24336 to branch-2.2
Key: HBASE-24756
URL: https://issues.apache.org/jira/browse/HBASE-24756
Project: HBase
Issue Type: Sub-task
mokai created HBASE-24755:
-
Summary: [LOG][RSGroup]Error message is confusing while adding a
offline RS to rsgroup
Key: HBASE-24755
URL: https://issues.apache.org/jira/browse/HBASE-24755
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-24696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani resolved HBASE-24696.
--
Fix Version/s: 1.7.0
Resolution: Fixed
> Include JVM information on Web UI under
[
https://issues.apache.org/jira/browse/HBASE-24696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reopened HBASE-24696:
--
For branch-1 backport.
> Include JVM information on Web UI under "Software Attributes"
>
Thanks Josh, and yeah object store is a bit different lol.
the major reason we didn't try to fold that into meta table were that
we don't know how well meta table can be scale, e.g. as Stack
mentioned about a previous design in HBASE-14090, it matches our
initial estimate that these piece of new
[
https://issues.apache.org/jira/browse/HBASE-24718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani resolved HBASE-24718.
--
Resolution: Fixed
> Generic NamedQueue framework for recent in-memory history (refactor
14 matches
Mail list logo
