[jira] [Commented] (HBASE-17780) BoundedByteBufferPool "At capacity" messages are not actionable
[
https://issues.apache.org/jira/browse/HBASE-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15926943#comment-15926943
]
stack commented on HBASE-17780:
---
+1
> BoundedByteBufferPool "At capacity" messages are not actionable
> ---
>
> Key: HBASE-17780
> URL: https://issues.apache.org/jira/browse/HBASE-17780
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 1.4.0, 1.1.9, 1.2.6, 1.31
>
> Attachments: HBASE-17780-branch-1.patch, HBASE-17780.patch
>
>
> This comment in BoundedByteBufferPool talks about "At capacity ..." warnings
> from this class that may appear in logs when under load:
> {code}
> * If a ByteBuffer is bigger than the configured threshold, we will just let
> the ByteBuffer go
> * rather than add it to the pool. If more ByteBuffers than the configured
> maximum instances,
> * we will not add the passed ByteBuffer to the pool; we will just drop it
> * (we will log a WARN in this case that we are at capacity).
> {code}
> First, dropping buffers when the pool is full is obviously an expected and
> normal condition. Second, there is nothing actionable about that warning.
> Might be useful for developers, perhaps. Drop it to DEBUG.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17780) BoundedByteBufferPool "At capacity" messages are not actionable
[
https://issues.apache.org/jira/browse/HBASE-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925450#comment-15925450
]
Hudson commented on HBASE-17780:
SUCCESS: Integrated in Jenkins build HBase-1.2-JDK7 #116 (See
[https://builds.apache.org/job/HBase-1.2-JDK7/116/])
HBASE-17780 BoundedByteBufferPool "At capacity" messages are not (apurtell: rev
17ef9fb15cca5f4075e90b78fdbcee7d0f80e238)
* (edit)
hbase-common/src/main/java/org/apache/hadoop/hbase/io/BoundedByteBufferPool.java
> BoundedByteBufferPool "At capacity" messages are not actionable
> ---
>
> Key: HBASE-17780
> URL: https://issues.apache.org/jira/browse/HBASE-17780
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 1.4.0, 1.1.9, 1.2.6, 1.31
>
> Attachments: HBASE-17780-branch-1.patch, HBASE-17780.patch
>
>
> This comment in BoundedByteBufferPool talks about "At capacity ..." warnings
> from this class that may appear in logs when under load:
> {code}
> * If a ByteBuffer is bigger than the configured threshold, we will just let
> the ByteBuffer go
> * rather than add it to the pool. If more ByteBuffers than the configured
> maximum instances,
> * we will not add the passed ByteBuffer to the pool; we will just drop it
> * (we will log a WARN in this case that we are at capacity).
> {code}
> First, dropping buffers when the pool is full is obviously an expected and
> normal condition. Second, there is nothing actionable about that warning.
> Might be useful for developers, perhaps. Drop it to DEBUG.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17780) BoundedByteBufferPool "At capacity" messages are not actionable
[
https://issues.apache.org/jira/browse/HBASE-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925426#comment-15925426
]
Hudson commented on HBASE-17780:
SUCCESS: Integrated in Jenkins build HBase-1.4 #671 (See
[https://builds.apache.org/job/HBase-1.4/671/])
HBASE-17780 BoundedByteBufferPool "At capacity" messages are not (apurtell: rev
d7666b60662cfc8492e396565b29494407c7843c)
* (edit)
hbase-common/src/main/java/org/apache/hadoop/hbase/io/BoundedByteBufferPool.java
> BoundedByteBufferPool "At capacity" messages are not actionable
> ---
>
> Key: HBASE-17780
> URL: https://issues.apache.org/jira/browse/HBASE-17780
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 1.4.0, 1.1.9, 1.2.6, 1.31
>
> Attachments: HBASE-17780-branch-1.patch, HBASE-17780.patch
>
>
> This comment in BoundedByteBufferPool talks about "At capacity ..." warnings
> from this class that may appear in logs when under load:
> {code}
> * If a ByteBuffer is bigger than the configured threshold, we will just let
> the ByteBuffer go
> * rather than add it to the pool. If more ByteBuffers than the configured
> maximum instances,
> * we will not add the passed ByteBuffer to the pool; we will just drop it
> * (we will log a WARN in this case that we are at capacity).
> {code}
> First, dropping buffers when the pool is full is obviously an expected and
> normal condition. Second, there is nothing actionable about that warning.
> Might be useful for developers, perhaps. Drop it to DEBUG.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17780) BoundedByteBufferPool "At capacity" messages are not actionable
[
https://issues.apache.org/jira/browse/HBASE-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925428#comment-15925428
]
Hudson commented on HBASE-17780:
SUCCESS: Integrated in Jenkins build HBase-1.2-JDK8 #111 (See
[https://builds.apache.org/job/HBase-1.2-JDK8/111/])
HBASE-17780 BoundedByteBufferPool "At capacity" messages are not (apurtell: rev
17ef9fb15cca5f4075e90b78fdbcee7d0f80e238)
* (edit)
hbase-common/src/main/java/org/apache/hadoop/hbase/io/BoundedByteBufferPool.java
> BoundedByteBufferPool "At capacity" messages are not actionable
> ---
>
> Key: HBASE-17780
> URL: https://issues.apache.org/jira/browse/HBASE-17780
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 1.4.0, 1.1.9, 1.2.6, 1.31
>
> Attachments: HBASE-17780-branch-1.patch, HBASE-17780.patch
>
>
> This comment in BoundedByteBufferPool talks about "At capacity ..." warnings
> from this class that may appear in logs when under load:
> {code}
> * If a ByteBuffer is bigger than the configured threshold, we will just let
> the ByteBuffer go
> * rather than add it to the pool. If more ByteBuffers than the configured
> maximum instances,
> * we will not add the passed ByteBuffer to the pool; we will just drop it
> * (we will log a WARN in this case that we are at capacity).
> {code}
> First, dropping buffers when the pool is full is obviously an expected and
> normal condition. Second, there is nothing actionable about that warning.
> Might be useful for developers, perhaps. Drop it to DEBUG.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17780) BoundedByteBufferPool "At capacity" messages are not actionable
[
https://issues.apache.org/jira/browse/HBASE-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925390#comment-15925390
]
Hudson commented on HBASE-17780:
SUCCESS: Integrated in Jenkins build HBase-1.3-JDK8 #136 (See
[https://builds.apache.org/job/HBase-1.3-JDK8/136/])
HBASE-17780 BoundedByteBufferPool "At capacity" messages are not (apurtell: rev
48cbce7ce07a795786d2240f55577a7aeaf041cc)
* (edit)
hbase-common/src/main/java/org/apache/hadoop/hbase/io/BoundedByteBufferPool.java
> BoundedByteBufferPool "At capacity" messages are not actionable
> ---
>
> Key: HBASE-17780
> URL: https://issues.apache.org/jira/browse/HBASE-17780
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 1.4.0, 1.1.9, 1.2.6, 1.31
>
> Attachments: HBASE-17780-branch-1.patch, HBASE-17780.patch
>
>
> This comment in BoundedByteBufferPool talks about "At capacity ..." warnings
> from this class that may appear in logs when under load:
> {code}
> * If a ByteBuffer is bigger than the configured threshold, we will just let
> the ByteBuffer go
> * rather than add it to the pool. If more ByteBuffers than the configured
> maximum instances,
> * we will not add the passed ByteBuffer to the pool; we will just drop it
> * (we will log a WARN in this case that we are at capacity).
> {code}
> First, dropping buffers when the pool is full is obviously an expected and
> normal condition. Second, there is nothing actionable about that warning.
> Might be useful for developers, perhaps. Drop it to DEBUG.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17780) BoundedByteBufferPool "At capacity" messages are not actionable
[
https://issues.apache.org/jira/browse/HBASE-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925289#comment-15925289
]
Hudson commented on HBASE-17780:
SUCCESS: Integrated in Jenkins build HBase-1.1-JDK7 #1854 (See
[https://builds.apache.org/job/HBase-1.1-JDK7/1854/])
HBASE-17780 BoundedByteBufferPool "At capacity" messages are not (apurtell: rev
3ced5e4c5e64b18519aa99d950ac2c0599e49b1f)
* (edit)
hbase-common/src/main/java/org/apache/hadoop/hbase/io/BoundedByteBufferPool.java
> BoundedByteBufferPool "At capacity" messages are not actionable
> ---
>
> Key: HBASE-17780
> URL: https://issues.apache.org/jira/browse/HBASE-17780
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 1.4.0, 1.1.9, 1.2.6, 1.31
>
> Attachments: HBASE-17780-branch-1.patch, HBASE-17780.patch
>
>
> This comment in BoundedByteBufferPool talks about "At capacity ..." warnings
> from this class that may appear in logs when under load:
> {code}
> * If a ByteBuffer is bigger than the configured threshold, we will just let
> the ByteBuffer go
> * rather than add it to the pool. If more ByteBuffers than the configured
> maximum instances,
> * we will not add the passed ByteBuffer to the pool; we will just drop it
> * (we will log a WARN in this case that we are at capacity).
> {code}
> First, dropping buffers when the pool is full is obviously an expected and
> normal condition. Second, there is nothing actionable about that warning.
> Might be useful for developers, perhaps. Drop it to DEBUG.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17780) BoundedByteBufferPool "At capacity" messages are not actionable
[
https://issues.apache.org/jira/browse/HBASE-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925288#comment-15925288
]
Hudson commented on HBASE-17780:
SUCCESS: Integrated in Jenkins build HBase-1.3-JDK7 #126 (See
[https://builds.apache.org/job/HBase-1.3-JDK7/126/])
HBASE-17780 BoundedByteBufferPool "At capacity" messages are not (apurtell: rev
48cbce7ce07a795786d2240f55577a7aeaf041cc)
* (edit)
hbase-common/src/main/java/org/apache/hadoop/hbase/io/BoundedByteBufferPool.java
> BoundedByteBufferPool "At capacity" messages are not actionable
> ---
>
> Key: HBASE-17780
> URL: https://issues.apache.org/jira/browse/HBASE-17780
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 1.4.0, 1.1.9, 1.2.6, 1.31
>
> Attachments: HBASE-17780-branch-1.patch, HBASE-17780.patch
>
>
> This comment in BoundedByteBufferPool talks about "At capacity ..." warnings
> from this class that may appear in logs when under load:
> {code}
> * If a ByteBuffer is bigger than the configured threshold, we will just let
> the ByteBuffer go
> * rather than add it to the pool. If more ByteBuffers than the configured
> maximum instances,
> * we will not add the passed ByteBuffer to the pool; we will just drop it
> * (we will log a WARN in this case that we are at capacity).
> {code}
> First, dropping buffers when the pool is full is obviously an expected and
> normal condition. Second, there is nothing actionable about that warning.
> Might be useful for developers, perhaps. Drop it to DEBUG.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17780) BoundedByteBufferPool "At capacity" messages are not actionable
[
https://issues.apache.org/jira/browse/HBASE-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925283#comment-15925283
]
Hudson commented on HBASE-17780:
SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #2673 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/2673/])
HBASE-17780 BoundedByteBufferPool "At capacity" messages are not (apurtell: rev
14fb57cab2fd8c0117d59669018b09e29bd6e387)
* (edit)
hbase-common/src/main/java/org/apache/hadoop/hbase/io/BoundedByteBufferPool.java
> BoundedByteBufferPool "At capacity" messages are not actionable
> ---
>
> Key: HBASE-17780
> URL: https://issues.apache.org/jira/browse/HBASE-17780
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 1.4.0, 1.1.9, 1.2.6, 1.31
>
> Attachments: HBASE-17780-branch-1.patch, HBASE-17780.patch
>
>
> This comment in BoundedByteBufferPool talks about "At capacity ..." warnings
> from this class that may appear in logs when under load:
> {code}
> * If a ByteBuffer is bigger than the configured threshold, we will just let
> the ByteBuffer go
> * rather than add it to the pool. If more ByteBuffers than the configured
> maximum instances,
> * we will not add the passed ByteBuffer to the pool; we will just drop it
> * (we will log a WARN in this case that we are at capacity).
> {code}
> First, dropping buffers when the pool is full is obviously an expected and
> normal condition. Second, there is nothing actionable about that warning.
> Might be useful for developers, perhaps. Drop it to DEBUG.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17780) BoundedByteBufferPool "At capacity" messages are not actionable
[
https://issues.apache.org/jira/browse/HBASE-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925262#comment-15925262
]
Hudson commented on HBASE-17780:
SUCCESS: Integrated in Jenkins build HBase-1.2-IT #849 (See
[https://builds.apache.org/job/HBase-1.2-IT/849/])
HBASE-17780 BoundedByteBufferPool "At capacity" messages are not (apurtell: rev
17ef9fb15cca5f4075e90b78fdbcee7d0f80e238)
* (edit)
hbase-common/src/main/java/org/apache/hadoop/hbase/io/BoundedByteBufferPool.java
> BoundedByteBufferPool "At capacity" messages are not actionable
> ---
>
> Key: HBASE-17780
> URL: https://issues.apache.org/jira/browse/HBASE-17780
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 1.4.0, 1.1.9, 1.2.6, 1.31
>
> Attachments: HBASE-17780-branch-1.patch, HBASE-17780.patch
>
>
> This comment in BoundedByteBufferPool talks about "At capacity ..." warnings
> from this class that may appear in logs when under load:
> {code}
> * If a ByteBuffer is bigger than the configured threshold, we will just let
> the ByteBuffer go
> * rather than add it to the pool. If more ByteBuffers than the configured
> maximum instances,
> * we will not add the passed ByteBuffer to the pool; we will just drop it
> * (we will log a WARN in this case that we are at capacity).
> {code}
> First, dropping buffers when the pool is full is obviously an expected and
> normal condition. Second, there is nothing actionable about that warning.
> Might be useful for developers, perhaps. Drop it to DEBUG.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17780) BoundedByteBufferPool "At capacity" messages are not actionable
[
https://issues.apache.org/jira/browse/HBASE-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925217#comment-15925217
]
Hudson commented on HBASE-17780:
FAILURE: Integrated in Jenkins build HBase-1.1-JDK8 #1938 (See
[https://builds.apache.org/job/HBase-1.1-JDK8/1938/])
HBASE-17780 BoundedByteBufferPool "At capacity" messages are not (apurtell: rev
3ced5e4c5e64b18519aa99d950ac2c0599e49b1f)
* (edit)
hbase-common/src/main/java/org/apache/hadoop/hbase/io/BoundedByteBufferPool.java
> BoundedByteBufferPool "At capacity" messages are not actionable
> ---
>
> Key: HBASE-17780
> URL: https://issues.apache.org/jira/browse/HBASE-17780
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 1.4.0, 1.1.9, 1.2.6, 1.31
>
> Attachments: HBASE-17780-branch-1.patch, HBASE-17780.patch
>
>
> This comment in BoundedByteBufferPool talks about "At capacity ..." warnings
> from this class that may appear in logs when under load:
> {code}
> * If a ByteBuffer is bigger than the configured threshold, we will just let
> the ByteBuffer go
> * rather than add it to the pool. If more ByteBuffers than the configured
> maximum instances,
> * we will not add the passed ByteBuffer to the pool; we will just drop it
> * (we will log a WARN in this case that we are at capacity).
> {code}
> First, dropping buffers when the pool is full is obviously an expected and
> normal condition. Second, there is nothing actionable about that warning.
> Might be useful for developers, perhaps. Drop it to DEBUG.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17780) BoundedByteBufferPool "At capacity" messages are not actionable
[
https://issues.apache.org/jira/browse/HBASE-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925201#comment-15925201
]
Hudson commented on HBASE-17780:
SUCCESS: Integrated in Jenkins build HBase-1.3-IT #8 (See
[https://builds.apache.org/job/HBase-1.3-IT/8/])
HBASE-17780 BoundedByteBufferPool "At capacity" messages are not (apurtell: rev
48cbce7ce07a795786d2240f55577a7aeaf041cc)
* (edit)
hbase-common/src/main/java/org/apache/hadoop/hbase/io/BoundedByteBufferPool.java
> BoundedByteBufferPool "At capacity" messages are not actionable
> ---
>
> Key: HBASE-17780
> URL: https://issues.apache.org/jira/browse/HBASE-17780
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 1.4.0, 1.1.9, 1.2.6, 1.31
>
> Attachments: HBASE-17780-branch-1.patch, HBASE-17780.patch
>
>
> This comment in BoundedByteBufferPool talks about "At capacity ..." warnings
> from this class that may appear in logs when under load:
> {code}
> * If a ByteBuffer is bigger than the configured threshold, we will just let
> the ByteBuffer go
> * rather than add it to the pool. If more ByteBuffers than the configured
> maximum instances,
> * we will not add the passed ByteBuffer to the pool; we will just drop it
> * (we will log a WARN in this case that we are at capacity).
> {code}
> First, dropping buffers when the pool is full is obviously an expected and
> normal condition. Second, there is nothing actionable about that warning.
> Might be useful for developers, perhaps. Drop it to DEBUG.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17780) BoundedByteBufferPool "At capacity" messages are not actionable
[
https://issues.apache.org/jira/browse/HBASE-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15924599#comment-15924599
]
Andrew Purtell commented on HBASE-17780:
Going to commit trivial patch later today unless objection
> BoundedByteBufferPool "At capacity" messages are not actionable
> ---
>
> Key: HBASE-17780
> URL: https://issues.apache.org/jira/browse/HBASE-17780
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 1.4.0, 1.31
>
> Attachments: HBASE-17780-branch-1.patch, HBASE-17780.patch
>
>
> This comment in BoundedByteBufferPool talks about "At capacity ..." warnings
> from this class that may appear in logs when under load:
> {code}
> * If a ByteBuffer is bigger than the configured threshold, we will just let
> the ByteBuffer go
> * rather than add it to the pool. If more ByteBuffers than the configured
> maximum instances,
> * we will not add the passed ByteBuffer to the pool; we will just drop it
> * (we will log a WARN in this case that we are at capacity).
> {code}
> First, dropping buffers when the pool is full is obviously an expected and
> normal condition. Second, there is nothing actionable about that warning.
> Might be useful for developers, perhaps. Drop it to DEBUG.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (HBASE-17780) BoundedByteBufferPool "At capacity" messages are not actionable
[
https://issues.apache.org/jira/browse/HBASE-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923334#comment-15923334
]
Hadoop QA commented on HBASE-17780:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 18s
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
38s {color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 14s
{color} | {color:green} branch-1 passed with JDK v1.8.0_121 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 16s
{color} | {color:green} branch-1 passed with JDK v1.7.0_80 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
21s {color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
12s {color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
42s {color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 12s
{color} | {color:green} branch-1 passed with JDK v1.8.0_121 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 18s
{color} | {color:green} branch-1 passed with JDK v1.7.0_80 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
18s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 13s
{color} | {color:green} the patch passed with JDK v1.8.0_121 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 13s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 16s
{color} | {color:green} the patch passed with JDK v1.7.0_80 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 16s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
22s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
11s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
14m 12s {color} | {color:green} The patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green} 0m
11s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
53s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 13s
{color} | {color:green} the patch passed with JDK v1.8.0_121 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 18s
{color} | {color:green} the patch passed with JDK v1.7.0_80 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 50s
{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
8s {color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 23m 45s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:e01ee2f |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12858584/HBASE-17780-branch-1.patch
|
| JIRA Issue | HBASE-17780 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux a0f9a39db501 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12
13:48:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/hbase.sh |
| git revision | branch-1 /
[jira] [Commented] (HBASE-17780) BoundedByteBufferPool "At capacity" messages are not actionable
[
https://issues.apache.org/jira/browse/HBASE-17780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923210#comment-15923210
]
Andrew Purtell commented on HBASE-17780:
Trivial patch
> BoundedByteBufferPool "At capacity" messages are not actionable
> ---
>
> Key: HBASE-17780
> URL: https://issues.apache.org/jira/browse/HBASE-17780
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.3.0
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 2.0.0, 1.4.0, 1.31
>
> Attachments: HBASE-17780-branch-1.patch, HBASE-17780.patch
>
>
> This comment in BoundedByteBufferPool talks about "At capacity ..." warnings
> from this class that may appear in logs when under load:
> {code}
> * If a ByteBuffer is bigger than the configured threshold, we will just let
> the ByteBuffer go
> * rather than add it to the pool. If more ByteBuffers than the configured
> maximum instances,
> * we will not add the passed ByteBuffer to the pool; we will just drop it
> * (we will log a WARN in this case that we are at capacity).
> {code}
> First, dropping buffers when the pool is full is obviously an expected and
> normal condition. Second, there is nothing actionable about that warning.
> Might be useful for developers, perhaps. Drop it to DEBUG.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
