[jira] [Updated] (HBASE-26987) The length of compact queue grows too big when the compacting is slow
[ https://issues.apache.org/jira/browse/HBASE-26987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Wang updated HBASE-26987: --- External issue URL: (was: https://issues.apache.org/jira/browse/HBASE-8665) > The length of compact queue grows too big when the compacting is slow > - > > Key: HBASE-26987 > URL: https://issues.apache.org/jira/browse/HBASE-26987 > Project: HBase > Issue Type: Improvement >Reporter: Zheng Wang >Assignee: Zheng Wang >Priority: Major > Attachments: image-2022-04-29-10-26-09-351.png, > image-2022-04-29-10-26-18-323.png, image-2022-04-29-10-26-24-087.png > > > For some system compaction, we set the selectNow to false, so the file > selecting will not be done until the compaction running, it brings side > effect, if another compacting is slow, we may put lots of compaction to > queue, because the filesCompacting of Hstore is empty in the meantime. > An example shows at attachments, there are 154 regions and about 2000 hfiles, > but the length of compact queue grows to 1391, it cause confusion and may > trigger unexpected alarm. > My approach is limit the compaction queue count, by compute the > filesNotCompating and hbase.hstore.compaction.max. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (HBASE-26987) The length of compact queue grows too big when the compacting is slow
[ https://issues.apache.org/jira/browse/HBASE-26987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Wang updated HBASE-26987: --- External issue URL: https://issues.apache.org/jira/browse/HBASE-8665 > The length of compact queue grows too big when the compacting is slow > - > > Key: HBASE-26987 > URL: https://issues.apache.org/jira/browse/HBASE-26987 > Project: HBase > Issue Type: Improvement >Reporter: Zheng Wang >Assignee: Zheng Wang >Priority: Major > Attachments: image-2022-04-29-10-26-09-351.png, > image-2022-04-29-10-26-18-323.png, image-2022-04-29-10-26-24-087.png > > > For some system compaction, we set the selectNow to false, so the file > selecting will not be done until the compaction running, it brings side > effect, if another compacting is slow, we may put lots of compaction to > queue, because the filesCompacting of Hstore is empty in the meantime. > An example shows at attachments, there are 154 regions and about 2000 hfiles, > but the length of compact queue grows to 1391, it cause confusion and may > trigger unexpected alarm. > My approach is limit the compaction queue count, by compute the > filesNotCompating and hbase.hstore.compaction.max. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (HBASE-26987) The length of compact queue grows too big when the compacting is slow
[ https://issues.apache.org/jira/browse/HBASE-26987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Wang updated HBASE-26987: --- Description: For some system compaction, we set the selectNow to false, so the file selecting will not be done until the compaction running, it brings side effect, if another compacting is slow, we may put lots of compaction to queue, because the filesCompacting of Hstore is empty in the meantime. An example shows at attachments, there are 154 regions and about 2000 hfiles, but the length of compact queue grows to 1391, it cause confusion and may trigger unexpected alarm. My approach is limit the compaction queue count, by compute the filesNotCompating and hbase.hstore.compaction.max. was: For some system compaction, we set the selectNow to false, so the file selecting will not be done until the compaction running, it brings side effect, if another compacting is slow, we may put lots of compaction to queue, because the filesCompacting of Hstore is empty in the meantime. An example shows at attachments, there are 154 regions and about 2000 hfiles, but the length of compact queue grows to 1391, it cause confusion and may trigger unexpected alarm. > The length of compact queue grows too big when the compacting is slow > - > > Key: HBASE-26987 > URL: https://issues.apache.org/jira/browse/HBASE-26987 > Project: HBase > Issue Type: Improvement >Reporter: Zheng Wang >Assignee: Zheng Wang >Priority: Major > Attachments: image-2022-04-29-10-26-09-351.png, > image-2022-04-29-10-26-18-323.png, image-2022-04-29-10-26-24-087.png > > > For some system compaction, we set the selectNow to false, so the file > selecting will not be done until the compaction running, it brings side > effect, if another compacting is slow, we may put lots of compaction to > queue, because the filesCompacting of Hstore is empty in the meantime. > An example shows at attachments, there are 154 regions and about 2000 hfiles, > but the length of compact queue grows to 1391, it cause confusion and may > trigger unexpected alarm. > My approach is limit the compaction queue count, by compute the > filesNotCompating and hbase.hstore.compaction.max. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (HBASE-26987) The length of compact queue grows too big when the compacting is slow
[ https://issues.apache.org/jira/browse/HBASE-26987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Wang updated HBASE-26987: --- Description: For some system compaction, we set the selectNow to false, so the file selecting will not be done until the compaction running, it brings side effect, if another compacting is slow, we may put lots of compaction to queue, because the filesCompacting of Hstore is empty in the meantime. An example shows at attachments, there are 154 regions and about 2000 hfiles, but the length of compact queue grows to 1391, it cause confusion and may trigger unexpected alarm. was: For some system compaction, we set the selectNow to false, so the file selecting will not be done until the compaction running, it brings side effect, if another compacting is slow, we may put lots of compaction to queue, because the filesCompacting of Hstore is empty in the meantime. An example shows at attachments, there are 154 regions and about 2000 hfiles, but the length of compact queue grows to 1391, it cause confusion and may trigger wrong alarm. > The length of compact queue grows too big when the compacting is slow > - > > Key: HBASE-26987 > URL: https://issues.apache.org/jira/browse/HBASE-26987 > Project: HBase > Issue Type: Improvement >Reporter: Zheng Wang >Priority: Major > Attachments: image-2022-04-29-10-26-09-351.png, > image-2022-04-29-10-26-18-323.png, image-2022-04-29-10-26-24-087.png > > > For some system compaction, we set the selectNow to false, so the file > selecting will not be done until the compaction running, it brings side > effect, if another compacting is slow, we may put lots of compaction to > queue, because the filesCompacting of Hstore is empty in the meantime. > An example shows at attachments, there are 154 regions and about 2000 hfiles, > but the length of compact queue grows to 1391, it cause confusion and may > trigger unexpected alarm. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (HBASE-26987) The length of compact queue grows too big when the compacting is slow
[ https://issues.apache.org/jira/browse/HBASE-26987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Wang updated HBASE-26987: --- Description: For some system compaction, we set the selectNow to false, so the file selecting will not be done until the compaction running, it brings side effect, if another compacting is slow, we may put lots of compaction to queue, because the filesCompacting of Hstore is empty in the meantime. An example shows at attachments, there are 154 regions and about 2000 hfiles, but the length of compact queue grows to 1391, it cause confusion and may trigger wrong alarm. was: For some system compaction, we set the selectNow to false, so the file selecting will be done until the compaction running, but it brings a side effect, if another compacting is slow, we may put lots of compaction to queue, because the filesCompacting of Hstore is empty in the meantime. An example shows at attachments, there are 154 regions and about 2000 hfiles, but the length of compact queue grows to 1391, it cause confusion and may trigger wrong alarm. > The length of compact queue grows too big when the compacting is slow > - > > Key: HBASE-26987 > URL: https://issues.apache.org/jira/browse/HBASE-26987 > Project: HBase > Issue Type: Improvement >Reporter: Zheng Wang >Priority: Major > Attachments: image-2022-04-29-10-26-09-351.png, > image-2022-04-29-10-26-18-323.png, image-2022-04-29-10-26-24-087.png > > > For some system compaction, we set the selectNow to false, so the file > selecting will not be done until the compaction running, it brings side > effect, if another compacting is slow, we may put lots of compaction to > queue, because the filesCompacting of Hstore is empty in the meantime. > An example shows at attachments, there are 154 regions and about 2000 hfiles, > but the length of compact queue grows to 1391, it cause confusion and may > trigger wrong alarm. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (HBASE-26987) The length of compact queue grows too big when the compacting is slow
[ https://issues.apache.org/jira/browse/HBASE-26987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Wang updated HBASE-26987: --- Summary: The length of compact queue grows too big when the compacting is slow (was: The length of compact queue too big when the compacting is slow) > The length of compact queue grows too big when the compacting is slow > - > > Key: HBASE-26987 > URL: https://issues.apache.org/jira/browse/HBASE-26987 > Project: HBase > Issue Type: Improvement >Reporter: Zheng Wang >Priority: Major > Attachments: image-2022-04-29-10-26-09-351.png, > image-2022-04-29-10-26-18-323.png, image-2022-04-29-10-26-24-087.png > > > For some system compaction, we set the selectNow to false, so the file > selecting will be done until the compaction running, but it brings a side > effect, if another compacting is slow, we may put lots of compaction to > queue, because the filesCompacting of Hstore is empty in the meantime. > An example shows at attachments, there are 154 regions and about 2000 hfiles, > but the length of compact queue grows to 1391, it cause confusion and may > trigger wrong alarm. -- This message was sent by Atlassian Jira (v8.20.7#820007)
