[jira] [Reopened] (HBASE-14988) java.lang.reflect.InvocationTargetException when doing batch with large number of increment
[
https://issues.apache.org/jira/browse/HBASE-14988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk reopened HBASE-14988:
--
I read too quickly. This is apparently not related to the onejar reflection.
> java.lang.reflect.InvocationTargetException when doing batch with large
> number of increment
> ---
>
> Key: HBASE-14988
> URL: https://issues.apache.org/jira/browse/HBASE-14988
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Keith Lui
>
> Tried to do a 10K increment with batch. When using
> public void batch(List actions, Object[] results)
> got
> java.lang.reflect.InvocationTargetException
> 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 com.simontuffs.onejar.Boot.run(Boot.java:340)
> at com.simontuffs.onejar.Boot.main(Boot.java:166)
> Caused by: java.lang.AssertionError: results.length
> at
> org.apache.hadoop.hbase.client.AsyncProcess$AsyncRequestFutureImpl.(AsyncProcess.java:763)
> at
> org.apache.hadoop.hbase.client.AsyncProcess.createAsyncRequestFuture(AsyncProcess.java:1578)
> at
> org.apache.hadoop.hbase.client.AsyncProcess.submitAll(AsyncProcess.java:554)
> at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:1000)
> Interestingly no exception is thrown when using the deprecated method
> public Object[] batch(List actions)
> This is a sample code in Scala:
> val table = connection.getTable(TableName.valueOf("test_table"))
> val increments = for (i <- 0 until 1) yield {
> val increment = new Increment(Random.nextDouble().toString.getBytes)
> increment.addColumn(family, qualifier, Random.nextLong())
> increment
> }
> table.batch(increments, Array.empty[Object])
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (HBASE-14943) Procedure-V2: Deadlock in WALProcedureStore
[ https://issues.apache.org/jira/browse/HBASE-14943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Yuan Jiang reopened HBASE-14943: > Procedure-V2: Deadlock in WALProcedureStore > --- > > Key: HBASE-14943 > URL: https://issues.apache.org/jira/browse/HBASE-14943 > Project: HBase > Issue Type: Bug > Components: proc-v2 >Affects Versions: 2.0.0, 1.2.0, 1.1.3 >Reporter: Ashu Pachauri >Assignee: Matteo Bertozzi >Priority: Blocker > Fix For: 2.0.0, 1.2.0, 1.1.3 > > Attachments: HBASE-14943-v0.patch, deadlock-jstack.out > > > Found deadlock in WALProcedureStore between the WALProcedureSyncThread and > WALProcedureStore#update/delete/insert API which is used by the > ProcedureExecutor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HBASE-14943) Procedure-V2: Deadlock in WALProcedureStore
[ https://issues.apache.org/jira/browse/HBASE-14943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephen Yuan Jiang resolved HBASE-14943. Resolution: Duplicate > Procedure-V2: Deadlock in WALProcedureStore > --- > > Key: HBASE-14943 > URL: https://issues.apache.org/jira/browse/HBASE-14943 > Project: HBase > Issue Type: Bug > Components: proc-v2 >Affects Versions: 2.0.0, 1.2.0, 1.1.3 >Reporter: Ashu Pachauri >Assignee: Matteo Bertozzi >Priority: Blocker > Fix For: 2.0.0, 1.2.0, 1.1.3 > > Attachments: HBASE-14943-v0.patch, deadlock-jstack.out > > > Found deadlock in WALProcedureStore between the WALProcedureSyncThread and > WALProcedureStore#update/delete/insert API which is used by the > ProcedureExecutor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Successful: HBase Generate Website
Build status: Successful If successful, the website and docs have been generated. If failed, skip to the bottom of this email. Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If you prefer to keep the hbase-site repo around permanently, you can skip the clone step. git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git cd hbase-site wget -O- https://builds.apache.org/job/hbase_generate_website/69/artifact/website.patch.zip | funzip > 7099ab4c56518024a26f5c499a9a1f2ea6bacd6e.patch git fetch git checkout -b asf-site-7099ab4c56518024a26f5c499a9a1f2ea6bacd6e origin/asf-site git am 7099ab4c56518024a26f5c499a9a1f2ea6bacd6e.patch At this point, you can preview the changes by opening index.html or any of the other HTML pages in your local asf-site-7099ab4c56518024a26f5c499a9a1f2ea6bacd6e branch, and you can review the differences by running: git diff origin/asf-site When you are satisfied, publish your changes to origin/asf-site using this command: git push origin asf-site-7099ab4c56518024a26f5c499a9a1f2ea6bacd6e:asf-site Changes take a couple of minutes to be propagated. You can then remove your asf-site-7099ab4c56518024a26f5c499a9a1f2ea6bacd6e branch: git checkout asf-site && git branch -d asf-site-7099ab4c56518024a26f5c499a9a1f2ea6bacd6e If failed, see https://builds.apache.org/job/hbase_generate_website/69/console
[jira] [Reopened] (HBASE-14863) Add missing test/resources/log4j files in hbase modules
[ https://issues.apache.org/jira/browse/HBASE-14863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey reopened HBASE-14863: - In 0.98 this added files into the hbase-spark and hbase-procedure modules that don't exist in that branch. > Add missing test/resources/log4j files in hbase modules > --- > > Key: HBASE-14863 > URL: https://issues.apache.org/jira/browse/HBASE-14863 > Project: HBase > Issue Type: Sub-task > Components: test >Affects Versions: 2.0.0, 1.2.0, 1.1.2 >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi >Priority: Trivial > Fix For: 2.0.0, 1.2.0, 1.3.0, 1.1.3, 0.98.17 > > Attachments: HBASE-14863-v0.patch > > > HBASE-14848 will investigate what is changed and why now we require to have > the log4j file in every submodule. > for now with this jira we are going to commit the log4j files in the missing > hbase modules -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HBASE-14988) java.lang.reflect.InvocationTargetException when doing batch with large number of increment
[
https://issues.apache.org/jira/browse/HBASE-14988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-14988.
--
Resolution: Invalid
Do other operations work with this onejar thing? I suspect it's muddled with
the classloaders and is causing trouble.
Regardless, this looks like it warrants a discussion on the mailing list until
we know what need fixed in HBase. Please start a thread over on
u...@hbase.apache.org. We can reopen this ticket once we've identified what
product fix (if any) is required.
> java.lang.reflect.InvocationTargetException when doing batch with large
> number of increment
> ---
>
> Key: HBASE-14988
> URL: https://issues.apache.org/jira/browse/HBASE-14988
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Keith Lui
>
> Tried to do a 10K increment with batch. When using
> public void batch(List actions, Object[] results)
> got
> java.lang.reflect.InvocationTargetException
> 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 com.simontuffs.onejar.Boot.run(Boot.java:340)
> at com.simontuffs.onejar.Boot.main(Boot.java:166)
> Caused by: java.lang.AssertionError: results.length
> at
> org.apache.hadoop.hbase.client.AsyncProcess$AsyncRequestFutureImpl.(AsyncProcess.java:763)
> at
> org.apache.hadoop.hbase.client.AsyncProcess.createAsyncRequestFuture(AsyncProcess.java:1578)
> at
> org.apache.hadoop.hbase.client.AsyncProcess.submitAll(AsyncProcess.java:554)
> at org.apache.hadoop.hbase.client.HTable.batch(HTable.java:1000)
> Interestingly no exception is thrown when using the deprecated method
> public Object[] batch(List actions)
> This is a sample code in Scala:
> val table = connection.getTable(TableName.valueOf("test_table"))
> val increments = for (i <- 0 until 1) yield {
> val increment = new Increment(Random.nextDouble().toString.getBytes)
> increment.addColumn(family, qualifier, Random.nextLong())
> increment
> }
> table.batch(increments, Array.empty[Object])
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Successful: HBase Generate Website
Build status: Successful If successful, the website and docs have been generated. If failed, skip to the bottom of this email. Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If you prefer to keep the hbase-site repo around permanently, you can skip the clone step. git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git cd hbase-site wget -O- https://builds.apache.org/job/hbase_generate_website/70/artifact/website.patch.zip | funzip > 7099ab4c56518024a26f5c499a9a1f2ea6bacd6e.patch git fetch git checkout -b asf-site-7099ab4c56518024a26f5c499a9a1f2ea6bacd6e origin/asf-site git am 7099ab4c56518024a26f5c499a9a1f2ea6bacd6e.patch At this point, you can preview the changes by opening index.html or any of the other HTML pages in your local asf-site-7099ab4c56518024a26f5c499a9a1f2ea6bacd6e branch, and you can review the differences by running: git diff origin/asf-site When you are satisfied, publish your changes to origin/asf-site using this command: git push origin asf-site-7099ab4c56518024a26f5c499a9a1f2ea6bacd6e:asf-site Changes take a couple of minutes to be propagated. You can then remove your asf-site-7099ab4c56518024a26f5c499a9a1f2ea6bacd6e branch: git checkout asf-site && git branch -d asf-site-7099ab4c56518024a26f5c499a9a1f2ea6bacd6e If failed, see https://builds.apache.org/job/hbase_generate_website/70/console
[jira] [Reopened] (HBASE-14977) ChoreService.shutdown may result in ConcurrentModificationException
[ https://issues.apache.org/jira/browse/HBASE-14977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov reopened HBASE-14977: --- Small addendum to fix failing TestChoreService test > ChoreService.shutdown may result in ConcurrentModificationException > --- > > Key: HBASE-14977 > URL: https://issues.apache.org/jira/browse/HBASE-14977 > Project: HBase > Issue Type: Bug >Reporter: Vladimir Rodionov >Assignee: Vladimir Rodionov >Priority: Minor > Fix For: 2.0.0, 1.2.0, 1.3.0, 1.1.4 > > Attachments: HBASE-14977-add.patch, HBASE-14977-v1.patch > > > As seen in this test: > https://builds.apache.org/job/HBase-1.3/jdk=latest1.8,label=Hadoop/425/artifact/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.regionserver.compactions.TestFIFOCompactionPolicy-output.txt > We need to make shutdown method synchronized to avoid this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Aborted: hbase.apache.org HTML Checker
Aborted If successful, the HTML and link-checking report for http://hbase.apache.org is available at https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/11/artifact/link_report/index.html. If failed, see https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/11/console.
Successful: hbase.apache.org HTML Checker
Successful If successful, the HTML and link-checking report for http://hbase.apache.org is available at https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/12/artifact/link_report/index.html. If failed, see https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/12/console.
Successful: hbase.apache.org HTML Checker
Successful If successful, the HTML and link-checking report for http://hbase.apache.org is available at https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/13/artifact/link_report/index.html. If failed, see https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/13/console.
Successful: hbase.apache.org HTML Checker
Successful If successful, the HTML and link-checking report for http://hbase.apache.org is available at https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/14/artifact/link_report/index.html. If failed, see https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/14/console.
[jira] [Created] (HBASE-14995) Optimize setting tagsPresent in DefaultMemStore.java
huaxiang sun created HBASE-14995:
Summary: Optimize setting tagsPresent in DefaultMemStore.java
Key: HBASE-14995
URL: https://issues.apache.org/jira/browse/HBASE-14995
Project: HBase
Issue Type: Improvement
Components: regionserver
Affects Versions: 2.0.0, 1.2.0
Reporter: huaxiang sun
Priority: Minor
The current implementation calls e.getTagsLength() for each cell. Once
tagsPresent is set, e.getTagsLength() can be avoided.
private boolean addToCellSet(Cell e) {
boolean b = this.cellSet.add(e);
// In no tags case this NoTagsKeyValue.getTagsLength() is a cheap call.
// When we use ACL CP or Visibility CP which deals with Tags during
// mutation, the TagRewriteCell.getTagsLength() is a cheaper call. We do not
// parse the byte[] to identify the tags length.
if(e.getTagsLength() > 0) {
tagsPresent = true;
}
setOldestEditTimeToNow();
return b;
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-14996) Some more API cleanup for 2.0
Enis Soztutar created HBASE-14996: - Summary: Some more API cleanup for 2.0 Key: HBASE-14996 URL: https://issues.apache.org/jira/browse/HBASE-14996 Project: HBase Issue Type: Bug Reporter: Enis Soztutar Fix For: 2.0.0 Parent jira to keep track of some more API cleanup that did not happen in 1.x timeframe. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-14998) Unify synchronous and asynchronous methods in Admin and cleanup
Enis Soztutar created HBASE-14998:
-
Summary: Unify synchronous and asynchronous methods in Admin and
cleanup
Key: HBASE-14998
URL: https://issues.apache.org/jira/browse/HBASE-14998
Project: HBase
Issue Type: Sub-task
Reporter: Enis Soztutar
Fix For: 2.0.0
Admin has a bunch of methods, some are asnyc, some are sync. Needs some
unification in method naming, and method signatures.
- We use modify and alter interchangeably. Pick one and stick with it
(modifyTable(), versus getAlterStatus()). Shell uses {{alter}}.
- Remove getAlterStatus(), should not be needed.
- remove already deprecated methods
- isTableAvailable(TableName tableName, byte[][] splitKeys) should be
removed.
- Consistently use Aysnc as a prefix for all async methods.
- Other ideas?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (HBASE-14974) Total number of Regions in Transition number on UI incorrect
[ https://issues.apache.org/jira/browse/HBASE-14974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Antonov resolved HBASE-14974. - Resolution: Fixed > Total number of Regions in Transition number on UI incorrect > > > Key: HBASE-14974 > URL: https://issues.apache.org/jira/browse/HBASE-14974 > Project: HBase > Issue Type: Bug > Components: UI >Reporter: Elliott Clark >Priority: Trivial > Fix For: 2.0.0, 1.2.0, 1.3.0 > > Attachments: HBASE-14974.patch, Screen Shot 2015-12-14 at 11.34.14 > AM.png > > > Total number of Regions in Transition shows 100 when there are 100 or more > regions in transition. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-14997) Move compareOp and Comparators out of filter to client package
Enis Soztutar created HBASE-14997:
-
Summary: Move compareOp and Comparators out of filter to client
package
Key: HBASE-14997
URL: https://issues.apache.org/jira/browse/HBASE-14997
Project: HBase
Issue Type: Bug
Reporter: Enis Soztutar
Fix For: 2.0.0
{{Table.checkAndPut()}} and its cousins depend on CompareOp from the filter
package. Originally, ComparaOp and ByteArrayComparable, and various
"comparators" have been used in filters, so these are in the filter package.
However, for checkAndPut(), etc we depend on the filter subpackage although
these are not filter related operations. We can use some clean up.
{code}
boolean checkAndPut(byte[] row, byte[] family, byte[] qualifier,
CompareFilter.CompareOp compareOp, byte[] value, Put put) throws
IOException;
{code}
Some ideas
- Cleanup ByteArrayComparable interface (see the TODO at the class)
- Maybe introduce a {{Condition}} or a similar concept and do
{{checkAndPut(Condition condition, Put put)}} and change filters to use that as
well.
- Introducing Condition like thing will allow us to have an interface like:
{{checkAndMutate(List conditions, List mutations)}}.
- BinaryComparator, etc are not "Comparators", they are comparables.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (HBASE-13613) Add test to verify DDL operations from admin when the master is restarted
[ https://issues.apache.org/jira/browse/HBASE-13613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Bertozzi resolved HBASE-13613. - Resolution: Won't Fix Fix Version/s: (was: 1.1.4) (was: 1.2.1) (was: 1.3.0) (was: 2.0.0) closing this one, HBASE-13470 implemented an integration test which is better IntegrationTestDDLMasterFailover > Add test to verify DDL operations from admin when the master is restarted > - > > Key: HBASE-13613 > URL: https://issues.apache.org/jira/browse/HBASE-13613 > Project: HBase > Issue Type: Sub-task > Components: proc-v2, test >Affects Versions: 2.0.0, 1.1.0, 1.2.0 >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi >Priority: Minor > Attachments: HBASE-13613-v0.patch, > org.apache.hadoop.hbase.master.procedure.TestMasterRestartWithProcedures-output.txt > > > Following an offline conversation with [~syuanjiang] we should add back > TestMasterRestartWithProcedures. > more or less it is similar to HBASE-13470 but running in a controlled > unit-test form. it is exercising the kill in a random point of execution + > wal replay of the procedure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-15000) Fix javadoc warn in LoadIncrementalHFiles
Anoop Sam John created HBASE-15000: -- Summary: Fix javadoc warn in LoadIncrementalHFiles Key: HBASE-15000 URL: https://issues.apache.org/jira/browse/HBASE-15000 Project: HBase Issue Type: Bug Reporter: Anoop Sam John Assignee: Ashish Singhi Priority: Trivial [WARNING] Javadoc Warnings [WARNING] /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java:430: warning - @param argument "hfilesDir" is not a parameter name -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (HBASE-14995) Optimize setting tagsPresent in DefaultMemStore.java
[
https://issues.apache.org/jira/browse/HBASE-14995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu reopened HBASE-14995:
> Optimize setting tagsPresent in DefaultMemStore.java
>
>
> Key: HBASE-14995
> URL: https://issues.apache.org/jira/browse/HBASE-14995
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
>Affects Versions: 2.0.0, 1.2.0
>Reporter: huaxiang sun
>Assignee: huaxiang sun
>Priority: Minor
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: HBASE-14995-v001.patch, HBASE-14995-v002.patch
>
>
> The current implementation calls e.getTagsLength() for each cell. Once
> tagsPresent is set, e.getTagsLength() can be avoided.
> {code}
> private boolean addToCellSet(Cell e) {
> boolean b = this.cellSet.add(e);
> // In no tags case this NoTagsKeyValue.getTagsLength() is a cheap call.
> // When we use ACL CP or Visibility CP which deals with Tags during
> // mutation, the TagRewriteCell.getTagsLength() is a cheaper call. We do
> not
> // parse the byte[] to identify the tags length.
> if(e.getTagsLength() > 0) {
> tagsPresent = true;
> }
> setOldestEditTimeToNow();
> return b;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-14999) Remove ref to org.mortbay.log.Log
Anoop Sam John created HBASE-14999: -- Summary: Remove ref to org.mortbay.log.Log Key: HBASE-14999 URL: https://issues.apache.org/jira/browse/HBASE-14999 Project: HBase Issue Type: Bug Reporter: Anoop Sam John Assignee: Anoop Sam John I could see some 2 or 3 src files and many test files referring to org.mortbay.log.Log instead of commons Log. Patch correct all such places -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Successful: HBase Generate Website
Build status: Successful If successful, the website and docs have been generated. If failed, skip to the bottom of this email. Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If you prefer to keep the hbase-site repo around permanently, you can skip the clone step. git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git cd hbase-site wget -O- https://builds.apache.org/job/hbase_generate_website/68/artifact/website.patch.zip | funzip > 60d33ce34191533bb858852584bd9bddfeb16a23.patch git fetch git checkout -b asf-site-60d33ce34191533bb858852584bd9bddfeb16a23 origin/asf-site git am 60d33ce34191533bb858852584bd9bddfeb16a23.patch At this point, you can preview the changes by opening index.html or any of the other HTML pages in your local asf-site-60d33ce34191533bb858852584bd9bddfeb16a23 branch, and you can review the differences by running: git diff origin/asf-site When you are satisfied, publish your changes to origin/asf-site using this command: git push origin asf-site-60d33ce34191533bb858852584bd9bddfeb16a23:asf-site Changes take a couple of minutes to be propagated. You can then remove your asf-site-60d33ce34191533bb858852584bd9bddfeb16a23 branch: git checkout asf-site && git branch -d asf-site-60d33ce34191533bb858852584bd9bddfeb16a23 If failed, see https://builds.apache.org/job/hbase_generate_website/68/console
[jira] [Created] (HBASE-14993) aggregate post-commit feedback
Sean Busbey created HBASE-14993: --- Summary: aggregate post-commit feedback Key: HBASE-14993 URL: https://issues.apache.org/jira/browse/HBASE-14993 Project: HBase Issue Type: Improvement Components: build, tooling Reporter: Sean Busbey Given our current number of post-commit jobs and the regularity with which patches are going across 2-3 branches, it would be nice if we could get a fewer comments from the CI system with the results summarized rather than a comment per job as we do now. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-14992) Add cache stats of past n periods in region server status page
Jianwei Cui created HBASE-14992: --- Summary: Add cache stats of past n periods in region server status page Key: HBASE-14992 URL: https://issues.apache.org/jira/browse/HBASE-14992 Project: HBase Issue Type: Improvement Components: BlockCache, metrics Affects Versions: 2.0.0 Reporter: Jianwei Cui Priority: Minor The cache stats of past n periods, such as SumHitCountsPastNPeriods, SumHitCachingCountsPastNPeriods, etc, are useful to indicate the real-time read load of region server, especially for temporary read peak. It is helpful to add such metrics to BlockCache#Stats tab of region server status page. Discussion and suggestion are welcomed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
