[jira] [Resolved] (HBASE-26010) Backport HBASE-25703 and HBASE-26002 to branch-2.3
[ https://issues.apache.org/jira/browse/HBASE-26010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-26010. -- Resolution: Won't Fix > Backport HBASE-25703 and HBASE-26002 to branch-2.3 > -- > > Key: HBASE-26010 > URL: https://issues.apache.org/jira/browse/HBASE-26010 > Project: HBase > Issue Type: Improvement > Components: backport >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 2.3.6 > > > Backport HBASE-25703 "Support conditional update in MultiRowMutationEndpoint" > and HBASE-26002 "MultiRowMutationEndpoint should return the result of the > conditional update" to branch-2.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-26009) Backport HBASE-25766 "Introduce RegionSplitRestriction that restricts the pattern of the split point" to branch-2.3
[ https://issues.apache.org/jira/browse/HBASE-26009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-26009. -- Resolution: Won't Fix > Backport HBASE-25766 "Introduce RegionSplitRestriction that restricts the > pattern of the split point" to branch-2.3 > --- > > Key: HBASE-26009 > URL: https://issues.apache.org/jira/browse/HBASE-26009 > Project: HBase > Issue Type: Sub-task >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 2.3.6 > > > Backport the parent issue to branch-2.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-26010) Backport HBASE-25703 and HBASE-26002 to branch-2.3
Toshihiro Suzuki created HBASE-26010: Summary: Backport HBASE-25703 and HBASE-26002 to branch-2.3 Key: HBASE-26010 URL: https://issues.apache.org/jira/browse/HBASE-26010 Project: HBase Issue Type: Bug Components: backport Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Backport HBASE-25703 "Support conditional update in MultiRowMutationEndpoint" and HBASE-26002 "MultiRowMutationEndpoint should return the result of the conditional update" to branch-2.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-26009) Backport HBASE-25766 "Introduce RegionSplitRestriction that restricts the pattern of the split point" to branch-2.3
Toshihiro Suzuki created HBASE-26009: Summary: Backport HBASE-25766 "Introduce RegionSplitRestriction that restricts the pattern of the split point" to branch-2.3 Key: HBASE-26009 URL: https://issues.apache.org/jira/browse/HBASE-26009 Project: HBase Issue Type: Sub-task Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Backport the parent issue to branch-2.3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-26002) MultiRowMutationEndpoint should return the result of the conditional update
[ https://issues.apache.org/jira/browse/HBASE-26002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-26002. -- Hadoop Flags: Reviewed Resolution: Fixed > MultiRowMutationEndpoint should return the result of the conditional update > --- > > Key: HBASE-26002 > URL: https://issues.apache.org/jira/browse/HBASE-26002 > Project: HBase > Issue Type: Improvement > Components: Coprocessors >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.5 > > > HBASE-25703 added support for the conditional update in > MultiRowMutationEndpoint, but MultiRowMutationEndpoint doesn't return the > result of the conditional update (whether or not the mutations are executed). > In this Jira, we will make MultiRowMutationEndpoint return the result of the > conditional update. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-26002) MultiRowMutationEndpoint should return the result of the conditional update
Toshihiro Suzuki created HBASE-26002: Summary: MultiRowMutationEndpoint should return the result of the conditional update Key: HBASE-26002 URL: https://issues.apache.org/jira/browse/HBASE-26002 Project: HBase Issue Type: Improvement Components: Coprocessors Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki HBASE-25703 added support for the conditional update in MultiRowMutationEndpoint, but MultiRowMutationEndpoint doesn't return the result of the conditional update (whether or not the mutations are executed). In this Jira, we will make MultiRowMutationEndpoint return the result of the conditional update. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25766) Introduce RegionSplitRestriction that restricts the pattern of the split point
[ https://issues.apache.org/jira/browse/HBASE-25766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-25766. -- Hadoop Flags: Reviewed Resolution: Fixed > Introduce RegionSplitRestriction that restricts the pattern of the split point > -- > > Key: HBASE-25766 > URL: https://issues.apache.org/jira/browse/HBASE-25766 > Project: HBase > Issue Type: Improvement >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3 > > > As discussed in HBASE-25706, we can introduce RegionSplitRestriction that > restricts the pattern of the split point. > See the following comment for the details: > https://issues.apache.org/jira/browse/HBASE-25706?focusedCommentId=17310190=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17310190 > CC: [~zhangduo] [~stack] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25706) Support specifying a base split policy class in KeyPrefixRegionSplitPolicy and DelimitedKeyPrefixRegionSplitPolicy
[ https://issues.apache.org/jira/browse/HBASE-25706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-25706. -- Resolution: Won't Fix Closing this Jira and opened a new Jira HBASE-25766 to introduce RegionSplitPointRestriction. > Support specifying a base split policy class in KeyPrefixRegionSplitPolicy > and DelimitedKeyPrefixRegionSplitPolicy > -- > > Key: HBASE-25706 > URL: https://issues.apache.org/jira/browse/HBASE-25706 > Project: HBase > Issue Type: Improvement >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > > Basically, I think we can use KeyPrefixRegionSplitPolicy and > DelimitedKeyPrefixRegionSplitPolicy along with other split policies. In this > Jira, we will support specifying a base split policy class in > KeyPrefixRegionSplitPolicy and DelimitedKeyPrefixRegionSplitPolicy to use > them with different split policies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25766) Introduce RegionSplitPointRestriction that restricts the pattern of the split point
Toshihiro Suzuki created HBASE-25766: Summary: Introduce RegionSplitPointRestriction that restricts the pattern of the split point Key: HBASE-25766 URL: https://issues.apache.org/jira/browse/HBASE-25766 Project: HBase Issue Type: Improvement Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Fix For: 3.0.0-alpha-1, 2.4.3 As discussed in HBASE-25706, we can introduce RegionSplitPointRestriction that restricts the pattern of the split point. See the following comment for the details: https://issues.apache.org/jira/browse/HBASE-25706?focusedCommentId=17310190=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17310190 CC: [~zhangduo] [~stack] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25703) Support conditional update in MultiRowMutationEndpoint
[ https://issues.apache.org/jira/browse/HBASE-25703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-25703. -- Hadoop Flags: Reviewed Resolution: Fixed > Support conditional update in MultiRowMutationEndpoint > -- > > Key: HBASE-25703 > URL: https://issues.apache.org/jira/browse/HBASE-25703 > Project: HBase > Issue Type: Improvement > Components: Coprocessors >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3 > > > In some use cases, I think it will be useful that we can perform conditional > update in MultiRowMutationEndpoint. In this Jira, we can add support > conditional update in MultiRowMutationEndpoint. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25706) Support specifying a base split policy class in KeyPrefixRegionSplitPolicy to make it more useful
Toshihiro Suzuki created HBASE-25706: Summary: Support specifying a base split policy class in KeyPrefixRegionSplitPolicy to make it more useful Key: HBASE-25706 URL: https://issues.apache.org/jira/browse/HBASE-25706 Project: HBase Issue Type: Improvement Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Basically, I think we can use KeyPrefixRegionSplitPolicy along with other split policies. In this Jira, we will support specifying a base split policy class in KeyPrefixRegionSplitPolicy to use it with different split policies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25702) Remove RowProcessor
[ https://issues.apache.org/jira/browse/HBASE-25702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-25702. -- Hadoop Flags: Reviewed Resolution: Fixed > Remove RowProcessor > --- > > Key: HBASE-25702 > URL: https://issues.apache.org/jira/browse/HBASE-25702 > Project: HBase > Issue Type: Improvement >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1 > > > As RowProcessor is deprecated, we can remove it in this Jira. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25704) Support conditional update in MultiRowMutationEndpoint
[ https://issues.apache.org/jira/browse/HBASE-25704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-25704. -- Resolution: Duplicate > Support conditional update in MultiRowMutationEndpoint > -- > > Key: HBASE-25704 > URL: https://issues.apache.org/jira/browse/HBASE-25704 > Project: HBase > Issue Type: Improvement > Components: Coprocessors >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3 > > > In some use cases, I think it will be useful that we can perform conditional > update in MultiRowMutationEndpoint. In this Jira, we can add support > conditional update in MultiRowMutationEndpoint. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25704) Support conditional update in MultiRowMutationEndpoint
Toshihiro Suzuki created HBASE-25704: Summary: Support conditional update in MultiRowMutationEndpoint Key: HBASE-25704 URL: https://issues.apache.org/jira/browse/HBASE-25704 Project: HBase Issue Type: Improvement Components: Coprocessors Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3 In some use cases, I think it will be useful that we can perform conditional update in MultiRowMutationEndpoint. In this Jira, we can add support conditional update in MultiRowMutationEndpoint. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25703) Support conditional update in MultiRowMutationEndpoint
Toshihiro Suzuki created HBASE-25703: Summary: Support conditional update in MultiRowMutationEndpoint Key: HBASE-25703 URL: https://issues.apache.org/jira/browse/HBASE-25703 Project: HBase Issue Type: Improvement Components: Coprocessors Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3 In some use cases, I think it will be useful that we can perform conditional update in MultiRowMutationEndpoint. In this Jira, we can add support conditional update in MultiRowMutationEndpoint. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25686) [hbtop] Add some javadoc
[ https://issues.apache.org/jira/browse/HBASE-25686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-25686. -- Hadoop Flags: Reviewed Resolution: Fixed > [hbtop] Add some javadoc > > > Key: HBASE-25686 > URL: https://issues.apache.org/jira/browse/HBASE-25686 > Project: HBase > Issue Type: Improvement > Components: hbtop >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Minor > Fix For: 3.0.0-alpha-1, 1.7.0, 2.5.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25702) Remove RowProcessor
Toshihiro Suzuki created HBASE-25702: Summary: Remove RowProcessor Key: HBASE-25702 URL: https://issues.apache.org/jira/browse/HBASE-25702 Project: HBase Issue Type: Improvement Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Fix For: 3.0.0-alpha-1 As RowProcessor is deprecated, we can remove it in this Jira. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25678) Support nonce operations for Increment/Append in RowMutations and CheckAndMutate
[ https://issues.apache.org/jira/browse/HBASE-25678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-25678. -- Hadoop Flags: Reviewed Resolution: Fixed > Support nonce operations for Increment/Append in RowMutations and > CheckAndMutate > > > Key: HBASE-25678 > URL: https://issues.apache.org/jira/browse/HBASE-25678 > Project: HBase > Issue Type: Improvement >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3 > > > Currently, we support nonce operations for single Increment/Append operations > but don't support for Increment/Append in RowMutations and CheckAndMutate. We > should support it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25686) [hbtop] Add some javadoc
Toshihiro Suzuki created HBASE-25686: Summary: [hbtop] Add some javadoc Key: HBASE-25686 URL: https://issues.apache.org/jira/browse/HBASE-25686 Project: HBase Issue Type: Improvement Components: hbtop Reporter: Toshihiro Suzuki -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25258) Backport HBASE-24776 "[hbtop] Support Batch mode" to branch-1
[ https://issues.apache.org/jira/browse/HBASE-25258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-25258. -- Fix Version/s: 1.7.0 Hadoop Flags: Reviewed Resolution: Fixed > Backport HBASE-24776 "[hbtop] Support Batch mode" to branch-1 > - > > Key: HBASE-25258 > URL: https://issues.apache.org/jira/browse/HBASE-25258 > Project: HBase > Issue Type: Sub-task >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 1.7.0 > > > Backport parent issue to branch-1. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25678) Support nonce operations for Increment/Append in RowMutations and CheckAndMutate
Toshihiro Suzuki created HBASE-25678: Summary: Support nonce operations for Increment/Append in RowMutations and CheckAndMutate Key: HBASE-25678 URL: https://issues.apache.org/jira/browse/HBASE-25678 Project: HBase Issue Type: Improvement Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Fix For: 3.0.0-alpha-1, 2.4.3 Currently, we support nonce operations for single Increment/Append operations but don't support for Increment/Append in RowMutations and CheckAndMutate. We should support it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25575) Should validate Puts in RowMutations
[ https://issues.apache.org/jira/browse/HBASE-25575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-25575. -- Hadoop Flags: Reviewed Resolution: Fixed > Should validate Puts in RowMutations > > > Key: HBASE-25575 > URL: https://issues.apache.org/jira/browse/HBASE-25575 > Project: HBase > Issue Type: Bug > Components: Client >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Minor > Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.2 > > > Currently, we don't validate the key value sizes of Puts in RowMutations. We > should do that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25574) Revisit put/delete/increment/append related RegionObserver methods
[ https://issues.apache.org/jira/browse/HBASE-25574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-25574. -- Hadoop Flags: Reviewed Resolution: Fixed > Revisit put/delete/increment/append related RegionObserver methods > -- > > Key: HBASE-25574 > URL: https://issues.apache.org/jira/browse/HBASE-25574 > Project: HBase > Issue Type: Improvement > Components: Coprocessors >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.2 > > > After HBASE-24602, increment/append operations are performed in > HRegion.batchMutate(). Accordingly, we should make some changes for the > increment/append related RegionObserver methods. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25576) Should not use HashMap (ConcurrentHashMap) or HashSet when using byte[] as a key of Map or an element of Set
Toshihiro Suzuki created HBASE-25576:
Summary: Should not use HashMap (ConcurrentHashMap) or HashSet
when using byte[] as a key of Map or an element of Set
Key: HBASE-25576
URL: https://issues.apache.org/jira/browse/HBASE-25576
Project: HBase
Issue Type: Bug
Reporter: Toshihiro Suzuki
I sometimes face the code using HashMap (ConcurrentHashMap) or HashSet when
using byte[] as a key of Map or an element of Set in the HBase code, which
could cause very confusing bugs.
We should use TreeMap (ConcurrentSkipListMap) or TreeSet
(ConcurrentSkipListSet) with Bytes.BYTES_COMPARATOR when using byte[] as a key
of Map or an element of Set as follows:
{code}
Map map1 = new TreeMap<>(Bytes.BYTES_COMPARATOR);
Map map2 = new ConcurrentSkipListMap<>(Bytes.BYTES_COMPARATOR);
Set set1 = new TreeSet<>(Bytes.BYTES_COMPARATOR);
Set set2 = new ConcurrentSkipListSet<>(Bytes.BYTES_COMPARATOR);
{code}
We should fix the existing ones in this Jira.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-25575) Should validate Puts in RowMutations
Toshihiro Suzuki created HBASE-25575: Summary: Should validate Puts in RowMutations Key: HBASE-25575 URL: https://issues.apache.org/jira/browse/HBASE-25575 Project: HBase Issue Type: Bug Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Currently, we don't validate Puts in RowMutations. We should do that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25574) Revisit increment/append related RegionObserver methods
Toshihiro Suzuki created HBASE-25574: Summary: Revisit increment/append related RegionObserver methods Key: HBASE-25574 URL: https://issues.apache.org/jira/browse/HBASE-25574 Project: HBase Issue Type: Improvement Components: Coprocessors Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Fix For: 3.0.0-alpha-1, 2.4.2 After HBASE-24602, increment/append operations are performed in HRegion.batchMutate(). Accordingly, we should make some changes for the increment/append related RegionObserver methods. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25258) Backport HBASE-24776 "[hbtop] Support Batch mode" to branch-1
Toshihiro Suzuki created HBASE-25258: Summary: Backport HBASE-24776 "[hbtop] Support Batch mode" to branch-1 Key: HBASE-25258 URL: https://issues.apache.org/jira/browse/HBASE-25258 Project: HBase Issue Type: Sub-task Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Backport parent issue to branch-1. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25242) Add Increment/Append support to RowMutations
Toshihiro Suzuki created HBASE-25242: Summary: Add Increment/Append support to RowMutations Key: HBASE-25242 URL: https://issues.apache.org/jira/browse/HBASE-25242 Project: HBase Issue Type: New Feature Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Fix For: 3.0.0-alpha-1, 2.4.0 Currently, RowMutations supports only Put and Delete. Supporting Increment/Append in RowMutations would be helpful for some use cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24210) Add Increment, Append and CheckAndMutate support to RowMutations
[ https://issues.apache.org/jira/browse/HBASE-24210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-24210. -- Resolution: Won't Fix > Add Increment, Append and CheckAndMutate support to RowMutations > > > Key: HBASE-24210 > URL: https://issues.apache.org/jira/browse/HBASE-24210 > Project: HBase > Issue Type: New Feature >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1, 2.4.0 > > > Currently, RowMutations supports only Put and Delete. Supporting Increment, > Append and CheckAndMutate in RowMutations would be helpful for some use cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24996) Support CheckAndMutate in Region.batchMutate()
[ https://issues.apache.org/jira/browse/HBASE-24996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-24996. -- Resolution: Won't Fix > Support CheckAndMutate in Region.batchMutate() > -- > > Key: HBASE-24996 > URL: https://issues.apache.org/jira/browse/HBASE-24996 > Project: HBase > Issue Type: Sub-task >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1, 2.4.0 > > > After HBASE-24602, Region.batchMutate() supports Put/Delete/Increment/Append > operations, but it doesn't support CheckAndMutate. If we support > CheckAndMutate Region.batchMutate(), we can perform > Put/Delete/Increment/Append/CheckAndMutate operations atomically, which is > very useful for some cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25206) Data loss can happen if a cloned table loses original split region(delete table)
Toshihiro Suzuki created HBASE-25206:
Summary: Data loss can happen if a cloned table loses original
split region(delete table)
Key: HBASE-25206
URL: https://issues.apache.org/jira/browse/HBASE-25206
Project: HBase
Issue Type: Bug
Reporter: Toshihiro Suzuki
Assignee: Toshihiro Suzuki
Steps to reproduce are as follows:
1. Create a table and put some data into the table:
{code:java}
create 'test1','cf'
put 'test1','r1','cf','v1'
put 'test1','r2','cf','v2'
put 'test1','r3','cf','v3'
put 'test1','r4','cf','v4'
put 'test1','r5','cf','v5'
{code}
2. Take a snapshot for the table:
{code:java}
snapshot 'test1','snap_test'
{code}
3. Clone the snapshot to another table
{code:java}
clone_snapshot 'snap_test','test2'
{code}
4. Delete the snapshot
{code:java}
delete_snapshot 'snap_test'
{code}
5. Split the original table
{code:java}
split 'test1','r3'
{code}
6. Drop the original table
{code:java}
disable 'test1'
drop 'test1'
{code}
After that, we see the error like the following in RS log when opening the
regions of the cloned table:
{code:java}
2020-10-20 22:15:47,554 WARN [RS_OPEN_REGION-regionserver/10.0.1.8:0-0]
regionserver.HRegion(965): Failed initialize of region=
testCloneSnapshotBeforeSplittingRegionAndDroppingTable_0__regionReplication_1_-1603199739880,,1603199732706.92f431fab12aaded92a23513901daa5a.,
starting to roll back memstore
java.io.IOException: java.io.IOException: java.io.FileNotFoundException:
HFileLink
locations=[hdfs://localhost:62716/user/tsuzuki/test-data/c00e6c6b-1c3b-5e40-4227-831ae42cf2f4/data/default/testCloneSnapshotBeforeSplittingRegionAndDroppingTable_0__regionReplication_1_1603199732705/f4658c2b6fb129d95f62e63d3742177d/cf/719b64120a0f4394ae7af8926bc56402,
hdfs://localhost:62716/user/tsuzuki/test-data/c00e6c6b-1c3b-5e40-4227-831ae42cf2f4/.tmp/data/default/testCloneSnapshotBeforeSplittingRegionAndDroppingTable_0__regionReplication_1_1603199732705/f4658c2b6fb129d95f62e63d3742177d/cf/719b64120a0f4394ae7af8926bc56402,
hdfs://localhost:62716/user/tsuzuki/test-data/c00e6c6b-1c3b-5e40-4227-831ae42cf2f4/mobdir/data/default/testCloneSnapshotBeforeSplittingRegionAndDroppingTable_0__regionReplication_1_1603199732705/f4658c2b6fb129d95f62e63d3742177d/cf/719b64120a0f4394ae7af8926bc56402,
hdfs://localhost:62716/user/tsuzuki/test-data/c00e6c6b-1c3b-5e40-4227-831ae42cf2f4/archive/data/default/testCloneSnapshotBeforeSplittingRegionAndDroppingTable_0__regionReplication_1_1603199732705/f4658c2b6fb129d95f62e63d3742177d/cf/719b64120a0f4394ae7af8926bc56402]
at
org.apache.hadoop.hbase.regionserver.HRegion.initializeStores(HRegion.java:1179)
at
org.apache.hadoop.hbase.regionserver.HRegion.initializeStores(HRegion.java:1121)
at
org.apache.hadoop.hbase.regionserver.HRegion.initializeRegionInternals(HRegion.java:1011)
at
org.apache.hadoop.hbase.regionserver.HRegion.initialize(HRegion.java:962)
at
org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:7999)
at
org.apache.hadoop.hbase.regionserver.HRegion.openHRegionFromTableDir(HRegion.java:7955)
at
org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:7930)
at
org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:7888)
at
org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:7839)
at
org.apache.hadoop.hbase.regionserver.handler.AssignRegionHandler.process(AssignRegionHandler.java:132)
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: java.io.FileNotFoundException: HFileLink
locations=[hdfs://localhost:62716/user/tsuzuki/test-data/c00e6c6b-1c3b-5e40-4227-831ae42cf2f4/data/default/testCloneSnapshotBeforeSplittingRegionAndDroppingTable_0__regionReplication_1_1603199732705/f4658c2b6fb129d95f62e63d3742177d/cf/719b64120a0f4394ae7af8926bc56402,
hdfs://localhost:62716/user/tsuzuki/test-data/c00e6c6b-1c3b-5e40-4227-831ae42cf2f4/.tmp/data/default/testCloneSnapshotBeforeSplittingRegionAndDroppingTable_0__regionReplication_1_1603199732705/f4658c2b6fb129d95f62e63d3742177d/cf/719b64120a0f4394ae7af8926bc56402,
hdfs://localhost:62716/user/tsuzuki/test-data/c00e6c6b-1c3b-5e40-4227-831ae42cf2f4/mobdir/data/default/testCloneSnapshotBeforeSplittingRegionAndDroppingTable_0__regionReplication_1_1603199732705/f4658c2b6fb129d95f62e63d3742177d/cf/719b64120a0f4394ae7af8926bc56402,
[jira] [Resolved] (HBASE-25160) Refactor AccessController and VisibilityController
[ https://issues.apache.org/jira/browse/HBASE-25160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-25160. -- Hadoop Flags: Reviewed Resolution: Fixed > Refactor AccessController and VisibilityController > -- > > Key: HBASE-25160 > URL: https://issues.apache.org/jira/browse/HBASE-25160 > Project: HBase > Issue Type: Improvement >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1, 2.4.0 > > > After HBASE-24602, the batchMutate() related coprocessor methods of > RegionObserver are called when increment/append operations are performed. We > can refactor AccessController and VisibilityController to make use of that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25160) Refactor AccessController and VisibilityController
Toshihiro Suzuki created HBASE-25160: Summary: Refactor AccessController and VisibilityController Key: HBASE-25160 URL: https://issues.apache.org/jira/browse/HBASE-25160 Project: HBase Issue Type: Improvement Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Fix For: 3.0.0-alpha-1, 2.4.0 After HBASE-24602, the batchMutate() related coprocessor methods of RegionObserver are called when increment/append operations are performed. We can refactor AccessController and VisibilityController to make use of that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25096) WAL size in RegionServer UI is wrong
[
https://issues.apache.org/jira/browse/HBASE-25096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toshihiro Suzuki resolved HBASE-25096.
--
Hadoop Flags: Reviewed
Resolution: Fixed
> WAL size in RegionServer UI is wrong
>
>
> Key: HBASE-25096
> URL: https://issues.apache.org/jira/browse/HBASE-25096
> Project: HBase
> Issue Type: Bug
>Reporter: Toshihiro Suzuki
>Assignee: Toshihiro Suzuki
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.3, 1.7.0, 2.4.0, 2.2.7
>
>
> In MetricsRegionServerWrapperImpl, *walFileSize* is calculated by
> *provider.getLogFileSize()* twice as follows, which is causing the wrong WAL
> size in RegionServer UI:
> {code:java}
> walFileSize = (provider == null ? 0 : provider.getLogFileSize()) +
> (provider == null ? 0 : provider.getLogFileSize());
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-25096) WAL size in RegionServer UI is wrong
Toshihiro Suzuki created HBASE-25096:
Summary: WAL size in RegionServer UI is wrong
Key: HBASE-25096
URL: https://issues.apache.org/jira/browse/HBASE-25096
Project: HBase
Issue Type: Bug
Reporter: Toshihiro Suzuki
Assignee: Toshihiro Suzuki
In MetricsRegionServerWrapperImpl, *walFileSize* is calculated by
*provider.getLogFileSize()* twice as follows, which is causing the wrong WAL
size in RegionServer UI:
{code:java}
walFileSize = (provider == null ? 0 : provider.getLogFileSize()) +
(provider == null ? 0 : provider.getLogFileSize());
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-25008) Add document for "HBASE-24776 [hbtop] Support Batch mode"
[ https://issues.apache.org/jira/browse/HBASE-25008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-25008. -- Fix Version/s: 3.0.0-alpha-1 Hadoop Flags: Reviewed Resolution: Fixed > Add document for "HBASE-24776 [hbtop] Support Batch mode" > - > > Key: HBASE-25008 > URL: https://issues.apache.org/jira/browse/HBASE-25008 > Project: HBase > Issue Type: Sub-task > Components: documentation, hbtop >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1 > > > Add a document for the batch mode of hbtop introduced in HBASE-24776 to the > ref guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23643) Add document for "HBASE-23065 [hbtop] Top-N heavy hitter user and client drill downs"
[ https://issues.apache.org/jira/browse/HBASE-23643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-23643. -- Fix Version/s: 3.0.0-alpha-1 Hadoop Flags: Reviewed Resolution: Fixed > Add document for "HBASE-23065 [hbtop] Top-N heavy hitter user and client > drill downs" > - > > Key: HBASE-23643 > URL: https://issues.apache.org/jira/browse/HBASE-23643 > Project: HBase > Issue Type: Sub-task > Components: documentation, hbtop >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1 > > > Add the new feature of hbtop in HBASE-23065 to the ref guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24776) [hbtop] Support Batch mode
[ https://issues.apache.org/jira/browse/HBASE-24776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-24776. -- Hadoop Flags: Reviewed Resolution: Fixed > [hbtop] Support Batch mode > -- > > Key: HBASE-24776 > URL: https://issues.apache.org/jira/browse/HBASE-24776 > Project: HBase > Issue Type: New Feature > Components: hbtop >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1, 2.4.0, 2.2.7, 2.3.2 > > > Similar to Unix's 'top' command, we can support Batch mode that allows us to > send hbtop command output to other programs or to a file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-25008) Add document for "HBASE-24776 [hbtop] Support Batch mode"
Toshihiro Suzuki created HBASE-25008: Summary: Add document for "HBASE-24776 [hbtop] Support Batch mode" Key: HBASE-25008 URL: https://issues.apache.org/jira/browse/HBASE-25008 Project: HBase Issue Type: Sub-task Components: documentation, hbtop Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Add a document for the batch mode of hbtop introduced in HBASE-24776 to the ref guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24602) Add Increment and Append support to CheckAndMutate
[ https://issues.apache.org/jira/browse/HBASE-24602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-24602. -- Resolution: Fixed > Add Increment and Append support to CheckAndMutate > -- > > Key: HBASE-24602 > URL: https://issues.apache.org/jira/browse/HBASE-24602 > Project: HBase > Issue Type: New Feature >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1, 2.4.0 > > > Currently, CheckAndMutate supports only Put and Delete. Supporting Increment > and Append would be helpful for some use cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24996) Support CheckAndMutate in Region.batchMutate()
Toshihiro Suzuki created HBASE-24996: Summary: Support CheckAndMutate in Region.batchMutate() Key: HBASE-24996 URL: https://issues.apache.org/jira/browse/HBASE-24996 Project: HBase Issue Type: Sub-task Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Currently, Region.batchMutate() supports Put/Delete/Increment/Append operations, but it doesn't support CheckAndMutate. If we support CheckAndMutate Region.batchMutate(), we can perform Put/Delete/Increment/Append/CheckAndMutate operations atomically in a row, which is very useful for some cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24884) BulkLoadHFilesTool/LoadIncrementalHFiles should accept -D options from command line parameters
[ https://issues.apache.org/jira/browse/HBASE-24884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-24884. -- Hadoop Flags: Reviewed Resolution: Fixed > BulkLoadHFilesTool/LoadIncrementalHFiles should accept -D options from > command line parameters > -- > > Key: HBASE-24884 > URL: https://issues.apache.org/jira/browse/HBASE-24884 > Project: HBase > Issue Type: Bug >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Minor > Fix For: 3.0.0-alpha-1, 2.4.0, 2.2.7, 2.3.2 > > > Currently, BulkLoadHFilesTool/LoadIncrementalHFiles doesn't accept -D options > from command line parameters. It should support them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24884) BulkLoadHFilesTool/LoadIncrementalHFiles should accept -D options from command line parameters
Toshihiro Suzuki created HBASE-24884: Summary: BulkLoadHFilesTool/LoadIncrementalHFiles should accept -D options from command line parameters Key: HBASE-24884 URL: https://issues.apache.org/jira/browse/HBASE-24884 Project: HBase Issue Type: Bug Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Currently, BulkLoadHFilesTool/LoadIncrementalHFiles doesn't accept -D options from command line parameters. It should support them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24680) Refactor the checkAndMutate code on the server side
[ https://issues.apache.org/jira/browse/HBASE-24680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-24680. -- Hadoop Flags: Reviewed Resolution: Fixed > Refactor the checkAndMutate code on the server side > --- > > Key: HBASE-24680 > URL: https://issues.apache.org/jira/browse/HBASE-24680 > Project: HBase > Issue Type: Sub-task >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1, 2.4.0 > > > Refactor the checkAndMutate code on the server side by using the > CheckAndMutate class (introduced in HBASE-8458) and the CheckAndMutateResult > class (introduced in HBASE-24650). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24830) Some tests involving RS crash fail with NullPointerException after HBASE-24632 in branch-2
Toshihiro Suzuki created HBASE-24830:
Summary: Some tests involving RS crash fail with
NullPointerException after HBASE-24632 in branch-2
Key: HBASE-24830
URL: https://issues.apache.org/jira/browse/HBASE-24830
Project: HBase
Issue Type: Bug
Reporter: Toshihiro Suzuki
In some tests involving RS crash in branch-2, the following
NullPointerException is happening repeatedly and the tests finally fail due to
timeout:
{code:java}
2020-08-06 16:03:43,101 ERROR [RS_LOG_REPLAY_OPS-regionserver/10.0.1.11:0-1]
handler.RSProcedureHandler(51): pid=17
java.lang.NullPointerException
at
org.apache.hadoop.hbase.regionserver.SplitLogWorker.splitLog(SplitLogWorker.java:107)
at
org.apache.hadoop.hbase.regionserver.SplitWALCallable.call(SplitWALCallable.java:100)
at
org.apache.hadoop.hbase.regionserver.SplitWALCallable.call(SplitWALCallable.java:45)
at
org.apache.hadoop.hbase.regionserver.handler.RSProcedureHandler.process(RSProcedureHandler.java:49)
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-24775) [hbtop] StoreFile size should be rounded off
[ https://issues.apache.org/jira/browse/HBASE-24775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-24775. -- Hadoop Flags: Reviewed Resolution: Fixed > [hbtop] StoreFile size should be rounded off > > > Key: HBASE-24775 > URL: https://issues.apache.org/jira/browse/HBASE-24775 > Project: HBase > Issue Type: Bug > Components: hbtop >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Minor > Fix For: 3.0.0-alpha-1, 2.3.1, 1.7.0, 2.2.7 > > Attachments: Screen Shot.png, Screen Shot2.png > > > Currently, hbtop doesn't show StoreFile size rounded off, so when it's > reached 1GB it will be very ugly as follows: > !Screen Shot.png! > We should round off StoreFile size. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24776) [hbtop] Support Batch mode
Toshihiro Suzuki created HBASE-24776: Summary: [hbtop] Support Batch mode Key: HBASE-24776 URL: https://issues.apache.org/jira/browse/HBASE-24776 Project: HBase Issue Type: Bug Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Similar to Unix's 'top' command, we can support Batch mode that allows us to send top command output to other programs or to a file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24775) [hbtop] StoreFile size should be rounded off
Toshihiro Suzuki created HBASE-24775: Summary: [hbtop] StoreFile size should be rounded off Key: HBASE-24775 URL: https://issues.apache.org/jira/browse/HBASE-24775 Project: HBase Issue Type: Bug Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Attachments: Screen Shot.png Currently, hbtop doesn't show StoreFile size rounded off, so when it's reached 1GB it will be very ugly as follows: !Screen Shot.png! We should round off StoreFile size. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24650) Change the return types of the new checkAndMutate methods introduced in HBASE-8458
[
https://issues.apache.org/jira/browse/HBASE-24650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toshihiro Suzuki resolved HBASE-24650.
--
Hadoop Flags: Incompatible change,Reviewed
Release Note:
This changed the return type of checkAndMutate methods to support
CheckAndMutate with Increment/Append.
The new APIs for the Table interface:
{code}
/**
* checkAndMutate that atomically checks if a row matches the specified
condition. If it does,
* it performs the specified action.
*
* @param checkAndMutate The CheckAndMutate object.
* @return A CheckAndMutateResult object that represents the result for the
CheckAndMutate.
* @throws IOException if a remote or network exception occurs.
*/
default CheckAndMutateResult checkAndMutate(CheckAndMutate checkAndMutate)
throws IOException {
return checkAndMutate(Collections.singletonList(checkAndMutate)).get(0);
}
/**
* Batch version of checkAndMutate. The specified CheckAndMutates are batched
only in the sense
* that they are sent to a RS in one RPC, but each CheckAndMutate operation is
still executed
* atomically (and thus, each may fail independently of others).
*
* @param checkAndMutates The list of CheckAndMutate.
* @return A list of CheckAndMutateResult objects that represents the result
for each
* CheckAndMutate.
* @throws IOException if a remote or network exception occurs.
*/
default List checkAndMutate(List
checkAndMutates)
throws IOException {
throw new NotImplementedException("Add an implementation!");
}
{code}
The new APIs for the AsyncTable interface:
{code}
/**
* checkAndMutate that atomically checks if a row matches the specified
condition. If it does,
* it performs the specified action.
*
* @param checkAndMutate The CheckAndMutate object.
* @return A {@link CompletableFuture}s that represent the result for the
CheckAndMutate.
*/
CompletableFuture checkAndMutate(CheckAndMutate
checkAndMutate);
/**
* Batch version of checkAndMutate. The specified CheckAndMutates are batched
only in the sense
* that they are sent to a RS in one RPC, but each CheckAndMutate operation is
still executed
* atomically (and thus, each may fail independently of others).
*
* @param checkAndMutates The list of CheckAndMutate.
* @return A list of {@link CompletableFuture}s that represent the result for
each
* CheckAndMutate.
*/
List> checkAndMutate(
List checkAndMutates);
/**
* A simple version of batch checkAndMutate. It will fail if there are any
failures.
*
* @param checkAndMutates The list of rows to apply.
* @return A {@link CompletableFuture} that wrapper the result list.
*/
default CompletableFuture> checkAndMutateAll(
List checkAndMutates) {
return allOf(checkAndMutate(checkAndMutates));
}
{code}
Resolution: Fixed
> Change the return types of the new checkAndMutate methods introduced in
> HBASE-8458
> --
>
> Key: HBASE-24650
> URL: https://issues.apache.org/jira/browse/HBASE-24650
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Reporter: Toshihiro Suzuki
>Assignee: Toshihiro Suzuki
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> To support CheckAndMutate with Increment/Append, the new checkAndMutate
> methods introduced in HBASE-8458 need to return the result of the specified
> Increment/Append operation in addition to a boolean value represents whether
> it's successful or not. Currently, the methods return only boolean value(s),
> so we need to change the return types of the methods. The methods are
> unreleased yet currently, so I think it's no problem to change the return
> types of the methods.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24680) Refactor the checkAndMutate code on the server side
Toshihiro Suzuki created HBASE-24680: Summary: Refactor the checkAndMutate code on the server side Key: HBASE-24680 URL: https://issues.apache.org/jira/browse/HBASE-24680 Project: HBase Issue Type: Sub-task Reporter: Toshihiro Suzuki Refactor the checkAndMutate code on the server side by using the CheckAndMutate class (introduced in HBASE-8458) and the CheckAndMutateResult class (introduced in HBASE-24650). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24650) Change the return types of the new CheckAndMutate methods introduced in HBASE-8458
Toshihiro Suzuki created HBASE-24650: Summary: Change the return types of the new CheckAndMutate methods introduced in HBASE-8458 Key: HBASE-24650 URL: https://issues.apache.org/jira/browse/HBASE-24650 Project: HBase Issue Type: Sub-task Components: Client Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Fix For: 3.0.0-alpha-1, 2.4.0 To support CheckAndMutate with Increment/Append, the new CheckAndMutate methods introduced in HBASE-8458 need to return the result of the specified Increment/Append operation in addition to a boolean value represents whether it's successful or not. Currently, the methods return only boolean value(s), so we need to change the return types of the methods. The methods are unreleased yet currently, so I think it's no problem to change the return types of the methods. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24600) Empty RegionAction added to MultiRequest in case of RowMutations/CheckAndMutate batch
[ https://issues.apache.org/jira/browse/HBASE-24600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-24600. -- Fix Version/s: 2.2.6 2.1.10 2.4.0 2.3.1 3.0.0-alpha-1 Hadoop Flags: Reviewed Resolution: Fixed Pushed to master, branch-2, branch-2.3, branch-2.2 and branch-2.1. Thank you for reviewing this [~zghao]! > Empty RegionAction added to MultiRequest in case of > RowMutations/CheckAndMutate batch > - > > Key: HBASE-24600 > URL: https://issues.apache.org/jira/browse/HBASE-24600 > Project: HBase > Issue Type: Bug >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1, 2.3.1, 2.4.0, 2.1.10, 2.2.6 > > > When a client sends RowMutations/CheckAndMutate batch requests, no Action > objects are added to the *builder* (RegionAction.Builder), so empty > RegionAction is added to MultiRequest at the following line: > https://github.com/apache/hbase/blob/3c319811799cb4c1f51fb5b43dd4743acd28052c/hbase-client/src/main/java/org/apache/hadoop/hbase/shaded/protobuf/RequestConverter.java#L593 > We need to check if the *builder* has any Action objects or not here. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24602) Add Increment and Append support to CheckAndMutate
Toshihiro Suzuki created HBASE-24602: Summary: Add Increment and Append support to CheckAndMutate Key: HBASE-24602 URL: https://issues.apache.org/jira/browse/HBASE-24602 Project: HBase Issue Type: New Feature Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Currently, CheckAndMutate supports only Put, Delete and RowMutations. Supporting Increment and Append would be helpful for some use cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24600) Empty RegionAction added to MultiRequest in case of RowMutations/CheckAndMutate batch
Toshihiro Suzuki created HBASE-24600: Summary: Empty RegionAction added to MultiRequest in case of RowMutations/CheckAndMutate batch Key: HBASE-24600 URL: https://issues.apache.org/jira/browse/HBASE-24600 Project: HBase Issue Type: Bug Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki When a client sends RowMutations/CheckAndMutate batch requests, no Action objects are added to the *builder* (RegionAction.Builder), so empty RegionAction is added to MultiRequest at the following line: https://github.com/apache/hbase/blob/3c319811799cb4c1f51fb5b43dd4743acd28052c/hbase-client/src/main/java/org/apache/hadoop/hbase/shaded/protobuf/RequestConverter.java#L593 We need to check if the *builder* has any Action objects or not here. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-8458) Support for batch version of checkAndMutate()
[ https://issues.apache.org/jira/browse/HBASE-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-8458. - Resolution: Fixed > Support for batch version of checkAndMutate() > - > > Key: HBASE-8458 > URL: https://issues.apache.org/jira/browse/HBASE-8458 > Project: HBase > Issue Type: New Feature > Components: Client, regionserver >Reporter: Hari Mankude >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1, 2.4.0 > > > The use case is that the user has multiple threads loading hundreds of keys > into a hbase table. Occasionally there are collisions in the keys being > uploaded by different threads. So for correctness, it is required to do > checkAndMutate() instead of a put(). However, doing a checkAndMutate() rpc > for every key update is non optimal. It would be good to have a batch version > of checkAndMutate() similar to batch put(). The client can partition the keys > on region boundaries. > The jira is NOT looking for any type of cross-row locking or multi-row > atomicity with checkAndMutate(). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24529) hbase.rs.evictblocksonclose is not honored when removing compacted files and closing the storefiles
[ https://issues.apache.org/jira/browse/HBASE-24529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-24529. -- Hadoop Flags: Reviewed Resolution: Fixed > hbase.rs.evictblocksonclose is not honored when removing compacted files and > closing the storefiles > --- > > Key: HBASE-24529 > URL: https://issues.apache.org/jira/browse/HBASE-24529 > Project: HBase > Issue Type: Bug >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0-alpha-1, 2.3.0, 2.4.0, 2.1.10, 2.2.6 > > > Currently, when removing compacted files and closing the storefiles, RS > always does evict block caches for the store files. It should honor > hbase.rs.evictblocksonclose: > https://github.com/apache/hbase/blob/7b396e9b8ca93361de6a6c4bc8a40442db77c4da/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HStore.java#L2744 > https://github.com/apache/hbase/blob/7b396e9b8ca93361de6a6c4bc8a40442db77c4da/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HStore.java#L625 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24529) hbase.rs.evictblocksonclose is not honored when removing compacted files and closing the storefiles
Toshihiro Suzuki created HBASE-24529: Summary: hbase.rs.evictblocksonclose is not honored when removing compacted files and closing the storefiles Key: HBASE-24529 URL: https://issues.apache.org/jira/browse/HBASE-24529 Project: HBase Issue Type: Bug Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Currently, when removing compacted files and closing the storefiles, RS always does evict block caches for the store files. It should honor hbase.rs.evictblocksonclose: https://github.com/apache/hbase/blob/7b396e9b8ca93361de6a6c4bc8a40442db77c4da/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HStore.java#L2744 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24515) batch Increment/Append fails when retrying the RPC
[
https://issues.apache.org/jira/browse/HBASE-24515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toshihiro Suzuki resolved HBASE-24515.
--
Hadoop Flags: Reviewed
Resolution: Fixed
> batch Increment/Append fails when retrying the RPC
> --
>
> Key: HBASE-24515
> URL: https://issues.apache.org/jira/browse/HBASE-24515
> Project: HBase
> Issue Type: Bug
>Reporter: Toshihiro Suzuki
>Assignee: Toshihiro Suzuki
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.4.0, 2.1.10, 2.2.6
>
>
> When a client hits RPC timeout and sends a second RPC request for batch
> Increment/Append but the first RPC is already processed actually, the nonce
> of the RPC is saved in the RS.
> In this case, for the second RPC, the RS just reads the previous result and
> returns it to the client to avoid the Increment/Append is processed twice.
> At that time, for batch Increment/Append, we try to create a Get object from
> a CellScanner object in the following code:
>
> [https://github.com/apache/hbase/blob/66452afc09d8b82927e5e58565f97939faa22c7b/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java#L773-L776]
> However, the CellScanner object is already consumed to create the
> Increment/Append object in the following code, and it fails with the
> following exception:
>
> [https://github.com/apache/hbase/blob/66452afc09d8b82927e5e58565f97939faa22c7b/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java#L757]
> {code:java}
> 2020-06-06 14:09:06,153 WARN [hconnection-0x79c3903e-shared-pool3-t209]
> client.AsyncRequestFutureImpl: id=1, table=REF_Test, attempt=3/36,
> failureCount=1ops, last
> exception=org.apache.hadoop.hbase.DoNotRetryIOException:
> org.apache.hadoop.hbase.DoNotRetryIOException: Cell count of 1 but at index 0
> no cell returned: row: "xxx" mutate_type: INCREMENT timestamp:
> 9223372036854775807 durability: USE_DEFAULT time_range { from: 0 to:
> 9223372036854775807 } associated_cell_count: 1 nonce: 5281583076322914765
> at
> org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.toGet(ProtobufUtil.java:934)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.increment(RSRpcServices.java:737)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.doNonAtomicRegionMutation(RSRpcServices.java:877)
> at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.multi(RSRpcServices.java:2702)
> at
> org.apache.hadoop.hbase.shaded.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:42202)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:413)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:132)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:324)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:304)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24515) batch Increment/Append fails when retrying the RPC
Toshihiro Suzuki created HBASE-24515: Summary: batch Increment/Append fails when retrying the RPC Key: HBASE-24515 URL: https://issues.apache.org/jira/browse/HBASE-24515 Project: HBase Issue Type: Bug Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki When a client hits RPC timeout and sends a second RPC request for batch Increment/Append but the first RPC is already processed actually, the nonce of the RPC is saved in the RS. In this case, for the second RPC, the RS just reads the previous result and returns it to the client to avoid the Increment/Append is processed twice. At that time, for batch Increment/Append, we try to create a Get object from a CellScanner object in the following code: [https://github.com/apache/hbase/blob/66452afc09d8b82927e5e58565f97939faa22c7b/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java#L773-L776] However, the CellScanner object is already consumed to create the Increment/Append object as follows, and it fails: [https://github.com/apache/hbase/blob/66452afc09d8b82927e5e58565f97939faa22c7b/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java#L757] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24210) Add Increment, Append and CheckAndMutate support to RowMutations
Toshihiro Suzuki created HBASE-24210: Summary: Add Increment, Append and CheckAndMutate support to RowMutations Key: HBASE-24210 URL: https://issues.apache.org/jira/browse/HBASE-24210 Project: HBase Issue Type: New Feature Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Currently, RowMutations supports only Put and Delete. Supporting Increment, Append and CheckAndMutate in RowMutations would be helpful for some use cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24030) Add necessary validations to HRegion.checkAndMutate() and HRegion.checkAndRowMutate()
[ https://issues.apache.org/jira/browse/HBASE-24030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-24030. -- Hadoop Flags: Reviewed Resolution: Fixed > Add necessary validations to HRegion.checkAndMutate() and > HRegion.checkAndRowMutate() > - > > Key: HBASE-24030 > URL: https://issues.apache.org/jira/browse/HBASE-24030 > Project: HBase > Issue Type: Bug >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > Need to check that the following are fulfilled: > # The mutation type should be Put or Delete in HRegion.checkAndMutate(). > # The specified row should match the row of the Put/Delete/RowMutations in > HRegion.checkAndMutate() and HRegion.checkAndRowMutate(). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24031) TestHRegion.testCheckAndMutate_WithFilters is flaky
[
https://issues.apache.org/jira/browse/HBASE-24031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toshihiro Suzuki resolved HBASE-24031.
--
Resolution: Fixed
> TestHRegion.testCheckAndMutate_WithFilters is flaky
> ---
>
> Key: HBASE-24031
> URL: https://issues.apache.org/jira/browse/HBASE-24031
> Project: HBase
> Issue Type: Bug
>Reporter: Toshihiro Suzuki
>Assignee: Toshihiro Suzuki
>Priority: Minor
> Fix For: 3.0.0
>
>
> {code}
> [ERROR] Tests run: 108, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 119.165 s <<< FAILURE! - in org.apache.hadoop.hbase.regionserver.TestHRegion
> [ERROR]
> org.apache.hadoop.hbase.regionserver.TestHRegion.testCheckAndMutate_WithFilters
> Time elapsed: 0.179 s <<< FAILURE!
> java.lang.AssertionError: expected: but was:
> at
> org.apache.hadoop.hbase.regionserver.TestHRegion.testCheckAndMutate_WithFilters(TestHRegion.java:2218)
> {code}
> This happens only in the master branch.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24031) TestHRegion.testCheckAndMutate_WithFilters is flaky
Toshihiro Suzuki created HBASE-24031:
Summary: TestHRegion.testCheckAndMutate_WithFilters is flaky
Key: HBASE-24031
URL: https://issues.apache.org/jira/browse/HBASE-24031
Project: HBase
Issue Type: Bug
Reporter: Toshihiro Suzuki
Assignee: Toshihiro Suzuki
Fix For: 3.0.0
{code}
[ERROR] Tests run: 108, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
119.165 s <<< FAILURE! - in org.apache.hadoop.hbase.regionserver.TestHRegion
[ERROR]
org.apache.hadoop.hbase.regionserver.TestHRegion.testCheckAndMutate_WithFilters
Time elapsed: 0.179 s <<< FAILURE!
java.lang.AssertionError: expected: but was:
at
org.apache.hadoop.hbase.regionserver.TestHRegion.testCheckAndMutate_WithFilters(TestHRegion.java:2218)
{code}
This happens only in the master branch.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24030) Add necessary validations to HRegion.checkAndMutate() and HRegion.checkAndRowMutate()
Toshihiro Suzuki created HBASE-24030: Summary: Add necessary validations to HRegion.checkAndMutate() and HRegion.checkAndRowMutate() Key: HBASE-24030 URL: https://issues.apache.org/jira/browse/HBASE-24030 Project: HBase Issue Type: Bug Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Fix For: 3.0.0, 2.3.0 Need to check that the following are fulfilled in HRegion.checkAndMutate() and HRegion.checkAndRowMutate(): # The mutation type should be Put or Delete. # The specified row should match the row of the Put/Delete/RowMutations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23925) Implement the checkAndMutate(row, filter) method of ThriftTable for Thrift
Toshihiro Suzuki created HBASE-23925: Summary: Implement the checkAndMutate(row, filter) method of ThriftTable for Thrift Key: HBASE-23925 URL: https://issues.apache.org/jira/browse/HBASE-23925 Project: HBase Issue Type: Sub-task Reporter: Toshihiro Suzuki -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23924) Implement the checkAndMutate(row, filter) method of RemoteHTable for Rest
Toshihiro Suzuki created HBASE-23924: Summary: Implement the checkAndMutate(row, filter) method of RemoteHTable for Rest Key: HBASE-23924 URL: https://issues.apache.org/jira/browse/HBASE-23924 Project: HBase Issue Type: Sub-task Reporter: Toshihiro Suzuki -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23146) Support CheckAndMutate with multiple conditions
[
https://issues.apache.org/jira/browse/HBASE-23146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toshihiro Suzuki resolved HBASE-23146.
--
Release Note:
Add a checkAndMutate(row, filter) method in the AsyncTable interface and the
Table interface.
This method atomically checks if the row matches the specified filter. If it
does, it adds the Put/Delete/RowMutations.
This is a fluent style API, the code is like:
For Table interface:
{code}
table.checkAndMutate(row, filter).thenPut(put);
{code}
For AsyncTable interface:
{code}
table.checkAndMutate(row, filter).thenPut(put)
.thenAccept(succ -> {
if (succ) {
System.out.println("Check and put succeeded");
} else {
System.out.println("Check and put failed");
}
});
{code}
Assignee: Toshihiro Suzuki
Resolution: Fixed
> Support CheckAndMutate with multiple conditions
> ---
>
> Key: HBASE-23146
> URL: https://issues.apache.org/jira/browse/HBASE-23146
> Project: HBase
> Issue Type: New Feature
>Reporter: Toshihiro Suzuki
>Assignee: Toshihiro Suzuki
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> Currently, checkAndMutate supports only single condition. Supporting
> checkAndMutate with multi conditions is useful for some use cases.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-23817) The message "Please make sure that backup is enabled on the cluster." is shown even when the backup feature is enabled
Toshihiro Suzuki created HBASE-23817:
Summary: The message "Please make sure that backup is enabled on
the cluster." is shown even when the backup feature is enabled
Key: HBASE-23817
URL: https://issues.apache.org/jira/browse/HBASE-23817
Project: HBase
Issue Type: Bug
Reporter: Toshihiro Suzuki
The following message is shown even when the backup feature is enabled, which
is confusing:
{code}
Please make sure that backup is enabled on the cluster. To enable backup, in
hbase-site.xml, set:
hbase.backup.enable=true
hbase.master.logcleaner.plugins=YOUR_PLUGINS,org.apache.hadoop.hbase.backup.master.BackupLogCleaner
hbase.procedure.master.classes=YOUR_CLASSES,org.apache.hadoop.hbase.backup.master.LogRollMasterProcedureManager
hbase.procedure.regionserver.classes=YOUR_CLASSES,org.apache.hadoop.hbase.backup.regionserver.LogRollRegionServerProcedureManager
hbase.coprocessor.region.classes=YOUR_CLASSES,org.apache.hadoop.hbase.backup.BackupObserver
and restart the cluster
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-23165) [hbtop] Some modifications from HBASE-22988
[ https://issues.apache.org/jira/browse/HBASE-23165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-23165. -- Resolution: Fixed > [hbtop] Some modifications from HBASE-22988 > --- > > Key: HBASE-23165 > URL: https://issues.apache.org/jira/browse/HBASE-23165 > Project: HBase > Issue Type: Improvement >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Minor > Fix For: 3.0.0, 2.3.0, 2.2.3, 2.1.9 > > > Some modifications happened in the review of HBASE-22988. We can forward port > them to the master branch. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23643) Add document for "HBASE-23065 [hbtop] Top-N heavy hitter user and client drill downs"
Toshihiro Suzuki created HBASE-23643: Summary: Add document for "HBASE-23065 [hbtop] Top-N heavy hitter user and client drill downs" Key: HBASE-23643 URL: https://issues.apache.org/jira/browse/HBASE-23643 Project: HBase Issue Type: Sub-task Components: documentation Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Add the new feature of hbtop in HBASE-23065 to the ref guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23581) Creating table gets stuck when specifying an invalid split policy as METADATA
Toshihiro Suzuki created HBASE-23581:
Summary: Creating table gets stuck when specifying an invalid
split policy as METADATA
Key: HBASE-23581
URL: https://issues.apache.org/jira/browse/HBASE-23581
Project: HBase
Issue Type: Bug
Environment: HDP-3.1.0
Reporter: Toshihiro Suzuki
Assignee: Toshihiro Suzuki
We can reproduce this issue as follows:
{code}
create 'test', "f", {METADATA => {'hbase.regionserver.region.split.policy' =>
'UNDEFINED'}}
{code}
After running this, creating table will get stuck. And it looks like this is
because opening region fails with ClassNotFoundException:
{code}
2019-12-16 06:45:03,671 ERROR [RS_OPEN_REGION-regionserver/c126-node2:16020-17]
handler.OpenRegionHandler: Failed open of
region=test,,1576477039045.7435965ddb2229c62d926b3ee963dcf3.
java.io.IOException: Unable to load configured region split policy 'UNDEFINED'
for table 'test'
at
org.apache.hadoop.hbase.regionserver.RegionSplitPolicy.getSplitPolicyClass(RegionSplitPolicy.java:132)
at
org.apache.hadoop.hbase.regionserver.HRegion.checkClassLoading(HRegion.java:7162)
at
org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:7083)
at
org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:7043)
at
org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:7015)
at
org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6973)
at
org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6924)
at
org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:283)
at
org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:108)
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException: UNDEFINED
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at
org.apache.hadoop.hbase.regionserver.RegionSplitPolicy.getSplitPolicyClass(RegionSplitPolicy.java:127)
... 12 more
{code}
We should have sanity checks for the properties specified in METADATA.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-22096) /storeFile.jsp shows CorruptHFileException when the storeFile is a reference file
[ https://issues.apache.org/jira/browse/HBASE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-22096. -- Resolution: Fixed > /storeFile.jsp shows CorruptHFileException when the storeFile is a reference > file > - > > Key: HBASE-22096 > URL: https://issues.apache.org/jira/browse/HBASE-22096 > Project: HBase > Issue Type: Bug > Components: UI >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0, 2.3.0, 1.6.0, 2.2.3, 2.1.9, 1.4.13 > > Attachments: HBASE-22096.branch-2.2.addendum.v1.patch, screanshot.png > > > When the storeFile is a reference file, /storeFile.jsp for the storeFile > shows the following error: > !screanshot.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (HBASE-22096) /storeFile.jsp shows CorruptHFileException when the storeFile is a reference file
[ https://issues.apache.org/jira/browse/HBASE-22096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki reopened HBASE-22096: -- > /storeFile.jsp shows CorruptHFileException when the storeFile is a reference > file > - > > Key: HBASE-22096 > URL: https://issues.apache.org/jira/browse/HBASE-22096 > Project: HBase > Issue Type: Bug > Components: UI >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0, 2.3.0, 1.6.0, 2.2.3, 2.1.9 > > Attachments: HBASE-22096.branch-2.2.addendum.v1.patch, screanshot.png > > > When the storeFile is a reference file, /storeFile.jsp for the storeFile > shows the following error: > !screanshot.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23359) RS going down with NPE when splitting a region with compaction disabled in branch-1
[
https://issues.apache.org/jira/browse/HBASE-23359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toshihiro Suzuki resolved HBASE-23359.
--
Resolution: Fixed
> RS going down with NPE when splitting a region with compaction disabled in
> branch-1
> ---
>
> Key: HBASE-23359
> URL: https://issues.apache.org/jira/browse/HBASE-23359
> Project: HBase
> Issue Type: Bug
>Reporter: Toshihiro Suzuki
>Assignee: Toshihiro Suzuki
>Priority: Major
> Fix For: 1.6.0
>
>
> Trying to backport HBASE-22096 to brach-1, I faced the issue where a RS goes
> down with NPE when splitting a region with compaction disabled.
> The steps to reproduce this issue are as follows:
> {code}
> compaction_switch false
> create "test", "cf"
> (0...2000).each{|i| put "test", "row#{i}", "cf:col", "val#{i}"}
> split "test"
> {code}
> Looking at the regionserver log, I saw the following log:
> {code}
> 2019-12-03 22:25:38,611 INFO [RS:0;10.0.1.11:53504-splits-0]
> regionserver.SplitRequest: Running rollback/cleanup of failed split of
> test,,1575379535506.50e322ec68162025e17cddffdc2fb17e.; null
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.regionserver.HStore.cancelRequestedCompaction(HStore.java:1834)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplitThread$Rejection.rejectedExecution(CompactSplitThread.java:656)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
> at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplitThread.requestCompactionInternal(CompactSplitThread.java:401)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplitThread.requestSystemCompaction(CompactSplitThread.java:348)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.postOpenDeployTasks(HRegionServer.java:2111)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.postOpenDeployTasks(HRegionServer.java:2097)
> at
> org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.openDaughters(SplitTransactionImpl.java:478)
> at
> org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.stepsAfterPONR(SplitTransactionImpl.java:549)
> at
> org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.execute(SplitTransactionImpl.java:532)
> at
> org.apache.hadoop.hbase.regionserver.SplitRequest.doSplitting(SplitRequest.java:82)
> at
> org.apache.hadoop.hbase.regionserver.SplitRequest.run(SplitRequest.java:153)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> 2019-12-03 22:25:38,613 FATAL [RS:0;10.0.1.11:53504-splits-0]
> regionserver.HRegionServer: ABORTING region server
> 10.0.1.11,53504,1575379011279: Abort; we got an error after point-of-no-return
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (HBASE-23359) RS going down with NPE when splitting a region with compaction disabled in branch-1
[
https://issues.apache.org/jira/browse/HBASE-23359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toshihiro Suzuki reopened HBASE-23359:
--
Reopening. Will push it to branch-1.4.
> RS going down with NPE when splitting a region with compaction disabled in
> branch-1
> ---
>
> Key: HBASE-23359
> URL: https://issues.apache.org/jira/browse/HBASE-23359
> Project: HBase
> Issue Type: Bug
>Reporter: Toshihiro Suzuki
>Assignee: Toshihiro Suzuki
>Priority: Major
> Fix For: 1.6.0
>
>
> Trying to backport HBASE-22096 to brach-1, I faced the issue where a RS goes
> down with NPE when splitting a region with compaction disabled.
> The steps to reproduce this issue are as follows:
> {code}
> compaction_switch false
> create "test", "cf"
> (0...2000).each{|i| put "test", "row#{i}", "cf:col", "val#{i}"}
> split "test"
> {code}
> Looking at the regionserver log, I saw the following log:
> {code}
> 2019-12-03 22:25:38,611 INFO [RS:0;10.0.1.11:53504-splits-0]
> regionserver.SplitRequest: Running rollback/cleanup of failed split of
> test,,1575379535506.50e322ec68162025e17cddffdc2fb17e.; null
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.regionserver.HStore.cancelRequestedCompaction(HStore.java:1834)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplitThread$Rejection.rejectedExecution(CompactSplitThread.java:656)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
> at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplitThread.requestCompactionInternal(CompactSplitThread.java:401)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplitThread.requestSystemCompaction(CompactSplitThread.java:348)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.postOpenDeployTasks(HRegionServer.java:2111)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.postOpenDeployTasks(HRegionServer.java:2097)
> at
> org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.openDaughters(SplitTransactionImpl.java:478)
> at
> org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.stepsAfterPONR(SplitTransactionImpl.java:549)
> at
> org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.execute(SplitTransactionImpl.java:532)
> at
> org.apache.hadoop.hbase.regionserver.SplitRequest.doSplitting(SplitRequest.java:82)
> at
> org.apache.hadoop.hbase.regionserver.SplitRequest.run(SplitRequest.java:153)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> 2019-12-03 22:25:38,613 FATAL [RS:0;10.0.1.11:53504-splits-0]
> regionserver.HRegionServer: ABORTING region server
> 10.0.1.11,53504,1575379011279: Abort; we got an error after point-of-no-return
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-23303) Add security headers to REST server/info page
[
https://issues.apache.org/jira/browse/HBASE-23303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toshihiro Suzuki resolved HBASE-23303.
--
Resolution: Fixed
> Add security headers to REST server/info page
> -
>
> Key: HBASE-23303
> URL: https://issues.apache.org/jira/browse/HBASE-23303
> Project: HBase
> Issue Type: Improvement
> Components: REST
>Affects Versions: 3.0.0, 2.0.6, 2.1.7, 2.2.2
>Reporter: Andor Molnar
>Assignee: Andor Molnar
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.3, 2.1.9
>
>
> Vulnerability scanners suggest that the following extra headers should be
> added to both Info/Rest server endpoints which are exposed by {{hbase-rest}}
> project.
> * X-Frame-Options: SAMEORIGIN
> * X-Xss-Protection: 1; mode=block
> * X-Content-Type-Options: nosniff
> * Strict-Transport-Security: “max-age=63072000;includeSubDomains;preload”
> * Content-Security-Policy: default-src https: data: 'unsafe-inline'
> 'unsafe-eval'
> Info server already has "X-Frame-Options: DENY" which is more restrictive
> than "SAMEORIGIN", so it's probably fine. All of three headers are missing
> from REST responses.
> I'll put together a patch to resolve this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-23359) RS going down with NPE when splitting a region with compaction disabled in branch-1
[
https://issues.apache.org/jira/browse/HBASE-23359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toshihiro Suzuki resolved HBASE-23359.
--
Assignee: Toshihiro Suzuki
Resolution: Fixed
> RS going down with NPE when splitting a region with compaction disabled in
> branch-1
> ---
>
> Key: HBASE-23359
> URL: https://issues.apache.org/jira/browse/HBASE-23359
> Project: HBase
> Issue Type: Bug
>Reporter: Toshihiro Suzuki
>Assignee: Toshihiro Suzuki
>Priority: Major
> Fix For: 1.6.0
>
>
> Trying to backport HBASE-22096 to brach-1, I faced the issue where a RS goes
> down with NPE when splitting a region with compaction disabled.
> The steps to reproduce this issue are as follows:
> {code}
> compaction_switch false
> create "test", "cf"
> (0...2000).each{|i| put "test", "row#{i}", "cf:col", "val#{i}"}
> split "test"
> {code}
> Looking at the regionserver log, I saw the following log:
> {code}
> 2019-12-03 22:25:38,611 INFO [RS:0;10.0.1.11:53504-splits-0]
> regionserver.SplitRequest: Running rollback/cleanup of failed split of
> test,,1575379535506.50e322ec68162025e17cddffdc2fb17e.; null
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.regionserver.HStore.cancelRequestedCompaction(HStore.java:1834)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplitThread$Rejection.rejectedExecution(CompactSplitThread.java:656)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
> at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplitThread.requestCompactionInternal(CompactSplitThread.java:401)
> at
> org.apache.hadoop.hbase.regionserver.CompactSplitThread.requestSystemCompaction(CompactSplitThread.java:348)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.postOpenDeployTasks(HRegionServer.java:2111)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.postOpenDeployTasks(HRegionServer.java:2097)
> at
> org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.openDaughters(SplitTransactionImpl.java:478)
> at
> org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.stepsAfterPONR(SplitTransactionImpl.java:549)
> at
> org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.execute(SplitTransactionImpl.java:532)
> at
> org.apache.hadoop.hbase.regionserver.SplitRequest.doSplitting(SplitRequest.java:82)
> at
> org.apache.hadoop.hbase.regionserver.SplitRequest.run(SplitRequest.java:153)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> 2019-12-03 22:25:38,613 FATAL [RS:0;10.0.1.11:53504-splits-0]
> regionserver.HRegionServer: ABORTING region server
> 10.0.1.11,53504,1575379011279: Abort; we got an error after point-of-no-return
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-23359) RS going down with NPE when splitting a region with compaction disabled in branch-1
Toshihiro Suzuki created HBASE-23359:
Summary: RS going down with NPE when splitting a region with
compaction disabled in branch-1
Key: HBASE-23359
URL: https://issues.apache.org/jira/browse/HBASE-23359
Project: HBase
Issue Type: Bug
Reporter: Toshihiro Suzuki
Trying to backport HBASE-22096 to brach-1, I faced the issue where a RS goes
down with NPE when splitting a region with compaction disabled.
The steps to reproduce this issue are as follows:
{code}
compaction_switch false
create "test", "cf"
(0...2000).each{|i| put "test", "row#{i}", "cf:col", "val#{i}"}
split "test"
{code}
Looking at the regionserver log, I saw the following log:
{code}
2019-12-03 22:25:38,611 INFO [RS:0;10.0.1.11:53504-splits-0]
regionserver.SplitRequest: Running rollback/cleanup of failed split of
test,,1575379535506.50e322ec68162025e17cddffdc2fb17e.; null
java.lang.NullPointerException
at
org.apache.hadoop.hbase.regionserver.HStore.cancelRequestedCompaction(HStore.java:1834)
at
org.apache.hadoop.hbase.regionserver.CompactSplitThread$Rejection.rejectedExecution(CompactSplitThread.java:656)
at
java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
at
java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
at
org.apache.hadoop.hbase.regionserver.CompactSplitThread.requestCompactionInternal(CompactSplitThread.java:401)
at
org.apache.hadoop.hbase.regionserver.CompactSplitThread.requestSystemCompaction(CompactSplitThread.java:348)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.postOpenDeployTasks(HRegionServer.java:2111)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.postOpenDeployTasks(HRegionServer.java:2097)
at
org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.openDaughters(SplitTransactionImpl.java:478)
at
org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.stepsAfterPONR(SplitTransactionImpl.java:549)
at
org.apache.hadoop.hbase.regionserver.SplitTransactionImpl.execute(SplitTransactionImpl.java:532)
at
org.apache.hadoop.hbase.regionserver.SplitRequest.doSplitting(SplitRequest.java:82)
at
org.apache.hadoop.hbase.regionserver.SplitRequest.run(SplitRequest.java:153)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2019-12-03 22:25:38,613 FATAL [RS:0;10.0.1.11:53504-splits-0]
regionserver.HRegionServer: ABORTING region server
10.0.1.11,53504,1575379011279: Abort; we got an error after point-of-no-return
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-23166) [hbtop] Use a terminal library instead of writing our own
Toshihiro Suzuki created HBASE-23166: Summary: [hbtop] Use a terminal library instead of writing our own Key: HBASE-23166 URL: https://issues.apache.org/jira/browse/HBASE-23166 Project: HBase Issue Type: Improvement Reporter: Toshihiro Suzuki Currently, we use a custom terminal implementation in hbtop. Ideally, we should use a 3rd party terminal/libs instead of writing our own. This is discussed in the following: https://github.com/apache/hbase/pull/476 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23165) [hbtop] Some modifications from HBASE-22988
Toshihiro Suzuki created HBASE-23165: Summary: [hbtop] Some modifications from HBASE-22988 Key: HBASE-23165 URL: https://issues.apache.org/jira/browse/HBASE-23165 Project: HBase Issue Type: Improvement Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Some modifications happened in the review of HBASE-22988. We can forward port them to the master branch. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23115) Unit change for StoreFileSize and MemStoreSize
[ https://issues.apache.org/jira/browse/HBASE-23115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-23115. -- Resolution: Fixed > Unit change for StoreFileSize and MemStoreSize > -- > > Key: HBASE-23115 > URL: https://issues.apache.org/jira/browse/HBASE-23115 > Project: HBase > Issue Type: Bug > Components: metrics, UI >Affects Versions: 3.0.0 >Reporter: Karthik Palanisamy >Assignee: Karthik Palanisamy >Priority: Minor > Fix For: 3.0.0, 2.3.0, 2.2.2, 2.1.8 > > Attachments: Units.pdf > > > StoreFileSize and MemstoreSize usually returned in MBs (link1, link2) but > few jsp pages contain inaccurate unit. The reason is table.jsp (link3) use > org.apache.hadoop.util.StringUtils.byteDesc(long len), this will perform > longtostring conversion and returns its unit(B, KB, MB, GB, TB, PB) based on > length. The concern here (link4) is computation (ByteVal/1024/1024) will > output always lesser than 1 for store contains few bytes or few kbs. Also, > typecast will not round up to its nearest value. > I think the best option is changing unit in table.jsp instead of changing > code, otherwise we may end up doing many refactors from getMemStoreSizeMB, > setMemStoreSizeMB, hasMemStoreSizeMB, getStorefileSizeMB, > setStorefileSizeMB,.. > > Please find the attachment, a simple example is posted. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23146) Support CheckAnd* with multi conditions
Toshihiro Suzuki created HBASE-23146: Summary: Support CheckAnd* with multi conditions Key: HBASE-23146 URL: https://issues.apache.org/jira/browse/HBASE-23146 Project: HBase Issue Type: New Feature Reporter: Toshihiro Suzuki Currently, checkAnd* supports only single condition. Supporting checkAnd* with multi conditions is useful for some use cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-22992) Blog post for hbtop on hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-22992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-22992. -- Resolution: Fixed > Blog post for hbtop on hbase.apache.org > --- > > Key: HBASE-22992 > URL: https://issues.apache.org/jira/browse/HBASE-22992 > Project: HBase > Issue Type: Sub-task >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-22986) Add documentation for hbtop
[ https://issues.apache.org/jira/browse/HBASE-22986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-22986. -- Resolution: Fixed > Add documentation for hbtop > --- > > Key: HBASE-22986 > URL: https://issues.apache.org/jira/browse/HBASE-22986 > Project: HBase > Issue Type: Sub-task > Components: documentation, hbtop >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Minor > Fix For: 3.0.0 > > > We already have README for hbtop, so we can make the refguide refer to this: > [https://github.com/apache/hbase/blob/master/hbase-hbtop/README.md] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (HBASE-22992) Blog post for hbtop on hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-22992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki reopened HBASE-22992: -- > Blog post for hbtop on hbase.apache.org > --- > > Key: HBASE-22992 > URL: https://issues.apache.org/jira/browse/HBASE-22992 > Project: HBase > Issue Type: Sub-task >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23064) [hbtop] Rewrite the parsing logic to a better way in RecordFilter
Toshihiro Suzuki created HBASE-23064: Summary: [hbtop] Rewrite the parsing logic to a better way in RecordFilter Key: HBASE-23064 URL: https://issues.apache.org/jira/browse/HBASE-23064 Project: HBase Issue Type: Improvement Components: hbtop Reporter: Toshihiro Suzuki As discussed in the following, we can rewrite the parsing logic to a better way (like index-substring way or pattern-matching way?) in RecordFilter: https://github.com/apache/hbase/pull/647#discussion_r326979376 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-22992) Blog post for hbtop on hbase.apache.org
Toshihiro Suzuki created HBASE-22992: Summary: Blog post for hbtop on hbase.apache.org Key: HBASE-22992 URL: https://issues.apache.org/jira/browse/HBASE-22992 Project: HBase Issue Type: Sub-task Reporter: Toshihiro Suzuki -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Reopened] (HBASE-11062) hbtop
[ https://issues.apache.org/jira/browse/HBASE-11062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki reopened HBASE-11062: -- > hbtop > - > > Key: HBASE-11062 > URL: https://issues.apache.org/jira/browse/HBASE-11062 > Project: HBase > Issue Type: New Feature > Components: hbtop >Reporter: Andrew Purtell >Assignee: Toshihiro Suzuki >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.1.7, 2.2.2 > > > A top-like monitor could be useful for testing, debugging, operations of > clusters of moderate size, and possibly for diagnosing issues in large > clusters. > Consider a curses interface like the one presented by atop > (http://www.atoptool.nl/images/screenshots/genericw.png) - with aggregate > metrics collected over a monitoring interval in the upper portion of the > pane, and a listing of discrete measurements sorted and filtered by various > criteria in the bottom part of the pane. One might imagine a cluster overview > with cluster aggregate metrics above and a list of regionservers sorted by > utilization below; and a regionserver view with process metrics above and a > list of metrics by operation type below, or a list of client connections, or > a list of threads, sorted by utilization, throughput, or latency. > Generically 'htop' is taken but would be distinctive in the HBase context, a > utility org.apache.hadoop.hbase.HTop > No need necessarily for a curses interface. Could be an external monitor with > a web front end as has been discussed before. I do like the idea of a process > that runs in a terminal because I interact with dev and test HBase clusters > exclusively by SSH. > UPDATE: > The tool name is changed from htop to hbtop. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (HBASE-22988) Backport HBASE-11062 "hbtop" to branch-1
Toshihiro Suzuki created HBASE-22988: Summary: Backport HBASE-11062 "hbtop" to branch-1 Key: HBASE-22988 URL: https://issues.apache.org/jira/browse/HBASE-22988 Project: HBase Issue Type: Sub-task Components: backport, hbtop Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Backport parent issue to branch-1. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (HBASE-22986) Add documentation for hbtop
Toshihiro Suzuki created HBASE-22986: Summary: Add documentation for hbtop Key: HBASE-22986 URL: https://issues.apache.org/jira/browse/HBASE-22986 Project: HBase Issue Type: Improvement Components: documentation, hbtop Reporter: Toshihiro Suzuki We already have README for hbtop, so we can make the refguide refer to this: [https://github.com/apache/hbase/blob/master/hbase-hbtop/README.md] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (HBASE-22818) regionserver's version in master status page
[ https://issues.apache.org/jira/browse/HBASE-22818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-22818. -- Resolution: Duplicate This issue was fixed by HBASE-20784. Resolving as Duplicate. > regionserver's version in master status page > > > Key: HBASE-22818 > URL: https://issues.apache.org/jira/browse/HBASE-22818 > Project: HBase > Issue Type: Bug > Environment: hortonworks 3.1.0.0-78 distribution with hbase 2.0.2 > version. >Reporter: Olivier Delhomme >Priority: Minor > Attachments: inconsistent_version.png > > > Hi, > Regionserver's version in master status page are displaying 11 nodes with > 2.0.2 version. The final line says : 11 nodes with inconsistent version (in > red). > Thanks. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HBASE-22690) Deprecate / Remove OfflineMetaRepair in hbase-2+
Toshihiro Suzuki created HBASE-22690: Summary: Deprecate / Remove OfflineMetaRepair in hbase-2+ Key: HBASE-22690 URL: https://issues.apache.org/jira/browse/HBASE-22690 Project: HBase Issue Type: Improvement Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki As discussed in the following thread, we can deprecate / remove OfflineMetaRepair. https://lists.apache.org/thread.html/f122efdc79be541d678e22cf8cf573352ab468159596d820c38bf84b@%3Cdev.hbase.apache.org%3E Maybe we can deprecate in 2.x and remove in 3.0. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HBASE-22661) list_regions command in hbase shell is broken
Toshihiro Suzuki created HBASE-22661:
Summary: list_regions command in hbase shell is broken
Key: HBASE-22661
URL: https://issues.apache.org/jira/browse/HBASE-22661
Project: HBase
Issue Type: Bug
Reporter: Toshihiro Suzuki
I faced the following error in the master branch:
{code}
hbase(main):001:0> create "test", "cf"
2019-07-07 23:24:15,254 WARN [main] util.NativeCodeLoader: Unable to load
native-hadoop library for your platform... using builtin-java classes where
applicable
Created table test
Took 6.5678 seconds
=> Hbase::Table - test
hbase(main):002:0> list_regions "test"
ERROR: undefined method `getClusterStatus' for
#
Did you mean? get_cluster_metrics
For usage try 'help "list_regions"'
Took 0.1997 seconds
{code}
I didn't check if the other branches has the same issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-22541) Backport HBASE-22160 "Add sorting functionality in regionserver web UI for user regions" to branch-1
Toshihiro Suzuki created HBASE-22541: Summary: Backport HBASE-22160 "Add sorting functionality in regionserver web UI for user regions" to branch-1 Key: HBASE-22541 URL: https://issues.apache.org/jira/browse/HBASE-22541 Project: HBase Issue Type: Sub-task Components: backport Reporter: Toshihiro Suzuki Assignee: Daisuke Kobayashi Backport parent issue to branch-1. Hope you don't mind my assigning it to you [~daisuke.kobayashi] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-16750) hbase compilation failed on power system
[
https://issues.apache.org/jira/browse/HBASE-16750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Toshihiro Suzuki resolved HBASE-16750.
--
Resolution: Duplicate
> hbase compilation failed on power system
>
>
> Key: HBASE-16750
> URL: https://issues.apache.org/jira/browse/HBASE-16750
> Project: HBase
> Issue Type: Bug
> Components: build, documentation
>Affects Versions: 1.1.2
>Reporter: Saravanan Krishnamoorthy
>Assignee: Saravanan Krishnamoorthy
>Priority: Major
> Attachments: HBASE-16750.branch-1.patch, HBASE-16750.master.patch,
> apache_hbase_reference_guide.pdf, apache_hbase_reference_guide.pdfmarks,
> book.pdf, book.pdfmarks
>
>
> Hi,
> hbase compilation failed on IBM power system ppc64le architecture with below
> error:
> {code}
> Hbase Failure:
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:33 min
> [INFO] Finished at: 2016-09-30T08:58:47-04:00
> [INFO] Final Memory: 215M/843M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: org.jruby.exceptions.RaiseException: (NotImplementedError) fstat
> unimplemented unsupported or native support failed to load
> at org.jruby.RubyFile.size(org/jruby/RubyFile.java:1108)
> at
> RUBY.render_body(/grid/0/jenkins/.m2/repository/org/asciidoctor/asciidoctorj-pdf/1.5.0-alpha.6/asciidoctorj-pdf-1.5.0-alpha.6.jar!/gems/pdf-core-0.2.5/lib/pdf/core/document_state.rb:69)
> at
>
[jira] [Resolved] (HBASE-18373) fstat unimplemented error on Rasbian Jessie
[ https://issues.apache.org/jira/browse/HBASE-18373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-18373. -- Resolution: Not A Problem > fstat unimplemented error on Rasbian Jessie > --- > > Key: HBASE-18373 > URL: https://issues.apache.org/jira/browse/HBASE-18373 > Project: HBase > Issue Type: Bug > Components: shell >Affects Versions: 2.0.0-alpha-1 > Environment: Raspberry Pi 3 > Rasbian Jessie (latest version) >Reporter: Nathan Green >Priority: Blocker > > I have a Hbase distributed cluster setup on my Raspberry PI cluster (1 x > Namenode & 4 x Datanode) > The stable version of Hbase shell works fine... unfortunately I had hadoop > issues (mismatch of jar files gr) so I have installed latest Hbase & > installed matching version of Hadoop (2.7.1). > HBase itself is up and running and all good. Hbase shell however gives this > error: > pi@pidoop1:/opt/hbase/lib/ruby/irb $ hbase shell > 2017-07-13 12:25:11,722 WARN [main] util.NativeCodeLoader: Unable to load > native-hadoop library for your platform... using builtin-java classes where > applicable > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/opt/hbase/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/opt/hadoop/share/hadoop/common/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory] > HBase Shell > Use "help" to get list of supported commands. > Use "exit" to quit this interactive shell. > Version 2.0.0-alpha-1, rc830a0f47f58d4892dd3300032c8244d6278aecc, Wed Jun 7 > 22:05:17 PDT 2017 > Took 0.0300 seconds > NotImplementedError: fstat unimplemented unsupported or native support failed > to load; see http://wiki.jruby.org/Native-Libraries > initialize at org/jruby/RubyIO.java:1013 > open at org/jruby/RubyIO.java:1154 > initialize at > uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/irb/input-method.rb:141 > initialize at > uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/irb/context.rb:70 > initialize at > uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/irb.rb:426 > initialize at /opt/hbase/lib/ruby/irb/hirb.rb:43 >start at /opt/hbase/bin/hirb.rb:194 >at /opt/hbase/bin/hirb.rb:206 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-22118) Backport HBASE-22095 "Taking a snapshot fails in local mode"
[ https://issues.apache.org/jira/browse/HBASE-22118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toshihiro Suzuki resolved HBASE-22118. -- Resolution: Invalid > Backport HBASE-22095 "Taking a snapshot fails in local mode" > > > Key: HBASE-22118 > URL: https://issues.apache.org/jira/browse/HBASE-22118 > Project: HBase > Issue Type: Sub-task >Reporter: Toshihiro Suzuki >Assignee: Toshihiro Suzuki >Priority: Major > > Backport the parent issue to branch-1. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-22118) Backport HBASE-22095 "Taking a snapshot fails in local mode"
Toshihiro Suzuki created HBASE-22118: Summary: Backport HBASE-22095 "Taking a snapshot fails in local mode" Key: HBASE-22118 URL: https://issues.apache.org/jira/browse/HBASE-22118 Project: HBase Issue Type: Sub-task Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Backport the parent issue to branch-1. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-22097) Modify the description of split command in shell
Toshihiro Suzuki created HBASE-22097: Summary: Modify the description of split command in shell Key: HBASE-22097 URL: https://issues.apache.org/jira/browse/HBASE-22097 Project: HBase Issue Type: Improvement Components: shell Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki We can make the description of split command in shell better. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-22096) /storeFile.jsp shows CorruptHFileException when the storeFile is a reference file
Toshihiro Suzuki created HBASE-22096: Summary: /storeFile.jsp shows CorruptHFileException when the storeFile is a reference file Key: HBASE-22096 URL: https://issues.apache.org/jira/browse/HBASE-22096 Project: HBase Issue Type: Bug Components: UI Reporter: Toshihiro Suzuki Assignee: Toshihiro Suzuki Attachments: screanshot.png When the storeFile is a reference file, /storeFile.jsp shows the following error: !screanshot.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
