[jira] [Assigned] (HBASE-25633) When unconfigured, PressureAwareCompactionThroughputController should sniff NIC speed and use appropriate settings
[ https://issues.apache.org/jira/browse/HBASE-25633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divyesh Chandra reassigned HBASE-25633: --- Assignee: Divyesh Chandra > When unconfigured, PressureAwareCompactionThroughputController should sniff > NIC speed and use appropriate settings > -- > > Key: HBASE-25633 > URL: https://issues.apache.org/jira/browse/HBASE-25633 > Project: HBase > Issue Type: Improvement > Components: Compaction >Reporter: Nick Dimiduk >Assignee: Divyesh Chandra >Priority: Major > > After upgrading a cluster to 2.3, we noticed that compactions were taking > much longer. We tracked this down to the > PressureAwareCompactionThroughputController, which became default as part of > our upgrade. Our default configuration settings set the lower bound: 50MB/s, > upper bound: 100MB/s. These settings make sense if you have a 1gbit NIC (~120 > MB/s). For a 10gbit NIC, they’re quite inadequate. > Suggestion: instead of using fixed values as the default for these > configurations, we should sniff the NIC speed and configure for an optimal > value according to available bandwidth. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-25633) When unconfigured, PressureAwareCompactionThroughputController should sniff NIC speed and use appropriate settings
[ https://issues.apache.org/jira/browse/HBASE-25633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308591#comment-17308591 ] Divyesh Chandra commented on HBASE-25633: - Hi Nick, Id like to work on this. Assigning it to myself. > When unconfigured, PressureAwareCompactionThroughputController should sniff > NIC speed and use appropriate settings > -- > > Key: HBASE-25633 > URL: https://issues.apache.org/jira/browse/HBASE-25633 > Project: HBase > Issue Type: Improvement > Components: Compaction >Reporter: Nick Dimiduk >Priority: Major > > After upgrading a cluster to 2.3, we noticed that compactions were taking > much longer. We tracked this down to the > PressureAwareCompactionThroughputController, which became default as part of > our upgrade. Our default configuration settings set the lower bound: 50MB/s, > upper bound: 100MB/s. These settings make sense if you have a 1gbit NIC (~120 > MB/s). For a 10gbit NIC, they’re quite inadequate. > Suggestion: instead of using fixed values as the default for these > configurations, we should sniff the NIC speed and configure for an optimal > value according to available bandwidth. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HBASE-25694) Improve the shell's 'status replication' command output
[ https://issues.apache.org/jira/browse/HBASE-25694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divyesh Chandra reassigned HBASE-25694: --- Assignee: Divyesh Chandra > Improve the shell's 'status replication' command output > --- > > Key: HBASE-25694 > URL: https://issues.apache.org/jira/browse/HBASE-25694 > Project: HBase > Issue Type: Task > Components: Operability, Replication, shell >Affects Versions: 2.4.2 >Reporter: Andrew Kyle Purtell >Assignee: Divyesh Chandra >Priority: Major > Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3 > > > The output of the shell's 'status "replication"' command could use some > cleaning up. > The basic format is: > version VERSION > N live servers > SERVER_1: >SOURCE: PeerID=PEERID, AgeOfLastShippedOp=160347, SizeOfLogQueue=49, > TimeStampsOfLastShippedOp=Thu Mar 25 01:55:21 UTC 2021, Replication Lag=161013 >SINK : AgeOfLastAppliedOp=0, TimeStampsOfLastAppliedOp=Thu Mar 25 > 01:49:53 UTC 2021 > ... > Issues: > - Per line format is KEY=VALUE, ... . Most KEYs are CamelCase but some have > spaces. Should all be camel case for consistency. > - Timestamp values are printed both in long and string (local TZ) format. > Pick one. Lets just emit them as long values. > - There is no sense of effective rate or bandwidth. Each source and sink line > emitted should provide some sense of current workload: rpcs/sec, bytes/sec, > cells/sec... something. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (HBASE-25652) Document normalizer features NORMALIZER_TARGET_REGION_SIZE and NORMALIZER_TARGET_REGION_COUNT
[
https://issues.apache.org/jira/browse/HBASE-25652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divyesh Chandra reassigned HBASE-25652:
---
Assignee: Divyesh Chandra
> Document normalizer features NORMALIZER_TARGET_REGION_SIZE and
> NORMALIZER_TARGET_REGION_COUNT
> -
>
> Key: HBASE-25652
> URL: https://issues.apache.org/jira/browse/HBASE-25652
> Project: HBase
> Issue Type: Task
> Components: documentation, Normalizer
>Affects Versions: 2.3.0
>Reporter: Nick Dimiduk
>Assignee: Divyesh Chandra
>Priority: Major
>
> The normalizer can be configured for specific behavior via table properties
> {{NORMALIZER_TARGET_REGION_SIZE}} and {{NORMALIZER_TARGET_REGION_COUNT}}.
> Neither of these are mentioned in the book.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (HBASE-25653) Improve normalizer logging
[ https://issues.apache.org/jira/browse/HBASE-25653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Divyesh Chandra reassigned HBASE-25653: --- Assignee: Divyesh Chandra > Improve normalizer logging > -- > > Key: HBASE-25653 > URL: https://issues.apache.org/jira/browse/HBASE-25653 > Project: HBase > Issue Type: Improvement > Components: master, Normalizer >Affects Versions: 3.0.0-alpha-1, 2.3.0, 2.4.0 >Reporter: Nick Dimiduk >Assignee: Divyesh Chandra >Priority: Major > > Normalizer logs progress and includes details regarding region count and > target size. The size values are logged without units, and floating point > numbers are logged without a specified precision, which can result in > scientific notation. Clean up the formatting of these log messages to make > them easily readable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-25653) Improve normalizer logging
[ https://issues.apache.org/jira/browse/HBASE-25653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17298498#comment-17298498 ] Divyesh Chandra commented on HBASE-25653: - Hi [~ndimiduk] can I pick this up ? > Improve normalizer logging > -- > > Key: HBASE-25653 > URL: https://issues.apache.org/jira/browse/HBASE-25653 > Project: HBase > Issue Type: Improvement > Components: master, Normalizer >Affects Versions: 3.0.0-alpha-1, 2.3.0, 2.4.0 >Reporter: Nick Dimiduk >Priority: Major > > Normalizer logs progress and includes details regarding region count and > target size. The size values are logged without units, and floating point > numbers are logged without a specified precision, which can result in > scientific notation. Clean up the formatting of these log messages to make > them easily readable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-25630) Set switch compaction after bulkload default as false
[ https://issues.apache.org/jira/browse/HBASE-25630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295965#comment-17295965 ] Divyesh Chandra commented on HBASE-25630: - Sorry [~niuyulin] I am a beginner here and raised a PR before you without the Jira being assigned to me. I am closing my PR. > Set switch compaction after bulkload default as false > - > > Key: HBASE-25630 > URL: https://issues.apache.org/jira/browse/HBASE-25630 > Project: HBase > Issue Type: Improvement >Reporter: Yulin Niu >Assignee: Yulin Niu >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-25610) Support multiple tables as input in generateMissingTableDescriptorFile command in HBCK2
[ https://issues.apache.org/jira/browse/HBASE-25610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295963#comment-17295963 ] Divyesh Chandra commented on HBASE-25610: - Cool. :) > Support multiple tables as input in generateMissingTableDescriptorFile > command in HBCK2 > --- > > Key: HBASE-25610 > URL: https://issues.apache.org/jira/browse/HBASE-25610 > Project: HBase > Issue Type: Improvement > Components: hbase-operator-tools, hbck2 >Reporter: Sanjeet Nishad >Assignee: Sanjeet Nishad >Priority: Minor > > Currently 'generateMissingTableDescriptorFile' command in HBCK2 supports only > 1 TableName as input. HBCK's _fixOrphanTables()_ had a support for fixing the > missing .tableinfo files for a list of tables and it also supported fixing > the missing descriptor for all tables if no tables were specified. > It looks like a convinient enhancement to have in > generateMissingTableDescriptorFile command of HBCK2. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (HBASE-25610) Support multiple tables as input in generateMissingTableDescriptorFile command in HBCK2
[ https://issues.apache.org/jira/browse/HBASE-25610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295488#comment-17295488 ] Divyesh Chandra edited comment on HBASE-25610 at 3/5/21, 3:16 AM: -- Hi I would like to pick this up was (Author: divyesh): Hi I would like to try taking this on. > Support multiple tables as input in generateMissingTableDescriptorFile > command in HBCK2 > --- > > Key: HBASE-25610 > URL: https://issues.apache.org/jira/browse/HBASE-25610 > Project: HBase > Issue Type: Improvement > Components: hbase-operator-tools, hbck2 >Reporter: Sanjeet Nishad >Assignee: Sanjeet Nishad >Priority: Minor > > Currently 'generateMissingTableDescriptorFile' command in HBCK2 supports only > 1 TableName as input. HBCK's _fixOrphanTables()_ had a support for fixing the > missing .tableinfo files for a list of tables and it also supported fixing > the missing descriptor for all tables if no tables were specified. > It looks like a convinient enhancement to have in > generateMissingTableDescriptorFile command of HBCK2. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-25610) Support multiple tables as input in generateMissingTableDescriptorFile command in HBCK2
[ https://issues.apache.org/jira/browse/HBASE-25610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295488#comment-17295488 ] Divyesh Chandra commented on HBASE-25610: - Hi I would like to try taking this on. > Support multiple tables as input in generateMissingTableDescriptorFile > command in HBCK2 > --- > > Key: HBASE-25610 > URL: https://issues.apache.org/jira/browse/HBASE-25610 > Project: HBase > Issue Type: Improvement > Components: hbase-operator-tools, hbck2 >Reporter: Sanjeet Nishad >Assignee: Sanjeet Nishad >Priority: Minor > > Currently 'generateMissingTableDescriptorFile' command in HBCK2 supports only > 1 TableName as input. HBCK's _fixOrphanTables()_ had a support for fixing the > missing .tableinfo files for a list of tables and it also supported fixing > the missing descriptor for all tables if no tables were specified. > It looks like a convinient enhancement to have in > generateMissingTableDescriptorFile command of HBCK2. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-25630) Set switch compaction after bulkload default as false
[ https://issues.apache.org/jira/browse/HBASE-25630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295475#comment-17295475 ] Divyesh Chandra commented on HBASE-25630: - Hi [~niuyulin] can I pick this up ? > Set switch compaction after bulkload default as false > - > > Key: HBASE-25630 > URL: https://issues.apache.org/jira/browse/HBASE-25630 > Project: HBase > Issue Type: Improvement >Reporter: Yulin Niu >Assignee: Yulin Niu >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
