Duo Zhang created HBASE-24646:
-
Summary: Set the log level for ScheduledChore to INFO in HBTU
Key: HBASE-24646
URL: https://issues.apache.org/jira/browse/HBASE-24646
Project: HBase
Issue Type:
Heya,
I've seen a lot of use-cases where the normalizer would be a nice solution
for operators and application developers. I've been trying to beef it up a
bit to handle these cases. However, some of these considerations are at
odds, so I want to vet the ideas here.
The normalizer is a
[
https://issues.apache.org/jira/browse/HBASE-20819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-20819.
---
Resolution: Fixed
Merged. Thanks for nice contrib [~bitoffdev] (thanks for reviews
Nick Dimiduk created HBASE-24645:
Summary: Include dump files in the jenkins archive
Key: HBASE-24645
URL: https://issues.apache.org/jira/browse/HBASE-24645
Project: HBase
Issue Type: Task
Circling back after more inputs, if we use this as a description of the
proposals:
1. Replace "master"/"hmaster" with ???, this one has by far the most
significant impact and both opinion and interpretation on this one is mixed.
2. Replace "slave" with "follower", seems to impact the cross
Hey Anoop, I opened https://issues.apache.org/jira/browse/HBASE-24637 and
attached the patches and script used to make the comparison.
On Fri, Jun 26, 2020 at 2:33 AM Anoop John wrote:
> Great investigation Andy. Do you know any Jiras which made changes in SQM?
> Would be great if you can
Nick Dimiduk created HBASE-24644:
Summary: Add a clause to the book noting that sometimes we
short-circuit the deprecation cycle
Key: HBASE-24644
URL: https://issues.apache.org/jira/browse/HBASE-24644
Huaxiang Sun created HBASE-24643:
Summary: Replace Cluster#primariesOfRegionsPerServer from int
array to treemap
Key: HBASE-24643
URL: https://issues.apache.org/jira/browse/HBASE-24643
Project: HBase
> Is there a word that's not "master" and not "coordinator" that is clear
and
suitable for (diverse, polyglot) community?
There are also:
- captain (sounds pretty close to "master" without the negative side and it
should be relatable around the world)
- conductor (as in orchestra)
- controller
Bharath Vissapragada created HBASE-24642:
Summary: Apache Yetus integration
Key: HBASE-24642
URL: https://issues.apache.org/jira/browse/HBASE-24642
Project: HBase
Issue Type:
Bharath Vissapragada created HBASE-24641:
Summary: Add linter checks for patches
Key: HBASE-24641
URL: https://issues.apache.org/jira/browse/HBASE-24641
Project: HBase
Issue Type:
I've restored the previous method signature to LoadIncrementalHFiles, so
that piece is complete for the next RC.
Based on the latest comments, let me update my proposed course of action.
1. restore any VisibleForTesting method signatures for 2.3.0, treat this as
public API going forward.
2.
Nick Dimiduk created HBASE-24640:
Summary: Purge use of VisibleForTesting
Key: HBASE-24640
URL: https://issues.apache.org/jira/browse/HBASE-24640
Project: HBase
Issue Type: Task
[
https://issues.apache.org/jira/browse/HBASE-24221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-24221.
--
Fix Version/s: (was: 2.4.0)
Resolution: Fixed
And branch-2.2. Thanks for the
[
https://issues.apache.org/jira/browse/HBASE-24221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk reopened HBASE-24221:
--
Reopening, pardon. need branch-2.2 as well.
> Support bulkLoadHFile by family
>
[
https://issues.apache.org/jira/browse/HBASE-24221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-24221.
--
Resolution: Fixed
Addendum pushed to branch-2 and branch-2.3.
> Support bulkLoadHFile by
[
https://issues.apache.org/jira/browse/HBASE-24638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-24638.
---
Fix Version/s: 3.0.0-alpha-1
Assignee: Michael Stack
Resolution: Fixed
For the LoadIncrementalHFiles class, the IA.Public annotation itself is a
problem. It should be IA.LimitPrivate(TOOLS). So I'm fine with either
adding the method back or not, the opinion of the release manager is
most important I think.
Thanks.
Viraj Jasani 于2020年6月26日周五 下午9:50写道：
> Agree on
Agree on replacing VFT in next 2.4.0 or 3.0.0 release and restoring the required
method for now to unblock 2.3.0 RC1.
On 2020/06/26 01:11:31, Andrew Purtell wrote:
> Sounds fine to me.
>
> My earlier objection was to talk of an HBase 3 followed by an HBase 4. We
> don't need to do a full
Pranshu Khandelwal created HBASE-24639:
--
Summary: RequestId Tracing feature for HBase
Key: HBASE-24639
URL: https://issues.apache.org/jira/browse/HBASE-24639
Project: HBase
Issue Type:
[
https://issues.apache.org/jira/browse/HBASE-24626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wellington Chevreuil resolved HBASE-24626.
--
Resolution: Fixed
Merged to master.
> [HBCK2] Remove reference to hase I.A.
Great investigation Andy. Do you know any Jiras which made changes in SQM?
Would be great if you can attach your patch which tracks the scan flow. If
we have a Jira for this issue, can you pls attach?
Anoop
On Fri, Jun 26, 2020 at 1:56 AM Andrew Purtell
wrote:
> Related, I think I found a
>
> It's supposed to be controlling how big the region is?
>
Precisely. It may not make a big difference for compaction itself, but
might have further implications on overall RS resource usage, with larger
than expected regions. Given the feedback provided here, I guess we can
proceed with
Michael Stack created HBASE-24638:
-
Summary: Edit doc on (offheap) memory management
Key: HBASE-24638
URL: https://issues.apache.org/jira/browse/HBASE-24638
Project: HBase
Issue Type:
24 matches
Mail list logo
