Reid Chan created HBASE-21390:
-
Summary: [test] TestRpcAccessChecks is buggy
Key: HBASE-21390
URL: https://issues.apache.org/jira/browse/HBASE-21390
Project: HBase
Issue Type: Improvement
On Thu, Oct 25, 2018 at 4:50 PM Josh Elser wrote:
> Stack just hit me up in Slack. He suggested wiping the
> data/hbase/namespace and the relevant rows in hbase:meta.
>
> Fine "fix" for me given I didn't have anything in there besides the
> default ns.
>
>
2.0.3 should allow us do better. It has
Duo Zhang created HBASE-21389:
-
Summary: Revisit the procedure lock for sync replication
Key: HBASE-21389
URL: https://issues.apache.org/jira/browse/HBASE-21389
Project: HBase
Issue Type:
Guanghao Zhang created HBASE-21388:
--
Summary: No need to instantiate MemStore for master which not
carry table
Key: HBASE-21388
URL: https://issues.apache.org/jira/browse/HBASE-21388
Project: HBase
Stack just hit me up in Slack. He suggested wiping the
data/hbase/namespace and the relevant rows in hbase:meta.
Fine "fix" for me given I didn't have anything in there besides the
default ns.
On 10/25/18 5:47 PM, Josh Elser wrote:
Hey Stephen,
Thanks for the reply.
I'm not concerned
[
https://issues.apache.org/jira/browse/HBASE-9559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-9559.
--
Resolution: Won't Fix
We don't use getRowAtOrBefore anymore. Removed in hbase-2.
> getRowKeyAtOrBefore may be
[
https://issues.apache.org/jira/browse/HBASE-7044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-7044.
--
Resolution: Won't Fix
Resolving old issue w/ no progress.
> verifyRegionLocation in CatalogTracker.java
[
https://issues.apache.org/jira/browse/HBASE-7959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-7959.
--
Resolution: Won't Fix
Resolving old issue that has had no work done.
> HBCK skips regions that have been
[
https://issues.apache.org/jira/browse/HBASE-13535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-13535.
---
Resolution: Invalid
No DLR anymore. Assignment is different now.
> Regions go unassigned when
[
https://issues.apache.org/jira/browse/HBASE-17801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-17801.
---
Resolution: Cannot Reproduce
Resolving as 'cannot reproduce'
> Assigning dead region causing FAILED_OPEN
[
https://issues.apache.org/jira/browse/HBASE-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-6184.
--
Resolution: Cannot Reproduce
Resolving old issue that we don't see anymore as 'cannot reproduce'
>
[
https://issues.apache.org/jira/browse/HBASE-15355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-15355.
---
Resolution: Won't Fix
This issue became invalid after we ruled out master hosting Regions (See above
for
Hey Stephen,
Thanks for the reply.
I'm not concerned about the cause at this point as I haven't done
due-diligence yet. I am looking for any tips on how to fix this by hand
(prior to hbck2).
I thought I could trick the master into assigning it by messing with the
row in meta, but I've not
Ted Yu created HBASE-21387:
--
Summary: Race condition in snapshot cache refreshing leads to loss
of snapshot files
Key: HBASE-21387
URL: https://issues.apache.org/jira/browse/HBASE-21387
Project: HBase
Not sure if this is related to
https://issues.apache.org/jira/browse/HBASE-20671
if so, and if you have HBASE-20702 on your branch, when a new cluster that
master starts on the
same root directory (my case is on root directory is on S3),
hbase:namespace table cannot be assigned.
(Sorry that I
[
https://issues.apache.org/jira/browse/HBASE-18152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-18152.
---
Resolution: Cannot Reproduce
Closing as 'Cannot Reproduce' Haven seen this in months. It looks like its
I hear what you're saying, but I'd also be pissed if we waste our own
time dealing with Hadoop issues that have already been addressed. Just
my feeling, but I think I'm distracting from the original question at
this point.
On 10/24/18 5:01 PM, Sean Busbey wrote:
Yes, because they deployed
I have a cluster on branch-2.0 from a week or two ago where
hbase:namespace is not assigned (haven't figured out why yet), I can't
use any of the normal assign/move shell commands because the Master is
useless as it's not initialized (because hbase:namespace is
unreachable), but I can't figure
stack created HBASE-21386:
-
Summary: Disable TestRSGroups#testRSGroupsWithHBaseQuota; causes
TestRSGroups to fail in branch-2.1.
Key: HBASE-21386
URL: https://issues.apache.org/jira/browse/HBASE-21386
Guanghao Zhang created HBASE-21385:
--
Summary: HTable.delete request use rpc call directly instead of
AsyncProcess
Key: HBASE-21385
URL: https://issues.apache.org/jira/browse/HBASE-21385
Project:
20 matches
Mail list logo