[
https://issues.apache.org/jira/browse/HBASE-25057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang resolved HBASE-25057.
Fix Version/s: 2.2.7
2.4.0
2.3.3
3
Mohammad Arshad created HBASE-25069:
---
Summary: Display region name instead of encoded region name for
holes in HBCK report page.
Key: HBASE-25069
URL: https://issues.apache.org/jira/browse/HBASE-25069
It is beneficial for some scenarios where you are going to retain hostnames
via dns or some other way. Example: *server-rs-1* : *10.22.32.11* goes
down, can be replaced with *server-rs-1* : *10.22.32.23. *(only ip has
changed and not the hostname)
On every regionserver restart, you don't have to a
Michael Stack created HBASE-25068:
-
Summary: Pass WALFactory to Replication so it knows of all
WALProviders, not just default/user-space
Key: HBASE-25068
URL: https://issues.apache.org/jira/browse/HBASE-25068
[
https://issues.apache.org/jira/browse/HBASE-25061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25061.
--
Fix Version/s: 3.0.0-alpha-1
Resolution: Fixed
> Update default URL to KEYS file in `hb
Why do we need to track such dead servers which are not going to come back.
Pardon, maybe I missed some pointer.
Any thought?
Regards,
Pankaj
-Original Message-
From: mallik.v.ar...@gmail.com [mailto:mallik.v.ar...@gmail.com]
Sent: Friday, September 18, 2020 11:19 PM
To: dev@hbase.apac
Michael Stack created HBASE-25067:
-
Summary: Edit of log messages around async WAL Replication;
checkstyle fixes; and a bugfix
Key: HBASE-25067
URL: https://issues.apache.org/jira/browse/HBASE-25067
P
Moving any dead region servers to default rsgroup would remove them from
knows server list.
On Fri, Sep 18, 2020, 11:08 PM Pankaj Kumar wrote:
> Dear Folks,
>
> Currently we don’t allow user to remove a dead server from a RSGroup.
>
>
> https://github.com/apache/hbase/blob/e386ec566f89162e4aa082
Dear Folks,
Currently we don’t allow user to remove a dead server from a RSGroup.
https://github.com/apache/hbase/blob/e386ec566f89162e4aa08229f40a708ea3c9a038/hbase-server/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupInfoManagerImpl.java#L899
There can be a scenario where a server is c
Duo Zhang created HBASE-25066:
-
Summary: Use FutureUtils.rethrow in AsyncTableResultScanner to
better catch the stack trace
Key: HBASE-25066
URL: https://issues.apache.org/jira/browse/HBASE-25066
Project:
ramkrishna.s.vasudevan created HBASE-25065:
--
Summary: WAL archival can be batched/throttled and also done by a
separate thread
Key: HBASE-25065
URL: https://issues.apache.org/jira/browse/HBASE-25065
Thanks Wellington and Nick for your help with this RC.
In the wake of rare but quite problematic static initializer issue
(HBASE-24896), we
will sink this RC and include patch (https://github.com/apache/hbase/pull/2417)
for 2.3.2.
Thanks everyone, will be back with new RC after the patch gets in.
[
https://issues.apache.org/jira/browse/HBASE-25060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wellington Chevreuil resolved HBASE-25060.
--
Resolution: Fixed
> [HBOSS] TreeLockManager should not define itself as the de
Duo Zhang created HBASE-25063:
-
Summary: Fan out the edits to root to backup masters
Key: HBASE-25063
URL: https://issues.apache.org/jira/browse/HBASE-25063
Project: HBase
Issue Type: Sub-task
14 matches
Mail list logo
