[
https://issues.apache.org/jira/browse/HBASE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558512#comment-16558512
]
Hadoop QA commented on HBASE-20919:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote ||
[
https://issues.apache.org/jira/browse/HBASE-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558804#comment-16558804
]
Jan Hentschel commented on HBASE-20782:
---
Readded patch -.003 to kick off QA again.
> Fix
[
https://issues.apache.org/jira/browse/HBASE-20782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Hentschel updated HBASE-20782:
--
Attachment: HBASE-20782.master.003.patch
> Fix duplication of TestServletFilter.access
>
[
https://issues.apache.org/jira/browse/HBASE-20962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558878#comment-16558878
]
Josh Elser commented on HBASE-20962:
Posed this question to [~enis] in email. Let me try to
Josh Elser created HBASE-20952:
--
Summary: Re-visit the WAL API
Key: HBASE-20952
URL: https://issues.apache.org/jira/browse/HBASE-20952
Project: HBase
Issue Type: Sub-task
Reporter:
Josh Elser created HBASE-20959:
--
Summary: Port backup and restore to new WAL API
Key: HBASE-20959
URL: https://issues.apache.org/jira/browse/HBASE-20959
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-20952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558650#comment-16558650
]
Sean Busbey commented on HBASE-20952:
-
and fall out for the replication system
> Re-visit the WAL
Josh Elser created HBASE-20954:
--
Summary: Support recovery to read from a LogService WAL
Key: HBASE-20954
URL: https://issues.apache.org/jira/browse/HBASE-20954
Project: HBase
Issue Type:
[
https://issues.apache.org/jira/browse/HBASE-20952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558671#comment-16558671
]
stack commented on HBASE-20952:
---
Old request is reexamination of the WALEdit/WALKey entities because they
[
https://issues.apache.org/jira/browse/HBASE-20894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558834#comment-16558834
]
Hadoop QA commented on HBASE-20894:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-20952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-20952:
Component/s: wal
> Re-visit the WAL API
>
>
> Key:
Josh Elser created HBASE-20961:
--
Summary: Recover RAFT quorum membership loss
Key: HBASE-20961
URL: https://issues.apache.org/jira/browse/HBASE-20961
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558600#comment-16558600
]
Sergey Soldatov commented on HBASE-20927:
-
[~elserj] Almost. After some modifications (removing
Josh Elser created HBASE-20953:
--
Summary: Write to Ratis LogService as a WAL
Key: HBASE-20953
URL: https://issues.apache.org/jira/browse/HBASE-20953
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-20598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558715#comment-16558715
]
Jack Bearden commented on HBASE-20598:
--
Just a quick update on this. I have been investigating the
Josh Elser created HBASE-20956:
--
Summary: Port AsyncFSWAL over to the new WAL API
Key: HBASE-20956
URL: https://issues.apache.org/jira/browse/HBASE-20956
Project: HBase
Issue Type: Sub-task
Josh Elser created HBASE-20957:
--
Summary: Switch replication over to use the new WAL API
Key: HBASE-20957
URL: https://issues.apache.org/jira/browse/HBASE-20957
Project: HBase
Issue Type:
Josh Elser created HBASE-20955:
--
Summary: Port FSHLog to new WAL API
Key: HBASE-20955
URL: https://issues.apache.org/jira/browse/HBASE-20955
Project: HBase
Issue Type: Sub-task
Josh Elser created HBASE-20963:
--
Summary: Benchmark LogService WALs
Key: HBASE-20963
URL: https://issues.apache.org/jira/browse/HBASE-20963
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558736#comment-16558736
]
Mike Drob commented on HBASE-19369:
---
[~awleblang] - do you mind if I take this over?
> HBase Should
[
https://issues.apache.org/jira/browse/HBASE-20930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558541#comment-16558541
]
Vishal Khandelwal commented on HBASE-20930:
---
Thanks [~elserj] for review. I am fine with
Josh Elser created HBASE-20951:
--
Summary: Ratis LogService backed WALs
Key: HBASE-20951
URL: https://issues.apache.org/jira/browse/HBASE-20951
Project: HBase
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/HBASE-20952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558661#comment-16558661
]
Zach York commented on HBASE-20952:
---
I definitely have some thoughts on this. I'll try to summarize
[
https://issues.apache.org/jira/browse/HBASE-20954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-20954:
---
Description: Recovery needs to read from a LogStream and show that it can
replay all edits since
Josh Elser created HBASE-20958:
--
Summary: Port WAL recovery code to use the new WAL API
Key: HBASE-20958
URL: https://issues.apache.org/jira/browse/HBASE-20958
Project: HBase
Issue Type:
[
https://issues.apache.org/jira/browse/HBASE-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558815#comment-16558815
]
Mike Drob commented on HBASE-19369:
---
bq. Anyway I see branch-2.9 has already been cut and EC is not
Josh Elser created HBASE-20960:
--
Summary: Expose Ratis LogService metrics
Key: HBASE-20960
URL: https://issues.apache.org/jira/browse/HBASE-20960
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-20952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558809#comment-16558809
]
Josh Elser commented on HBASE-20952:
{quote}and fall out for the replication system
{quote}
Thanks
[
https://issues.apache.org/jira/browse/HBASE-20952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558805#comment-16558805
]
Josh Elser commented on HBASE-20952:
{quote}I definitely have some thoughts on this. I'll try to
[
https://issues.apache.org/jira/browse/HBASE-20952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-20952:
---
Description:
Take a step back from the current WAL implementations and think about what an
HBase
[
https://issues.apache.org/jira/browse/HBASE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-20927:
---
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: (was: 2.1.1)
[
https://issues.apache.org/jira/browse/HBASE-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558845#comment-16558845
]
Hudson commented on HBASE-18477:
Results for branch HBASE-18477
[build #276 on
[
https://issues.apache.org/jira/browse/HBASE-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558885#comment-16558885
]
Alex Leblang commented on HBASE-19369:
--
[~mdrob] I stalled on this patch and then unfortunately
[
https://issues.apache.org/jira/browse/HBASE-20949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559086#comment-16559086
]
Duo Zhang commented on HBASE-20949:
---
Confirmed, there are duplicated release lock acquires. Let me
[
https://issues.apache.org/jira/browse/HBASE-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob updated HBASE-19369:
--
Assignee: Mike Drob (was: Alex Leblang)
Fix Version/s: 2.2.0
Status: Open (was:
[
https://issues.apache.org/jira/browse/HBASE-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob updated HBASE-19369:
--
Fix Version/s: 3.0.0
Status: Patch Available (was: Open)
> HBase Should use Builder
[
https://issues.apache.org/jira/browse/HBASE-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559150#comment-16559150
]
Mike Drob commented on HBASE-19369:
---
v9: Finishes the EC test setup, verified that this test fails
[
https://issues.apache.org/jira/browse/HBASE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-20939:
--
Priority: Critical (was: Major)
> There will be race when we call suspendIfNotReady and then throw
>
[
https://issues.apache.org/jira/browse/HBASE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-20939:
--
Fix Version/s: 2.0.1
2.1.1
2.2.0
3.0.0
> There will
[
https://issues.apache.org/jira/browse/HBASE-18152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559196#comment-16559196
]
stack commented on HBASE-18152:
---
I think HBASE-20939 uncovers the root of corruption I've been trying to
[
https://issues.apache.org/jira/browse/HBASE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-20939:
--
Component/s: amv2
> There will be race when we call suspendIfNotReady and then throw
>
[
https://issues.apache.org/jira/browse/HBASE-20930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559268#comment-16559268
]
Vishal Khandelwal commented on HBASE-20930:
---
I have uploaded the new patch [~elserj]
>
[
https://issues.apache.org/jira/browse/HBASE-20964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-20964.
-
Resolution: Invalid
Fix Version/s: (was: hbase-7290)
> test
>
>
>
zhou pengbo created HBASE-20964:
---
Summary: test
Key: HBASE-20964
URL: https://issues.apache.org/jira/browse/HBASE-20964
Project: HBase
Issue Type: Test
Components: Client
Affects
[
https://issues.apache.org/jira/browse/HBASE-20657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Soldatov reassigned HBASE-20657:
---
Assignee: Sergey Soldatov (was: stack)
> Retrying RPC call for
[
https://issues.apache.org/jira/browse/HBASE-20657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558989#comment-16558989
]
Sergey Soldatov commented on HBASE-20657:
-
Oops. accidentally switched to branch-2 from master.
[
https://issues.apache.org/jira/browse/HBASE-20734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559009#comment-16559009
]
Zach York commented on HBASE-20734:
---
PR [https://github.com/apache/hbase/pull/86] contains the master
[
https://issues.apache.org/jira/browse/HBASE-20949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559091#comment-16559091
]
Duo Zhang commented on HBASE-20949:
---
The problem here is that, we seem to finish the procedure twice.
[
https://issues.apache.org/jira/browse/HBASE-20949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559101#comment-16559101
]
Duo Zhang commented on HBASE-20949:
---
OK I think the problem here is something like HBASE-20939.
After
[
https://issues.apache.org/jira/browse/HBASE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reassigned HBASE-20939:
-
Assignee: Duo Zhang
> There will be race when we call suspendIfNotReady and then throw
>
[
https://issues.apache.org/jira/browse/HBASE-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob updated HBASE-19369:
--
Attachment: HBASE-19369.v9.patch
> HBase Should use Builder Pattern to Create Log Files while using
[
https://issues.apache.org/jira/browse/HBASE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559189#comment-16559189
]
stack commented on HBASE-20939:
---
Your scenario would explain the WAL corruption that I'm seeing over in
[
https://issues.apache.org/jira/browse/HBASE-20893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559293#comment-16559293
]
stack commented on HBASE-20893:
---
Here is an addendum that changes split and merge to just reopen regions
[
https://issues.apache.org/jira/browse/HBASE-20893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-20893:
--
Status: Patch Available (was: Reopened)
> Data loss if splitting region while ServerCrashProcedure executing
[
https://issues.apache.org/jira/browse/HBASE-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559237#comment-16559237
]
Hadoop QA commented on HBASE-19369:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-20930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Khandelwal updated HBASE-20930:
--
Attachment: HBASE-20930.branch-1.3.v2.patch
> MetaScanner.metaScan should use passed
[
https://issues.apache.org/jira/browse/HBASE-20893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-20893:
--
Attachment: HBASE-20893-branch-2.0.addendum.patch
> Data loss if splitting region while ServerCrashProcedure
[
https://issues.apache.org/jira/browse/HBASE-20885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556942#comment-16556942
]
Sakthi commented on HBASE-20885:
[~elserj] or [~md...@cloudera.com] could you please review this?
>
[
https://issues.apache.org/jira/browse/HBASE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Soldatov updated HBASE-20927:
Attachment: HBASE-20927-master.patch
> RSGroupAdminEndpoint doesn't handle clearing dead
[
https://issues.apache.org/jira/browse/HBASE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Soldatov updated HBASE-20927:
Fix Version/s: 3.0.0
> RSGroupAdminEndpoint doesn't handle clearing dead servers if they
[
https://issues.apache.org/jira/browse/HBASE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556969#comment-16556969
]
Ted Yu commented on HBASE-20927:
lgtm
I wonder if it is possible to write a unit test.
Thanks
>
[
https://issues.apache.org/jira/browse/HBASE-20935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16557993#comment-16557993
]
Hadoop QA commented on HBASE-20935:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote ||
[
https://issues.apache.org/jira/browse/HBASE-18822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556962#comment-16556962
]
Pankaj Kumar commented on HBASE-18822:
--
{quote}Depends on the peer's replicateAllUserTables, if
[
https://issues.apache.org/jira/browse/HBASE-20930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556959#comment-16556959
]
Hadoop QA commented on HBASE-20930:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556972#comment-16556972
]
Ted Yu commented on HBASE-20919:
QA bot finds latest attachment but doesn't know how to handle it:
[
https://issues.apache.org/jira/browse/HBASE-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-20919:
---
Attachment: HBASE-20919-branch-2.0-02.patch
> meta region can't be re-onlined when restarting cluster if
[
https://issues.apache.org/jira/browse/HBASE-17885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558002#comment-16558002
]
jamjae kim commented on HBASE-17885:
I try it again.
(branch-1 and git apply)
many deletion, and
[
https://issues.apache.org/jira/browse/HBASE-20886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556957#comment-16556957
]
Hadoop QA commented on HBASE-20886:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-18822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16556966#comment-16556966
]
Ashish Singhi commented on HBASE-18822:
---
bq. Ashish Singhi also have the same concern I guess.
No,
[
https://issues.apache.org/jira/browse/HBASE-20896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikas Vishwakarma updated HBASE-20896:
--
Attachment: HBASE-20896.branch-1.4.003.patch
> Port HBASE-20866 to branch-1 and
[
https://issues.apache.org/jira/browse/HBASE-20657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Soldatov updated HBASE-20657:
Attachment: HBASE-20657-4-master.patch
> Retrying RPC call for ModifyTableProcedure may
[
https://issues.apache.org/jira/browse/HBASE-20927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559080#comment-16559080
]
Hudson commented on HBASE-20927:
Results for branch branch-2
[build #1030 on
[
https://issues.apache.org/jira/browse/HBASE-20921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allan Yang updated HBASE-20921:
---
Resolution: Fixed
Fix Version/s: 2.1.1
2.0.2
3.0.0
[
https://issues.apache.org/jira/browse/HBASE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559190#comment-16559190
]
stack commented on HBASE-20939:
---
Oh, when I was staring at it, the above is all happening under region
[
https://issues.apache.org/jira/browse/HBASE-19008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559198#comment-16559198
]
liubangchen commented on HBASE-19008:
-
[~Jan Hentschel] If you have no time, I can take this
[
https://issues.apache.org/jira/browse/HBASE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559217#comment-16559217
]
stack commented on HBASE-20939:
---
+1 on patch. Please put it in branch-2.0+. I'll test it.
> There will be
[
https://issues.apache.org/jira/browse/HBASE-20893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559201#comment-16559201
]
stack commented on HBASE-20893:
---
So, Split does not support rollback at the
[
https://issues.apache.org/jira/browse/HBASE-20657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Soldatov reassigned HBASE-20657:
---
Assignee: stack (was: Sergey Soldatov)
> Retrying RPC call for
[
https://issues.apache.org/jira/browse/HBASE-20885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sakthi updated HBASE-20885:
---
Attachment: hbase-20885.master.003.patch
> Remove entry for RPC quota from hbase:quota when RPC quota is
[
https://issues.apache.org/jira/browse/HBASE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559193#comment-16559193
]
Duo Zhang commented on HBASE-20939:
---
It could lead to a reorder but for most cases, we are likely to
[
https://issues.apache.org/jira/browse/HBASE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559194#comment-16559194
]
stack commented on HBASE-20939:
---
So IdLock is about serializing thread access and region lock is about
[
https://issues.apache.org/jira/browse/HBASE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559199#comment-16559199
]
Duo Zhang commented on HBASE-20939:
---
{quote}
So IdLock is about serializing thread access and region
[
https://issues.apache.org/jira/browse/HBASE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559200#comment-16559200
]
Duo Zhang commented on HBASE-20939:
---
To speak clearer, the procedure lock is to prevent other
[
https://issues.apache.org/jira/browse/HBASE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559209#comment-16559209
]
stack commented on HBASE-20939:
---
bq. but it can not prevent the same procedure to be executed parallel
[
https://issues.apache.org/jira/browse/HBASE-20828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559208#comment-16559208
]
stack commented on HBASE-20828:
---
Explain that there are "two dimensions" of exclusivity when we talk about
[
https://issues.apache.org/jira/browse/HBASE-19008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558634#comment-16558634
]
Jan Hentschel commented on HBASE-19008:
---
[~yuzhih...@gmail.com] Yes, we should definitely do this.
Josh Elser created HBASE-20962:
--
Summary: LogStream Metadata Tracking
Key: HBASE-20962
URL: https://issues.apache.org/jira/browse/HBASE-20962
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-20734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558921#comment-16558921
]
Zach York commented on HBASE-20734:
---
Sorry it took so long to get the master patch up. I'll be
[
https://issues.apache.org/jira/browse/HBASE-20874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559014#comment-16559014
]
Mohit Goel commented on HBASE-20874:
Review Link : https://reviews.apache.org/r/68035/
> Sending
[
https://issues.apache.org/jira/browse/HBASE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20939:
--
Attachment: HBASE-20939.patch
> There will be race when we call suspendIfNotReady and then throw
>
[
https://issues.apache.org/jira/browse/HBASE-20939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20939:
--
Status: Patch Available (was: Open)
> There will be race when we call suspendIfNotReady and then
[
https://issues.apache.org/jira/browse/HBASE-20657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Soldatov updated HBASE-20657:
Fix Version/s: 3.0.0
> Retrying RPC call for ModifyTableProcedure may get stuck
>
[
https://issues.apache.org/jira/browse/HBASE-20657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558974#comment-16558974
]
Hadoop QA commented on HBASE-20657:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem
[
https://issues.apache.org/jira/browse/HBASE-20657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558973#comment-16558973
]
Sergey Soldatov commented on HBASE-20657:
-
Removed the internal lock implementation, thanks
[
https://issues.apache.org/jira/browse/HBASE-20886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reid Chan updated HBASE-20886:
--
Attachment: HBASE-20886.master.007.patch
> [Auth] Support keytab login in hbase client
>
[
https://issues.apache.org/jira/browse/HBASE-20944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Korablev updated HBASE-20944:
---
Environment:
First env:
{code:java}
[
https://issues.apache.org/jira/browse/HBASE-20944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-20944.
---
Resolution: Invalid
Jira is for fixing bugs, not for asking questions.
Please send emails to
[
https://issues.apache.org/jira/browse/HBASE-20945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558113#comment-16558113
]
Hari Sekhon commented on HBASE-20945:
-
I'm also seeing a period of over 2 weeks between 7th and 24th
[
https://issues.apache.org/jira/browse/HBASE-20945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Sekhon updated HBASE-20945:
Affects Version/s: 1.1.2
> HBase JMX - timestamp of last Major Compaction (started, completed
>
[
https://issues.apache.org/jira/browse/HBASE-20945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Sekhon updated HBASE-20945:
Description:
Request that the timestamp of the last major compaction be stored in JMX API
1 - 100 of 167 matches
Mail list logo