[jira] [Commented] (HBASE-13706) CoprocessorClassLoader should not exempt Hive classes
[ https://issues.apache.org/jira/browse/HBASE-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14663300#comment-14663300 ] Hudson commented on HBASE-13706: FAILURE: Integrated in HBase-1.3 #97 (See [https://builds.apache.org/job/HBase-1.3/97/]) HBASE-13706 CoprocessorClassLoader should not exempt Hive classes (jerryjch: rev d322ebadf5cf8ab16cf3e4489188ced54a38ef0e) * hbase-common/src/main/java/org/apache/hadoop/hbase/util/CoprocessorClassLoader.java CoprocessorClassLoader should not exempt Hive classes - Key: HBASE-13706 URL: https://issues.apache.org/jira/browse/HBASE-13706 Project: HBase Issue Type: Bug Components: Coprocessors Affects Versions: 2.0.0, 1.0.1, 1.1.0, 0.98.12 Reporter: Jerry He Assignee: Jerry He Priority: Minor Fix For: 2.0.0, 1.2.0, 1.3.0 Attachments: HBASE-13706-branch-1.patch, HBASE-13706-master-v2.patch, HBASE-13706-master-v2.patch, HBASE-13706.patch CoprocessorClassLoader is used to load classes from the coprocessor jar. Certain classes are exempt from being loaded by this ClassLoader, which means they will be ignored in the coprocessor jar, but loaded from parent classpath instead. One problem is that we categorically exempt org.apache.hadoop. But it happens that Hive packages start with org.apache.hadoop. There is no reason to exclude hive classes from theCoprocessorClassLoader. HBase does not even include Hive jars. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13706) CoprocessorClassLoader should not exempt Hive classes
[ https://issues.apache.org/jira/browse/HBASE-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14663305#comment-14663305 ] Hudson commented on HBASE-13706: FAILURE: Integrated in HBase-1.2 #98 (See [https://builds.apache.org/job/HBase-1.2/98/]) HBASE-13706 CoprocessorClassLoader should not exempt Hive classes (jerryjch: rev a4c08f63045b2ccc983a6fb45614d09f7b47c3bc) * hbase-common/src/main/java/org/apache/hadoop/hbase/util/CoprocessorClassLoader.java CoprocessorClassLoader should not exempt Hive classes - Key: HBASE-13706 URL: https://issues.apache.org/jira/browse/HBASE-13706 Project: HBase Issue Type: Bug Components: Coprocessors Affects Versions: 2.0.0, 1.0.1, 1.1.0, 0.98.12 Reporter: Jerry He Assignee: Jerry He Priority: Minor Fix For: 2.0.0, 1.2.0, 1.3.0 Attachments: HBASE-13706-branch-1.patch, HBASE-13706-master-v2.patch, HBASE-13706-master-v2.patch, HBASE-13706.patch CoprocessorClassLoader is used to load classes from the coprocessor jar. Certain classes are exempt from being loaded by this ClassLoader, which means they will be ignored in the coprocessor jar, but loaded from parent classpath instead. One problem is that we categorically exempt org.apache.hadoop. But it happens that Hive packages start with org.apache.hadoop. There is no reason to exclude hive classes from theCoprocessorClassLoader. HBase does not even include Hive jars. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13706) CoprocessorClassLoader should not exempt Hive classes
[ https://issues.apache.org/jira/browse/HBASE-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14669879#comment-14669879 ] Hudson commented on HBASE-13706: SUCCESS: Integrated in HBase-1.2-IT #81 (See [https://builds.apache.org/job/HBase-1.2-IT/81/]) HBASE-13706 CoprocessorClassLoader should not exempt Hive classes (jerryjch: rev a4c08f63045b2ccc983a6fb45614d09f7b47c3bc) * hbase-common/src/main/java/org/apache/hadoop/hbase/util/CoprocessorClassLoader.java CoprocessorClassLoader should not exempt Hive classes - Key: HBASE-13706 URL: https://issues.apache.org/jira/browse/HBASE-13706 Project: HBase Issue Type: Bug Components: Coprocessors Affects Versions: 2.0.0, 1.0.1, 1.1.0, 0.98.12 Reporter: Jerry He Assignee: Jerry He Priority: Minor Fix For: 2.0.0, 1.2.0, 1.3.0 Attachments: HBASE-13706-branch-1.patch, HBASE-13706-master-v2.patch, HBASE-13706-master-v2.patch, HBASE-13706.patch CoprocessorClassLoader is used to load classes from the coprocessor jar. Certain classes are exempt from being loaded by this ClassLoader, which means they will be ignored in the coprocessor jar, but loaded from parent classpath instead. One problem is that we categorically exempt org.apache.hadoop. But it happens that Hive packages start with org.apache.hadoop. There is no reason to exclude hive classes from theCoprocessorClassLoader. HBase does not even include Hive jars. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13706) CoprocessorClassLoader should not exempt Hive classes
[ https://issues.apache.org/jira/browse/HBASE-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14669882#comment-14669882 ] Hudson commented on HBASE-13706: SUCCESS: Integrated in HBase-1.3-IT #79 (See [https://builds.apache.org/job/HBase-1.3-IT/79/]) HBASE-13706 CoprocessorClassLoader should not exempt Hive classes (jerryjch: rev d322ebadf5cf8ab16cf3e4489188ced54a38ef0e) * hbase-common/src/main/java/org/apache/hadoop/hbase/util/CoprocessorClassLoader.java CoprocessorClassLoader should not exempt Hive classes - Key: HBASE-13706 URL: https://issues.apache.org/jira/browse/HBASE-13706 Project: HBase Issue Type: Bug Components: Coprocessors Affects Versions: 2.0.0, 1.0.1, 1.1.0, 0.98.12 Reporter: Jerry He Assignee: Jerry He Priority: Minor Fix For: 2.0.0, 1.2.0, 1.3.0 Attachments: HBASE-13706-branch-1.patch, HBASE-13706-master-v2.patch, HBASE-13706-master-v2.patch, HBASE-13706.patch CoprocessorClassLoader is used to load classes from the coprocessor jar. Certain classes are exempt from being loaded by this ClassLoader, which means they will be ignored in the coprocessor jar, but loaded from parent classpath instead. One problem is that we categorically exempt org.apache.hadoop. But it happens that Hive packages start with org.apache.hadoop. There is no reason to exclude hive classes from theCoprocessorClassLoader. HBase does not even include Hive jars. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13924) Description for hbase.dynamic.jars.dir is wrong
[
https://issues.apache.org/jira/browse/HBASE-13924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-13924:
Status: Patch Available (was: In Progress)
Ready for review.
Description for hbase.dynamic.jars.dir is wrong
---
Key: HBASE-13924
URL: https://issues.apache.org/jira/browse/HBASE-13924
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0.1
Reporter: Lars George
Assignee: Misty Stanley-Jones
Labels: beginner
Fix For: 2.0.0, 1.3.0
Attachments: HBASE-13924.patch
The description in the following is wrong:
{noformat}
property
namehbase.dynamic.jars.dir/name
value${hbase.rootdir}/lib/value
description
The directory from which the custom filter/co-processor jars can be
loaded
dynamically by the region server without the need to restart. However,
an already loaded filter/co-processor class would not be un-loaded. See
HBASE-1936 for more details.
/description
/property
{noformat}
The {{DynamicClassLoader}} is *not* used for coprocessors, but only for
filters, comparators, and exceptions. Fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13924) Description for hbase.dynamic.jars.dir is wrong
[
https://issues.apache.org/jira/browse/HBASE-13924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-13924:
Attachment: HBASE-13924.patch
Description for hbase.dynamic.jars.dir is wrong
---
Key: HBASE-13924
URL: https://issues.apache.org/jira/browse/HBASE-13924
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0.1
Reporter: Lars George
Assignee: Misty Stanley-Jones
Labels: beginner
Fix For: 2.0.0, 1.3.0
Attachments: HBASE-13924.patch
The description in the following is wrong:
{noformat}
property
namehbase.dynamic.jars.dir/name
value${hbase.rootdir}/lib/value
description
The directory from which the custom filter/co-processor jars can be
loaded
dynamically by the region server without the need to restart. However,
an already loaded filter/co-processor class would not be un-loaded. See
HBASE-1936 for more details.
/description
/property
{noformat}
The {{DynamicClassLoader}} is *not* used for coprocessors, but only for
filters, comparators, and exceptions. Fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (HBASE-13446) Add docs warning about missing data for downstream on versions prior to HBASE-13262
[
https://issues.apache.org/jira/browse/HBASE-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones reassigned HBASE-13446:
---
Assignee: Misty Stanley-Jones
Add docs warning about missing data for downstream on versions prior to
HBASE-13262
---
Key: HBASE-13446
URL: https://issues.apache.org/jira/browse/HBASE-13446
Project: HBase
Issue Type: Task
Components: documentation
Affects Versions: 0.98.0, 1.0.0
Reporter: Sean Busbey
Assignee: Misty Stanley-Jones
Priority: Critical
Fix For: 2.0.0, 0.98.14, 1.0.3
From conversation at the end of HBASE-13262:
[~davelatham]
{quote}
Should we put a warning somewhere (mailing list? book?) about this? Something
like:
IF (client OR server is = 0.98.11/1.0.0) AND server has a smaller value for
hbase.client.scanner.max.result.size than client does, THEN scan requests
that reach the server's hbase.client.scanner.max.result.size are likely to
miss data. In particular, 0.98.11 defaults
hbase.client.scanner.max.result.size to 2MB but other versions default to
larger values, so be very careful using 0.98.11 servers with any other client
version.
{quote}
[~busbey]
{quote}
How about we add a note in the ref guide for upgrades and for
troubleshooting?
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (HBASE-12615) Document GC conserving guidelines for contributors
[ https://issues.apache.org/jira/browse/HBASE-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones reassigned HBASE-12615: --- Assignee: Misty Stanley-Jones Document GC conserving guidelines for contributors -- Key: HBASE-12615 URL: https://issues.apache.org/jira/browse/HBASE-12615 Project: HBase Issue Type: Bug Components: documentation Reporter: Andrew Purtell Assignee: Misty Stanley-Jones LinkedIn put up a blog post with a nice concise list of GC conserving techniques we should document for contributors. Additionally, when we're at a point our build supports custom error-prone plugins, we can develop warnings for some of them. Source: http://engineering.linkedin.com/performance/linkedin-feed-faster-less-jvm-garbage - Be careful with Iterators - Estimate the size of a collection when initializing - Defer expression evaluation - Compile the regex patterns in advance - Cache it if you can - String Interns are useful but dangerous All good advice and practice that I know we aim for. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HBASE-12983) HBase book mentions hadoop.ssl.enabled when it should be hbase.ssl.enabled
[
https://issues.apache.org/jira/browse/HBASE-12983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones reassigned HBASE-12983:
---
Assignee: Misty Stanley-Jones
HBase book mentions hadoop.ssl.enabled when it should be hbase.ssl.enabled
--
Key: HBASE-12983
URL: https://issues.apache.org/jira/browse/HBASE-12983
Project: HBase
Issue Type: Bug
Components: documentation
Reporter: Esteban Gutierrez
Assignee: Misty Stanley-Jones
Attachments: HBASE-12983.patch
In the HBase book we say the following:
{quote}
A default HBase install uses insecure HTTP connections for web UIs for the
master and region servers. To enable secure HTTP (HTTPS) connections instead,
set *hadoop.ssl.enabled* to true in hbase-site.xml. This does not change the
port used by the Web UI. To change the port for the web UI for a given HBase
component, configure that port’s setting in hbase-site.xml. These settings
are:
{quote}
The property should be *hbase.ssl.enabled* instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12983) HBase book mentions hadoop.ssl.enabled when it should be hbase.ssl.enabled
[
https://issues.apache.org/jira/browse/HBASE-12983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-12983:
Attachment: HBASE-12983.patch
HBase book mentions hadoop.ssl.enabled when it should be hbase.ssl.enabled
--
Key: HBASE-12983
URL: https://issues.apache.org/jira/browse/HBASE-12983
Project: HBase
Issue Type: Bug
Components: documentation
Reporter: Esteban Gutierrez
Assignee: Misty Stanley-Jones
Attachments: HBASE-12983.patch
In the HBase book we say the following:
{quote}
A default HBase install uses insecure HTTP connections for web UIs for the
master and region servers. To enable secure HTTP (HTTPS) connections instead,
set *hadoop.ssl.enabled* to true in hbase-site.xml. This does not change the
port used by the Web UI. To change the port for the web UI for a given HBase
component, configure that port’s setting in hbase-site.xml. These settings
are:
{quote}
The property should be *hbase.ssl.enabled* instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12983) HBase book mentions hadoop.ssl.enabled when it should be hbase.ssl.enabled
[
https://issues.apache.org/jira/browse/HBASE-12983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-12983:
Status: Patch Available (was: Open)
HBase book mentions hadoop.ssl.enabled when it should be hbase.ssl.enabled
--
Key: HBASE-12983
URL: https://issues.apache.org/jira/browse/HBASE-12983
Project: HBase
Issue Type: Bug
Components: documentation
Reporter: Esteban Gutierrez
Assignee: Misty Stanley-Jones
Attachments: HBASE-12983.patch
In the HBase book we say the following:
{quote}
A default HBase install uses insecure HTTP connections for web UIs for the
master and region servers. To enable secure HTTP (HTTPS) connections instead,
set *hadoop.ssl.enabled* to true in hbase-site.xml. This does not change the
port used by the Web UI. To change the port for the web UI for a given HBase
component, configure that port’s setting in hbase-site.xml. These settings
are:
{quote}
The property should be *hbase.ssl.enabled* instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (HBASE-13483) [docs] onheap is not a valid bucket cache IO engine.
[
https://issues.apache.org/jira/browse/HBASE-13483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones reassigned HBASE-13483:
---
Assignee: Misty Stanley-Jones
[docs] onheap is not a valid bucket cache IO engine.
Key: HBASE-13483
URL: https://issues.apache.org/jira/browse/HBASE-13483
Project: HBase
Issue Type: Bug
Components: documentation
Affects Versions: 2.0.0
Reporter: Esteban Gutierrez
Assignee: Misty Stanley-Jones
From the HBase book:
http://hbase.apache.org/book.html#hbase_default_configurations
:
{code}
hbase.bucketcache.ioengine
Description
Where to store the contents of the bucketcache. One of: *onheap*, offheap, or
file. If a file, set it to file:PATH_TO_FILE. See
https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/io/hfile/CacheConfig.html
for more information.
{code}
Instead of onheap it should be heap.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13446) Add docs warning about missing data for downstream on versions prior to HBASE-13262
[
https://issues.apache.org/jira/browse/HBASE-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-13446:
Attachment: HBASE-13446.patch
Add docs warning about missing data for downstream on versions prior to
HBASE-13262
---
Key: HBASE-13446
URL: https://issues.apache.org/jira/browse/HBASE-13446
Project: HBase
Issue Type: Task
Components: documentation
Affects Versions: 0.98.0, 1.0.0
Reporter: Sean Busbey
Assignee: Misty Stanley-Jones
Priority: Critical
Fix For: 2.0.0, 0.98.14, 1.0.3
Attachments: HBASE-13446.patch
From conversation at the end of HBASE-13262:
[~davelatham]
{quote}
Should we put a warning somewhere (mailing list? book?) about this? Something
like:
IF (client OR server is = 0.98.11/1.0.0) AND server has a smaller value for
hbase.client.scanner.max.result.size than client does, THEN scan requests
that reach the server's hbase.client.scanner.max.result.size are likely to
miss data. In particular, 0.98.11 defaults
hbase.client.scanner.max.result.size to 2MB but other versions default to
larger values, so be very careful using 0.98.11 servers with any other client
version.
{quote}
[~busbey]
{quote}
How about we add a note in the ref guide for upgrades and for
troubleshooting?
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13446) Add docs warning about missing data for downstream on versions prior to HBASE-13262
[
https://issues.apache.org/jira/browse/HBASE-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-13446:
Status: Patch Available (was: Open)
Ready for review.
Add docs warning about missing data for downstream on versions prior to
HBASE-13262
---
Key: HBASE-13446
URL: https://issues.apache.org/jira/browse/HBASE-13446
Project: HBase
Issue Type: Task
Components: documentation
Affects Versions: 1.0.0, 0.98.0
Reporter: Sean Busbey
Assignee: Misty Stanley-Jones
Priority: Critical
Fix For: 2.0.0, 0.98.14, 1.0.3
Attachments: HBASE-13446.patch
From conversation at the end of HBASE-13262:
[~davelatham]
{quote}
Should we put a warning somewhere (mailing list? book?) about this? Something
like:
IF (client OR server is = 0.98.11/1.0.0) AND server has a smaller value for
hbase.client.scanner.max.result.size than client does, THEN scan requests
that reach the server's hbase.client.scanner.max.result.size are likely to
miss data. In particular, 0.98.11 defaults
hbase.client.scanner.max.result.size to 2MB but other versions default to
larger values, so be very careful using 0.98.11 servers with any other client
version.
{quote}
[~busbey]
{quote}
How about we add a note in the ref guide for upgrades and for
troubleshooting?
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12621) Explain in the book when KEEP_DELETED_CELLS is useful
[
https://issues.apache.org/jira/browse/HBASE-12621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679403#comment-14679403
]
Misty Stanley-Jones commented on HBASE-12621:
-
I'm not sure what could be done to make it more clear. See
http://hbase.apache.org/book.html#cf.keep.deleted. Maybe you can let me know
what you would change, or just go ahead and change it since you are probably
the one who understands it best. See
{{src/main/asciidoc/_chapters/schema_design.adoc}}.
Explain in the book when KEEP_DELETED_CELLS is useful
-
Key: HBASE-12621
URL: https://issues.apache.org/jira/browse/HBASE-12621
Project: HBase
Issue Type: Sub-task
Components: documentation
Reporter: Lars Hofhansl
Fix For: 2.0.0
KEEP_DELETED_CELLS seems to be very confusing.
The books need further clarification when this setting is useful and what the
implications are.
(and maybe we should discuss if there's a simpler way to achieve what I
intended to achieve with this when I implemented it first)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12615) Document GC conserving guidelines for contributors
[ https://issues.apache.org/jira/browse/HBASE-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-12615: Status: Patch Available (was: Open) Ready for review Document GC conserving guidelines for contributors -- Key: HBASE-12615 URL: https://issues.apache.org/jira/browse/HBASE-12615 Project: HBase Issue Type: Bug Components: documentation Reporter: Andrew Purtell Assignee: Misty Stanley-Jones Attachments: HBASE-12615.patch LinkedIn put up a blog post with a nice concise list of GC conserving techniques we should document for contributors. Additionally, when we're at a point our build supports custom error-prone plugins, we can develop warnings for some of them. Source: http://engineering.linkedin.com/performance/linkedin-feed-faster-less-jvm-garbage - Be careful with Iterators - Estimate the size of a collection when initializing - Defer expression evaluation - Compile the regex patterns in advance - Cache it if you can - String Interns are useful but dangerous All good advice and practice that I know we aim for. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12615) Document GC conserving guidelines for contributors
[ https://issues.apache.org/jira/browse/HBASE-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-12615: Attachment: HBASE-12615.patch Document GC conserving guidelines for contributors -- Key: HBASE-12615 URL: https://issues.apache.org/jira/browse/HBASE-12615 Project: HBase Issue Type: Bug Components: documentation Reporter: Andrew Purtell Assignee: Misty Stanley-Jones Attachments: HBASE-12615.patch LinkedIn put up a blog post with a nice concise list of GC conserving techniques we should document for contributors. Additionally, when we're at a point our build supports custom error-prone plugins, we can develop warnings for some of them. Source: http://engineering.linkedin.com/performance/linkedin-feed-faster-less-jvm-garbage - Be careful with Iterators - Estimate the size of a collection when initializing - Defer expression evaluation - Compile the regex patterns in advance - Cache it if you can - String Interns are useful but dangerous All good advice and practice that I know we aim for. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13483) [docs] onheap is not a valid bucket cache IO engine.
[
https://issues.apache.org/jira/browse/HBASE-13483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-13483:
Attachment: HBASE-13483.patch
[docs] onheap is not a valid bucket cache IO engine.
Key: HBASE-13483
URL: https://issues.apache.org/jira/browse/HBASE-13483
Project: HBase
Issue Type: Bug
Components: documentation
Affects Versions: 2.0.0
Reporter: Esteban Gutierrez
Assignee: Misty Stanley-Jones
Attachments: HBASE-13483.patch
From the HBase book:
http://hbase.apache.org/book.html#hbase_default_configurations
:
{code}
hbase.bucketcache.ioengine
Description
Where to store the contents of the bucketcache. One of: *onheap*, offheap, or
file. If a file, set it to file:PATH_TO_FILE. See
https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/io/hfile/CacheConfig.html
for more information.
{code}
Instead of onheap it should be heap.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13483) [docs] onheap is not a valid bucket cache IO engine.
[
https://issues.apache.org/jira/browse/HBASE-13483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-13483:
Status: Patch Available (was: Open)
[docs] onheap is not a valid bucket cache IO engine.
Key: HBASE-13483
URL: https://issues.apache.org/jira/browse/HBASE-13483
Project: HBase
Issue Type: Bug
Components: documentation
Affects Versions: 2.0.0
Reporter: Esteban Gutierrez
Assignee: Misty Stanley-Jones
Attachments: HBASE-13483.patch
From the HBase book:
http://hbase.apache.org/book.html#hbase_default_configurations
:
{code}
hbase.bucketcache.ioengine
Description
Where to store the contents of the bucketcache. One of: *onheap*, offheap, or
file. If a file, set it to file:PATH_TO_FILE. See
https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/io/hfile/CacheConfig.html
for more information.
{code}
Instead of onheap it should be heap.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (HBASE-13928) Correct doc bug introduced in HBASE-11735
[
https://issues.apache.org/jira/browse/HBASE-13928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones resolved HBASE-13928.
-
Resolution: Not A Problem
Correct doc bug introduced in HBASE-11735
-
Key: HBASE-13928
URL: https://issues.apache.org/jira/browse/HBASE-13928
Project: HBase
Issue Type: Task
Components: documentation
Affects Versions: 0.99.0, 0.98.4, 0.98.5
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
Fix For: 2.0.0, 0.98.6, 0.99.0
{quote}Biju Nair added a comment - 09/Jun/15 04:53
I think the parameter hbase.bucketcache.sizes is used in the document patch
instead of hbase.bucketcache.bucket.sizes to configure bucket sizes.
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13129) Add troubleshooting hints around WAL retention from replication
[ https://issues.apache.org/jira/browse/HBASE-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679400#comment-14679400 ] Misty Stanley-Jones commented on HBASE-13129: - Is this addressed by HBASE-14071? Add troubleshooting hints around WAL retention from replication --- Key: HBASE-13129 URL: https://issues.apache.org/jira/browse/HBASE-13129 Project: HBase Issue Type: Improvement Components: documentation, Replication Reporter: Sean Busbey Labels: operations, supportability There's been some confusion on the mailing list about when WALs get retained / cleaned up once replication is on at all in a cluster. (ref [this thread|http://mail-archives.apache.org/mod_mbox/hbase-user/201502.mbox/%3ccamuu0w9aovbo7kgulim9txrulirqs9fm-3ra3pqccypw_17...@mail.gmail.com%3E]) We should add a NOTE in the replication section that wals are saved across enable/disable so long as there are peers. There looks like there might also be some confusing language around replication being enabled in the configs vs the enable/disable suspension mechanism. We should also add a troubleshooting item specific for my HDFS space keeps growing and it's all in oldWALs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HBASE-13425) Documentation nit in REST Gateway impersonation section
[ https://issues.apache.org/jira/browse/HBASE-13425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones reassigned HBASE-13425: --- Assignee: Misty Stanley-Jones Documentation nit in REST Gateway impersonation section --- Key: HBASE-13425 URL: https://issues.apache.org/jira/browse/HBASE-13425 Project: HBase Issue Type: Improvement Components: documentation Affects Versions: 2.0.0 Reporter: Jeremie Gomez Assignee: Misty Stanley-Jones Priority: Minor Fix For: 2.0.0 In section 55.8. REST Gateway Impersonation Configuration, there is another property that needs to be set (and thus documented). After this sentence (To enable REST gateway impersonation, add the following to the hbase-site.xml file for every REST gateway.), we should add : property namehbase.rest.support.proxyuser/name valuetrue/value /property It not set, doing a curl call on the rest gateway gives the error support for proxyuser is not configured. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13425) Documentation nit in REST Gateway impersonation section
[ https://issues.apache.org/jira/browse/HBASE-13425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-13425: Status: Patch Available (was: Open) Documentation nit in REST Gateway impersonation section --- Key: HBASE-13425 URL: https://issues.apache.org/jira/browse/HBASE-13425 Project: HBase Issue Type: Improvement Components: documentation Affects Versions: 2.0.0 Reporter: Jeremie Gomez Assignee: Misty Stanley-Jones Priority: Minor Fix For: 2.0.0 Attachments: HBASE-13425.patch In section 55.8. REST Gateway Impersonation Configuration, there is another property that needs to be set (and thus documented). After this sentence (To enable REST gateway impersonation, add the following to the hbase-site.xml file for every REST gateway.), we should add : property namehbase.rest.support.proxyuser/name valuetrue/value /property It not set, doing a curl call on the rest gateway gives the error support for proxyuser is not configured. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14071) Document troubleshooting unexpected filesystem usage by snapshots and WALs
[ https://issues.apache.org/jira/browse/HBASE-14071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-14071: Status: Patch Available (was: Open) Ready for review. Perhaps [~busbey] and [~mbertozzi] can take a look. Document troubleshooting unexpected filesystem usage by snapshots and WALs -- Key: HBASE-14071 URL: https://issues.apache.org/jira/browse/HBASE-14071 Project: HBase Issue Type: Task Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Attachments: HBASE-14071.patch Document how to troubleshoot things like unexpected snapshot and WAL growth on the filesystem -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13867) Add endpoint coprocessor guide to HBase book
[ https://issues.apache.org/jira/browse/HBASE-13867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679378#comment-14679378 ] Misty Stanley-Jones commented on HBASE-13867: - [~gbhardwaj], can you put this into a Google doc? I'd like to collaborate together on it, if that is OK with you. The technical content is good, but I think we can work together to make it a bit easier to understand. If you are open to that, just put the link to the Google doc here or email it to me (misty at apache). Thanks! Add endpoint coprocessor guide to HBase book Key: HBASE-13867 URL: https://issues.apache.org/jira/browse/HBASE-13867 Project: HBase Issue Type: Task Components: Coprocessors, documentation Reporter: Vladimir Rodionov Assignee: Gaurav Bhardwaj Fix For: 2.0.0 Attachments: HBASE-13867.1.patch, HBASE-13867.2.patch, HBASE-13867.2.patch Endpoint coprocessors are very poorly documented. Coprocessor section of HBase book must be updated either with its own endpoint coprocessors HOW-TO guide or, at least, with the link(s) to some other guides. There is good description here: http://www.3pillarglobal.com/insights/hbase-coprocessors -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14071) Document troubleshooting unexpected filesystem usage by snapshots and WALs
[ https://issues.apache.org/jira/browse/HBASE-14071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-14071: Attachment: HBASE-14071.patch Document troubleshooting unexpected filesystem usage by snapshots and WALs -- Key: HBASE-14071 URL: https://issues.apache.org/jira/browse/HBASE-14071 Project: HBase Issue Type: Task Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Attachments: HBASE-14071.patch Document how to troubleshoot things like unexpected snapshot and WAL growth on the filesystem -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14071) ocument troubleshooting unexpected filesystem usage by snapshots and WALs
[ https://issues.apache.org/jira/browse/HBASE-14071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-14071: Summary: ocument troubleshooting unexpected filesystem usage by snapshots and WALs (was: Document HBase directory layout for troubleshooting purposes) ocument troubleshooting unexpected filesystem usage by snapshots and WALs - Key: HBASE-14071 URL: https://issues.apache.org/jira/browse/HBASE-14071 Project: HBase Issue Type: Task Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Document how to troubleshoot things like unexpected snapshot and WAL growth on the filesystem -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14071) Document troubleshooting unexpected filesystem usage by snapshots and WALs
[ https://issues.apache.org/jira/browse/HBASE-14071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-14071: Summary: Document troubleshooting unexpected filesystem usage by snapshots and WALs (was: ocument troubleshooting unexpected filesystem usage by snapshots and WALs) Document troubleshooting unexpected filesystem usage by snapshots and WALs -- Key: HBASE-14071 URL: https://issues.apache.org/jira/browse/HBASE-14071 Project: HBase Issue Type: Task Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Document how to troubleshoot things like unexpected snapshot and WAL growth on the filesystem -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13907) Document how to deploy a coprocessor
[ https://issues.apache.org/jira/browse/HBASE-13907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679382#comment-14679382 ] Misty Stanley-Jones commented on HBASE-13907: - For point #1, I do not know the answer. I can reiterate that it's not a clean approach and is not recommended. For point #2, I think I will just take out the second sentence altogether. For point #3, I do not know the answer and need input from someone who knows more (maybe [~larsgeorge]?) Document how to deploy a coprocessor Key: HBASE-13907 URL: https://issues.apache.org/jira/browse/HBASE-13907 Project: HBase Issue Type: Bug Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Attachments: HBASE-13907-1.patch, HBASE-13907-2.patch, HBASE-13907.patch Capture this information: Where are the dependencies located for these classes? Is there a path on HDFS or local disk that dependencies need to be placed so that each RegionServer has access to them? It is suggested to bundle them as a single jar so that RS can load the whole jar and resolve dependencies. If you are not able to do that, you need place the dependencies in regionservers class path so that they are loaded during RS startup. Do either of these options work for you? Btw, you can load the coprocessors/filters into path specified by hbase.dynamic.jars.dir [1], so that they are loaded dynamically by regionservers when the class is accessed (or you can place them in the RS class path too, so that they are loaded during RS JVM startup). How would one deploy these using an automated system? (puppet/chef/ansible/etc) You can probably use these tools to automate shipping the jars to above locations? Tests our developers have done suggest that simply disabling a coprocessor, replacing the jar with a different version, and enabling the coprocessor again does not load the newest version. With that in mind how does one know which version is currently deployed and enabled without resorting to parsing `hbase shell` output or restarting hbase? Actually this is a design issue with current classloader. You can't reload a class in a JVM unless you delete all the current references to it. Since the current JVM (classloader) has reference to it, you can't overwrite it unless you kill the JVM, which is equivalent to restarting it. So you still have the older class loaded in place. For this to work, classloader design should be changed. If it works for you, you can rename the coprocessor class name and the new version of jar and RS loads it properly. Where does logging go, and how does one access it? Does logging need to be configured in a certain way? Can you please specify which logging you are referring to? Where is a good location to place configuration files? Same as above, are these hbase configs or something else? If hbase configs, are these gateway configs/server side? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13907) Document how to deploy a coprocessor
[ https://issues.apache.org/jira/browse/HBASE-13907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679381#comment-14679381 ] Misty Stanley-Jones commented on HBASE-13907: - For point #1, I do not know the answer. I can reiterate that it's not a clean approach and is not recommended. For point #2, I think I will just take out the second sentence altogether. For point #3, I do not know the answer and need input from someone who knows more (maybe [~larsgeorge]?) Document how to deploy a coprocessor Key: HBASE-13907 URL: https://issues.apache.org/jira/browse/HBASE-13907 Project: HBase Issue Type: Bug Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Attachments: HBASE-13907-1.patch, HBASE-13907-2.patch, HBASE-13907.patch Capture this information: Where are the dependencies located for these classes? Is there a path on HDFS or local disk that dependencies need to be placed so that each RegionServer has access to them? It is suggested to bundle them as a single jar so that RS can load the whole jar and resolve dependencies. If you are not able to do that, you need place the dependencies in regionservers class path so that they are loaded during RS startup. Do either of these options work for you? Btw, you can load the coprocessors/filters into path specified by hbase.dynamic.jars.dir [1], so that they are loaded dynamically by regionservers when the class is accessed (or you can place them in the RS class path too, so that they are loaded during RS JVM startup). How would one deploy these using an automated system? (puppet/chef/ansible/etc) You can probably use these tools to automate shipping the jars to above locations? Tests our developers have done suggest that simply disabling a coprocessor, replacing the jar with a different version, and enabling the coprocessor again does not load the newest version. With that in mind how does one know which version is currently deployed and enabled without resorting to parsing `hbase shell` output or restarting hbase? Actually this is a design issue with current classloader. You can't reload a class in a JVM unless you delete all the current references to it. Since the current JVM (classloader) has reference to it, you can't overwrite it unless you kill the JVM, which is equivalent to restarting it. So you still have the older class loaded in place. For this to work, classloader design should be changed. If it works for you, you can rename the coprocessor class name and the new version of jar and RS loads it properly. Where does logging go, and how does one access it? Does logging need to be configured in a certain way? Can you please specify which logging you are referring to? Where is a good location to place configuration files? Same as above, are these hbase configs or something else? If hbase configs, are these gateway configs/server side? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (HBASE-13924) Description for hbase.dynamic.jars.dir is wrong
[
https://issues.apache.org/jira/browse/HBASE-13924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HBASE-13924 started by Misty Stanley-Jones.
---
Description for hbase.dynamic.jars.dir is wrong
---
Key: HBASE-13924
URL: https://issues.apache.org/jira/browse/HBASE-13924
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0.1
Reporter: Lars George
Assignee: Misty Stanley-Jones
Labels: beginner
Fix For: 2.0.0, 1.3.0
The description in the following is wrong:
{noformat}
property
namehbase.dynamic.jars.dir/name
value${hbase.rootdir}/lib/value
description
The directory from which the custom filter/co-processor jars can be
loaded
dynamically by the region server without the need to restart. However,
an already loaded filter/co-processor class would not be un-loaded. See
HBASE-1936 for more details.
/description
/property
{noformat}
The {{DynamicClassLoader}} is *not* used for coprocessors, but only for
filters, comparators, and exceptions. Fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13425) Documentation nit in REST Gateway impersonation section
[ https://issues.apache.org/jira/browse/HBASE-13425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-13425: Attachment: HBASE-13425.patch Documentation nit in REST Gateway impersonation section --- Key: HBASE-13425 URL: https://issues.apache.org/jira/browse/HBASE-13425 Project: HBase Issue Type: Improvement Components: documentation Affects Versions: 2.0.0 Reporter: Jeremie Gomez Assignee: Misty Stanley-Jones Priority: Minor Fix For: 2.0.0 Attachments: HBASE-13425.patch In section 55.8. REST Gateway Impersonation Configuration, there is another property that needs to be set (and thus documented). After this sentence (To enable REST gateway impersonation, add the following to the hbase-site.xml file for every REST gateway.), we should add : property namehbase.rest.support.proxyuser/name valuetrue/value /property It not set, doing a curl call on the rest gateway gives the error support for proxyuser is not configured. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12396) Document suggested use of log levels in dev guide
[ https://issues.apache.org/jira/browse/HBASE-12396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679473#comment-14679473 ] Misty Stanley-Jones commented on HBASE-12396: - I was thinking of taking this, but I think at least the first draft needs to be done by developers. Document suggested use of log levels in dev guide - Key: HBASE-12396 URL: https://issues.apache.org/jira/browse/HBASE-12396 Project: HBase Issue Type: Improvement Components: documentation Reporter: Sean Busbey Priority: Minor Right now we don't provide any guidance on appropriate use of log levels, which leads to inconsistent use and in some cases exacerbating problems for tests and troubleshooting (see HBASE-12395). We should add a section on suggested use of log levels to the guide. Some related reading * [a good ops-focused blog post on levels|http://watchitlater.com/blog/2009/12/logging-guidelines/] * [another, focused on devs|http://www.codeproject.com/Articles/42354/The-Art-of-Logging] * [guidelines from a user on stackoverflow (that I like)|http://stackoverflow.com/a/2031209] also has some good discussion. * [extended logging discussion with some level use guidelines|http://www.javacodegeeks.com/2011/01/10-tips-proper-application-logging.html] * [guidelines for Atlassian devs|https://developer.atlassian.com/display/CONFDEV/Logging+Guidelines] * [guidelines for OpenStack devs|https://wiki.openstack.org/wiki/LoggingStandards] * [the Kafka dev guide|http://kafka.apache.org/coding-guide.html] has a good section on their use titled Logging -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12256) Update patch submission guidelines to call out binary file support
[
https://issues.apache.org/jira/browse/HBASE-12256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-12256:
Status: Patch Available (was: Open)
Update patch submission guidelines to call out binary file support
--
Key: HBASE-12256
URL: https://issues.apache.org/jira/browse/HBASE-12256
Project: HBase
Issue Type: Improvement
Components: documentation
Reporter: Sean Busbey
Assignee: Misty Stanley-Jones
Priority: Minor
Labels: git
Attachments: HBASE-12256.patch
Our guidelines should call out where users need to take special care if they
have binary files in their diff. (binary files here means anything {{file}}
detects as data)
By default {{git diff}} won't include binary files, instead it'll just say
something like binary files differ. That'll render the patch useless.
* Update reasons to favor format-patch to include can handle binary files
changing by default.
* Add a note on {{git diff}} (or change the default args) to use {{--binary}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12256) Update patch submission guidelines to call out binary file support
[
https://issues.apache.org/jira/browse/HBASE-12256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-12256:
Attachment: HBASE-12256.patch
Update patch submission guidelines to call out binary file support
--
Key: HBASE-12256
URL: https://issues.apache.org/jira/browse/HBASE-12256
Project: HBase
Issue Type: Improvement
Components: documentation
Reporter: Sean Busbey
Assignee: Misty Stanley-Jones
Priority: Minor
Labels: git
Attachments: HBASE-12256.patch
Our guidelines should call out where users need to take special care if they
have binary files in their diff. (binary files here means anything {{file}}
detects as data)
By default {{git diff}} won't include binary files, instead it'll just say
something like binary files differ. That'll render the patch useless.
* Update reasons to favor format-patch to include can handle binary files
changing by default.
* Add a note on {{git diff}} (or change the default args) to use {{--binary}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13062) Add documentation coverage for configuring dns server with thrift and rest gateways
[ https://issues.apache.org/jira/browse/HBASE-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-13062: Status: Patch Available (was: Open) Add documentation coverage for configuring dns server with thrift and rest gateways --- Key: HBASE-13062 URL: https://issues.apache.org/jira/browse/HBASE-13062 Project: HBase Issue Type: Bug Components: documentation Reporter: Srikanth Srungarapu Assignee: Misty Stanley-Jones Priority: Minor Attachments: HBASE-13062.patch Currently, the documentation doesn't cover about configuring DNS with thrift or rest gateways, though code base does provide provision for doing so. The following parameters are being used for accomplishing the same. For REST: * hbase.rest.dns.interface * hbase.rest.dns.nameserver For Thrift: * hbase.thrift.dns.interface * hbase.thrift.dns.nameserver -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HBASE-13062) Add documentation coverage for configuring dns server with thrift and rest gateways
[ https://issues.apache.org/jira/browse/HBASE-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones reassigned HBASE-13062: --- Assignee: Misty Stanley-Jones Add documentation coverage for configuring dns server with thrift and rest gateways --- Key: HBASE-13062 URL: https://issues.apache.org/jira/browse/HBASE-13062 Project: HBase Issue Type: Bug Components: documentation Reporter: Srikanth Srungarapu Assignee: Misty Stanley-Jones Priority: Minor Attachments: HBASE-13062.patch Currently, the documentation doesn't cover about configuring DNS with thrift or rest gateways, though code base does provide provision for doing so. The following parameters are being used for accomplishing the same. For REST: * hbase.rest.dns.interface * hbase.rest.dns.nameserver For Thrift: * hbase.thrift.dns.interface * hbase.thrift.dns.nameserver -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13062) Add documentation coverage for configuring dns server with thrift and rest gateways
[ https://issues.apache.org/jira/browse/HBASE-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-13062: Attachment: HBASE-13062.patch Add documentation coverage for configuring dns server with thrift and rest gateways --- Key: HBASE-13062 URL: https://issues.apache.org/jira/browse/HBASE-13062 Project: HBase Issue Type: Bug Components: documentation Reporter: Srikanth Srungarapu Assignee: Misty Stanley-Jones Priority: Minor Attachments: HBASE-13062.patch Currently, the documentation doesn't cover about configuring DNS with thrift or rest gateways, though code base does provide provision for doing so. The following parameters are being used for accomplishing the same. For REST: * hbase.rest.dns.interface * hbase.rest.dns.nameserver For Thrift: * hbase.thrift.dns.interface * hbase.thrift.dns.nameserver -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12615) Document GC conserving guidelines for contributors
[
https://issues.apache.org/jira/browse/HBASE-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679494#comment-14679494
]
Hadoop QA commented on HBASE-12615:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749494/HBASE-12615.patch
against master branch at commit 5bdb0eb91290e306213bca62cea82c5d1b24d317.
ATTACHMENT ID: 12749494
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+As Apache HBase is an Apache Software Foundation project, see asf,asf
for more information about how the ASF functions.
+Posing questions - and helping to answer other people's questions - is
encouraged! There are varying levels of experience on both lists so patience
and politeness are encouraged (and please stay on topic.)
+For additional information on setting up Eclipse for HBase development on
Windows, see
link:http://michaelmorello.blogspot.com/2011/09/hbase-subversion-eclipse-windows.html[Michael
Morello's blog] on the topic.
+Note that Hadoop-3.0.0-SNAPSHOT does not currently have a deployed maven
artificat - you will need to build and install your own in your local maven
repository if you want to run against this profile.
+In the following procedures, we make a distinction between HBase 1.x builds
and the awkward process involved building HBase 0.96/0.98 for either Hadoop 1
or Hadoop 2 targets.
+You should also have tried recent branch tips out on a cluster under load,
perhaps by running the `hbase-it` integration test suite for a few hours to
'burn in' the near-candidate bits.
+This usually involves copying the latest from trunk and making
version-particular adjustments to suit this release candidate version.
+Make sure you are pulling from the repository when tests run and that you are
not getting from your local repository, by either passing the `-U` flag or
deleting your local repo content and check maven is pulling from remote out of
the staging repository.
+If there is no _-SNAPSHOT_on the version string,
then we are 'deployed' to the apache maven repository staging directory from
which we can publish URLs for candidates and later, if they pass, publish as
release (if a _-SNAPSHOT_ on the version string, deploy will put the artifacts
up into apache snapshot repos).
+See appendix_contributing_to_documentation,appendix contributing to
documentation for more information on building the documentation.
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15019//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15019//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15019//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15019//console
This message is automatically generated.
Document GC conserving guidelines for contributors
--
Key: HBASE-12615
URL: https://issues.apache.org/jira/browse/HBASE-12615
Project: HBase
Issue Type: Bug
Components: documentation
Reporter: Andrew Purtell
Assignee: Misty Stanley-Jones
Attachments: HBASE-12615.patch
LinkedIn put up a blog post with a nice concise list of GC conserving
techniques we should document for contributors. Additionally, when we're at a
point our build supports custom error-prone plugins, we can develop warnings
for some of them.
Source:
[jira] [Commented] (HBASE-14071) Document troubleshooting unexpected filesystem usage by snapshots and WALs
[ https://issues.apache.org/jira/browse/HBASE-14071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679523#comment-14679523 ] Sean Busbey commented on HBASE-14071: - +1 Document troubleshooting unexpected filesystem usage by snapshots and WALs -- Key: HBASE-14071 URL: https://issues.apache.org/jira/browse/HBASE-14071 Project: HBase Issue Type: Task Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Attachments: HBASE-14071.patch Document how to troubleshoot things like unexpected snapshot and WAL growth on the filesystem -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13924) Description for hbase.dynamic.jars.dir is wrong
[
https://issues.apache.org/jira/browse/HBASE-13924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679446#comment-14679446
]
Misty Stanley-Jones commented on HBASE-13924:
-
Weird. I have no idea why that happened. Must be something with my editor. Let
me try to regenerate the patch.
Description for hbase.dynamic.jars.dir is wrong
---
Key: HBASE-13924
URL: https://issues.apache.org/jira/browse/HBASE-13924
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0.1
Reporter: Lars George
Assignee: Misty Stanley-Jones
Labels: beginner
Fix For: 2.0.0, 1.3.0
Attachments: HBASE-13924.patch
The description in the following is wrong:
{noformat}
property
namehbase.dynamic.jars.dir/name
value${hbase.rootdir}/lib/value
description
The directory from which the custom filter/co-processor jars can be
loaded
dynamically by the region server without the need to restart. However,
an already loaded filter/co-processor class would not be un-loaded. See
HBASE-1936 for more details.
/description
/property
{noformat}
The {{DynamicClassLoader}} is *not* used for coprocessors, but only for
filters, comparators, and exceptions. Fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13478) Document the change of default master ports being used .
[ https://issues.apache.org/jira/browse/HBASE-13478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-13478: Attachment: HBASE-13478.patch Document the change of default master ports being used . Key: HBASE-13478 URL: https://issues.apache.org/jira/browse/HBASE-13478 Project: HBase Issue Type: Sub-task Components: documentation Reporter: Srikanth Srungarapu Assignee: Misty Stanley-Jones Priority: Minor Attachments: HBASE-13478.patch In 1.0.x, master by default binds to the region server ports. But in 1.1 and 2.0 branches, we have undone this changes and brought back the usage of old master ports to make the migration from 0.98 - 1.1 hassle free. Please see the parent jira for more background. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HBASE-11299) Stop making javadoc for generated classes
[ https://issues.apache.org/jira/browse/HBASE-11299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones resolved HBASE-11299. - Resolution: Cannot Reproduce Stop making javadoc for generated classes - Key: HBASE-11299 URL: https://issues.apache.org/jira/browse/HBASE-11299 Project: HBase Issue Type: Bug Components: documentation Reporter: stack Priority: Minor Attachments: 11299.txt Our javadoc generation is taking a long time. Also, when we go to update our site, the javadoc changes are so many -- the date has changed on generated doc -- that it takes for ever to commit (it is frighteningly long and noobs can only think they've done something wrong). I have been trying various tricks to get javadoc tool to ignore the generated protobuf classes but am not having much success (it is a background process and the distractions don't help). Stashing here changes I have so far to the javadoc pom which excludes some of the unneeded files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13478) Document the change of default master ports being used .
[ https://issues.apache.org/jira/browse/HBASE-13478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-13478: Status: Patch Available (was: Open) Document the change of default master ports being used . Key: HBASE-13478 URL: https://issues.apache.org/jira/browse/HBASE-13478 Project: HBase Issue Type: Sub-task Components: documentation Reporter: Srikanth Srungarapu Assignee: Misty Stanley-Jones Priority: Minor Attachments: HBASE-13478.patch In 1.0.x, master by default binds to the region server ports. But in 1.1 and 2.0 branches, we have undone this changes and brought back the usage of old master ports to make the migration from 0.98 - 1.1 hassle free. Please see the parent jira for more background. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11299) Stop making javadoc for generated classes
[ https://issues.apache.org/jira/browse/HBASE-11299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679484#comment-14679484 ] Misty Stanley-Jones commented on HBASE-11299: - I think this got fixed somewhere along the line. Stop making javadoc for generated classes - Key: HBASE-11299 URL: https://issues.apache.org/jira/browse/HBASE-11299 Project: HBase Issue Type: Bug Components: documentation Reporter: stack Priority: Minor Attachments: 11299.txt Our javadoc generation is taking a long time. Also, when we go to update our site, the javadoc changes are so many -- the date has changed on generated doc -- that it takes for ever to commit (it is frighteningly long and noobs can only think they've done something wrong). I have been trying various tricks to get javadoc tool to ignore the generated protobuf classes but am not having much success (it is a background process and the distractions don't help). Stashing here changes I have so far to the javadoc pom which excludes some of the unneeded files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13425) Documentation nit in REST Gateway impersonation section
[
https://issues.apache.org/jira/browse/HBASE-13425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679490#comment-14679490
]
Hadoop QA commented on HBASE-13425:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749497/HBASE-13425.patch
against master branch at commit 5bdb0eb91290e306213bca62cea82c5d1b24d317.
ATTACHMENT ID: 12749497
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ZooKeeper has a pluggable authentication mechanism to enable access from
clients using different methods. ZooKeeper even allows authenticated and
un-authenticated clients at the same time. The access to znodes can be
restricted by providing Access Control Lists (ACLs) per znode. An ACL contains
two components, the authentication method and the principal. ACLs are NOT
enforced hierarchically. See
link:https://zookeeper.apache.org/doc/r3.3.6/zookeeperProgrammers.html#sc_ZooKeeperPluggableAuthentication[ZooKeeper
Programmers Guide] for details.
+HBase daemons authenticate to ZooKeeper via SASL and kerberos (See
zk.sasl.auth). HBase sets up the znode ACLs so that only the HBase user and
the configured hbase superuser (`hbase.superuser`) can access and modify the
data. In cases where ZooKeeper is used for service discovery or sharing state
with the client, the znodes created by HBase will also allow anyone (regardless
of authentication) to read these znodes (clusterId, master address, meta
location, etc), but only the HBase user can modify them.
+All of the data under management is kept under the root directory in the file
system (`hbase.rootdir`). Access to the data and WAL files in the filesystem
should be restricted so that users cannot bypass the HBase layer, and peek at
the underlying data files from the file system. HBase assumes the filesystem
used (HDFS or other) enforces permissions hierarchically. If sufficient
protection from the file system (both authorization and authentication) is not
provided, HBase level authorization control (ACLs, visibility labels, etc) is
meaningless since the user can always access the data from the file system.
+In secure mode, SecureBulkLoadEndpoint should be configured and used for
properly handing of users files created from MR jobs to the HBase daemons and
HBase user. The staging directory in the distributed file system used for bulk
load (`hbase.bulkload.staging.dir`, defaults to `/tmp/hbase-staging`) should
have (mode 711, or `rwx--x--x`) so that users can access the staging directory
created under that parent directory, but cannot do any other operation. See
hbase.secure.bulkload for how to configure SecureBulkLoadEndPoint.
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 3 zombie test(s):
at
org.apache.hadoop.hbase.client.TestMobRestoreSnapshotFromClient.testRestoreSnapshot(TestMobRestoreSnapshotFromClient.java:157)
at
org.apache.hadoop.hbase.client.TestCloneSnapshotFromClient.testCloneSnapshot(TestCloneSnapshotFromClient.java:171)
at
org.apache.hadoop.hbase.client.TestCloneSnapshotFromClient.testCloneSnapshot(TestCloneSnapshotFromClient.java:159)
at
org.apache.hadoop.hbase.client.TestBlockEvictionFromClient.testParallelGetsAndScanWithWrappedRegionScanner(TestBlockEvictionFromClient.java:749)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15020//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15020//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
[jira] [Commented] (HBASE-13924) Description for hbase.dynamic.jars.dir is wrong
[
https://issues.apache.org/jira/browse/HBASE-13924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679512#comment-14679512
]
Sean Busbey commented on HBASE-13924:
-
+1
Description for hbase.dynamic.jars.dir is wrong
---
Key: HBASE-13924
URL: https://issues.apache.org/jira/browse/HBASE-13924
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0.1
Reporter: Lars George
Assignee: Misty Stanley-Jones
Labels: beginner
Fix For: 2.0.0, 1.3.0
Attachments: HBASE-13924-v1.patch, HBASE-13924.patch
The description in the following is wrong:
{noformat}
property
namehbase.dynamic.jars.dir/name
value${hbase.rootdir}/lib/value
description
The directory from which the custom filter/co-processor jars can be
loaded
dynamically by the region server without the need to restart. However,
an already loaded filter/co-processor class would not be un-loaded. See
HBASE-1936 for more details.
/description
/property
{noformat}
The {{DynamicClassLoader}} is *not* used for coprocessors, but only for
filters, comparators, and exceptions. Fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13446) Add docs warning about missing data for downstream on versions prior to HBASE-13262
[
https://issues.apache.org/jira/browse/HBASE-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-13446:
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: (was: 1.0.3)
(was: 0.98.14)
Status: Resolved (was: Patch Available)
Pushed to master
Add docs warning about missing data for downstream on versions prior to
HBASE-13262
---
Key: HBASE-13446
URL: https://issues.apache.org/jira/browse/HBASE-13446
Project: HBase
Issue Type: Task
Components: documentation
Affects Versions: 0.98.0, 1.0.0
Reporter: Sean Busbey
Assignee: Misty Stanley-Jones
Priority: Critical
Fix For: 2.0.0
Attachments: HBASE-13446.patch
From conversation at the end of HBASE-13262:
[~davelatham]
{quote}
Should we put a warning somewhere (mailing list? book?) about this? Something
like:
IF (client OR server is = 0.98.11/1.0.0) AND server has a smaller value for
hbase.client.scanner.max.result.size than client does, THEN scan requests
that reach the server's hbase.client.scanner.max.result.size are likely to
miss data. In particular, 0.98.11 defaults
hbase.client.scanner.max.result.size to 2MB but other versions default to
larger values, so be very careful using 0.98.11 servers with any other client
version.
{quote}
[~busbey]
{quote}
How about we add a note in the ref guide for upgrades and for
troubleshooting?
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14071) Document troubleshooting unexpected filesystem usage by snapshots and WALs
[
https://issues.apache.org/jira/browse/HBASE-14071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679425#comment-14679425
]
Hadoop QA commented on HBASE-14071:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749492/HBASE-14071.patch
against master branch at commit 5bdb0eb91290e306213bca62cea82c5d1b24d317.
ATTACHMENT ID: 12749492
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation, build,
or dev-support patch that doesn't require tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.TestChoreService.testForceTrigger(TestChoreService.java:398)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15016//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15016//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15016//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15016//console
This message is automatically generated.
Document troubleshooting unexpected filesystem usage by snapshots and WALs
--
Key: HBASE-14071
URL: https://issues.apache.org/jira/browse/HBASE-14071
Project: HBase
Issue Type: Task
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
Attachments: HBASE-14071.patch
Document how to troubleshoot things like unexpected snapshot and WAL growth
on the filesystem
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13924) Description for hbase.dynamic.jars.dir is wrong
[
https://issues.apache.org/jira/browse/HBASE-13924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679454#comment-14679454
]
Hadoop QA commented on HBASE-13924:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749491/HBASE-13924.patch
against master branch at commit 5bdb0eb91290e306213bca62cea82c5d1b24d317.
ATTACHMENT ID: 12749491
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. 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:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15015//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15015//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15015//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15015//console
This message is automatically generated.
Description for hbase.dynamic.jars.dir is wrong
---
Key: HBASE-13924
URL: https://issues.apache.org/jira/browse/HBASE-13924
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0.1
Reporter: Lars George
Assignee: Misty Stanley-Jones
Labels: beginner
Fix For: 2.0.0, 1.3.0
Attachments: HBASE-13924-v1.patch, HBASE-13924.patch
The description in the following is wrong:
{noformat}
property
namehbase.dynamic.jars.dir/name
value${hbase.rootdir}/lib/value
description
The directory from which the custom filter/co-processor jars can be
loaded
dynamically by the region server without the need to restart. However,
an already loaded filter/co-processor class would not be un-loaded. See
HBASE-1936 for more details.
/description
/property
{noformat}
The {{DynamicClassLoader}} is *not* used for coprocessors, but only for
filters, comparators, and exceptions. Fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13907) Document how to deploy a coprocessor
[ https://issues.apache.org/jira/browse/HBASE-13907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679499#comment-14679499 ] Sean Busbey commented on HBASE-13907: - #1 and #2 sounds good to me. Document how to deploy a coprocessor Key: HBASE-13907 URL: https://issues.apache.org/jira/browse/HBASE-13907 Project: HBase Issue Type: Bug Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Attachments: HBASE-13907-1.patch, HBASE-13907-2.patch, HBASE-13907.patch Capture this information: Where are the dependencies located for these classes? Is there a path on HDFS or local disk that dependencies need to be placed so that each RegionServer has access to them? It is suggested to bundle them as a single jar so that RS can load the whole jar and resolve dependencies. If you are not able to do that, you need place the dependencies in regionservers class path so that they are loaded during RS startup. Do either of these options work for you? Btw, you can load the coprocessors/filters into path specified by hbase.dynamic.jars.dir [1], so that they are loaded dynamically by regionservers when the class is accessed (or you can place them in the RS class path too, so that they are loaded during RS JVM startup). How would one deploy these using an automated system? (puppet/chef/ansible/etc) You can probably use these tools to automate shipping the jars to above locations? Tests our developers have done suggest that simply disabling a coprocessor, replacing the jar with a different version, and enabling the coprocessor again does not load the newest version. With that in mind how does one know which version is currently deployed and enabled without resorting to parsing `hbase shell` output or restarting hbase? Actually this is a design issue with current classloader. You can't reload a class in a JVM unless you delete all the current references to it. Since the current JVM (classloader) has reference to it, you can't overwrite it unless you kill the JVM, which is equivalent to restarting it. So you still have the older class loaded in place. For this to work, classloader design should be changed. If it works for you, you can rename the coprocessor class name and the new version of jar and RS loads it properly. Where does logging go, and how does one access it? Does logging need to be configured in a certain way? Can you please specify which logging you are referring to? Where is a good location to place configuration files? Same as above, are these hbase configs or something else? If hbase configs, are these gateway configs/server side? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12256) Update patch submission guidelines to call out binary file support
[
https://issues.apache.org/jira/browse/HBASE-12256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679510#comment-14679510
]
Sean Busbey commented on HBASE-12256:
-
+1
nit: includes some nearby unrelated formatting fixes.
Update patch submission guidelines to call out binary file support
--
Key: HBASE-12256
URL: https://issues.apache.org/jira/browse/HBASE-12256
Project: HBase
Issue Type: Improvement
Components: documentation
Reporter: Sean Busbey
Assignee: Misty Stanley-Jones
Priority: Minor
Labels: git
Attachments: HBASE-12256.patch
Our guidelines should call out where users need to take special care if they
have binary files in their diff. (binary files here means anything {{file}}
detects as data)
By default {{git diff}} won't include binary files, instead it'll just say
something like binary files differ. That'll render the patch useless.
* Update reasons to favor format-patch to include can handle binary files
changing by default.
* Add a note on {{git diff}} (or change the default args) to use {{--binary}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14046) IllegalArgumentException: Negative position from hfile.bucket.FileIOEngine.read
[
https://issues.apache.org/jira/browse/HBASE-14046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679526#comment-14679526
]
Liu Shaohui commented on HBASE-14046:
-
[~louis.hust]
Do you enable the caching blocks on write?
May be it's same problem as HBASE-12270
IllegalArgumentException: Negative position from
hfile.bucket.FileIOEngine.read
---
Key: HBASE-14046
URL: https://issues.apache.org/jira/browse/HBASE-14046
Project: HBase
Issue Type: Bug
Components: hbase
Affects Versions: 0.98.6
Environment: CentOS release 6.4 X86_64
Reporter: louis hust
Priority: Critical
When I scan a table using hbase shell, got the following message:
{code:bash}
hbase(main):001:0 scan 'atpco:ttf_record6'
ROW COLUMN+CELL
ERROR: org.apache.hadoop.hbase.exceptions.OutOfOrderScannerNextException:
Expected nextCallSeq: 1 But the nextCallSeq got from client: 0;
request=scanner_id: 201542113 number_of_rows: 100 close_scanner: false
next_call_seq: 0
at
org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:3193)
at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29587)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2031)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
at
org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
at java.lang.Thread.run(Thread.java:744)
{code}
And the region server got the following error:
{code}
2015-06-30 11:08:11,877 ERROR
[B.defaultRpcServer.handler=27,queue=0,port=60020] ipc.RpcServer: Unexpected
throwable object
java.lang.IllegalArgumentException: Negative position
at sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:675)
at
org.apache.hadoop.hbase.io.hfile.bucket.FileIOEngine.read(FileIOEngine.java:87)
at
org.apache.hadoop.hbase.io.hfile.bucket.BucketCache.getBlock(BucketCache.java:406)
at
org.apache.hadoop.hbase.io.hfile.LruBlockCache.getBlock(LruBlockCache.java:389)
at
org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:359)
at
org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.readNextDataBlock(HFileReaderV2.java:635)
at
org.apache.hadoop.hbase.io.hfile.HFileReaderV2$ScannerV2.next(HFileReaderV2.java:749)
at
org.apache.hadoop.hbase.regionserver.StoreFileScanner.next(StoreFileScanner.java:136)
at
org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:108)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:507)
at
org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:140)
at
org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:3900)
at
org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:3980)
at
org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3858)
at
org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3849)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:3245)
at
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29587)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2031)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
{code}
It seems something wrong with the BucketCache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14200) Separate some subtests of TestStochasticLoadBalancer into TestStochasticLoadBalancer2
[ https://issues.apache.org/jira/browse/HBASE-14200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679569#comment-14679569 ] Jerry He commented on HBASE-14200: -- After the move, the protected/private methods testWithCluster and createServerMap are duplicated in two test files? Is there any way to avoid duplicating the same code? Separate some subtests of TestStochasticLoadBalancer into TestStochasticLoadBalancer2 - Key: HBASE-14200 URL: https://issues.apache.org/jira/browse/HBASE-14200 Project: HBase Issue Type: Test Reporter: Ted Yu Assignee: Ted Yu Priority: Minor Fix For: 2.0.0, 1.3.0 Attachments: 14200-v1.txt More and more functionality is added to StochasticLoadBalancer , making TestStochasticLoadBalancer run longer. From https://builds.apache.org/job/PreCommit-HBASE-Build/15011/testReport/org.apache.hadoop.hbase.master.balancer/TestStochasticLoadBalancer/ where total runtime was 14 min, here are the longest subtests: testRegionReplicasOnLargeCluster: 1 min 34 sec testRegionReplicasOnMidCluster: 1 min 31 sec testRegionReplicasOnMidClusterHighReplication: 2 min testRegionReplicationOnMidClusterReplicationGreaterThanNumNodes: 2 min 25 sec This issue is to separate out the above subtests into TestStochasticLoadBalancer2, giving each of the tests around 7 min runtime. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12256) Update patch submission guidelines to call out binary file support
[
https://issues.apache.org/jira/browse/HBASE-12256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679568#comment-14679568
]
Hadoop QA commented on HBASE-12256:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749508/HBASE-12256.patch
against master branch at commit 5bdb0eb91290e306213bca62cea82c5d1b24d317.
ATTACHMENT ID: 12749508
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ Make sure you review eclipse.code.formatting,eclipse.code.formatting
and common.patch.feedback,common.patch.feedback for code style.
+ If your patch was generated incorrectly or your code does not adhere to the
code formatting guidelines, you may be asked to redo some work.
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15023//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15023//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15023//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15023//console
This message is automatically generated.
Update patch submission guidelines to call out binary file support
--
Key: HBASE-12256
URL: https://issues.apache.org/jira/browse/HBASE-12256
Project: HBase
Issue Type: Improvement
Components: documentation
Reporter: Sean Busbey
Assignee: Misty Stanley-Jones
Priority: Minor
Labels: git
Fix For: 2.0.0
Attachments: HBASE-12256.patch
Our guidelines should call out where users need to take special care if they
have binary files in their diff. (binary files here means anything {{file}}
detects as data)
By default {{git diff}} won't include binary files, instead it'll just say
something like binary files differ. That'll render the patch useless.
* Update reasons to favor format-patch to include can handle binary files
changing by default.
* Add a note on {{git diff}} (or change the default args) to use {{--binary}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13446) Add docs warning about missing data for downstream on versions prior to HBASE-13262
[
https://issues.apache.org/jira/browse/HBASE-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679427#comment-14679427
]
Hadoop QA commented on HBASE-13446:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749493/HBASE-13446.patch
against master branch at commit 5bdb0eb91290e306213bca62cea82c5d1b24d317.
ATTACHMENT ID: 12749493
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15017//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15017//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15017//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15017//console
This message is automatically generated.
Add docs warning about missing data for downstream on versions prior to
HBASE-13262
---
Key: HBASE-13446
URL: https://issues.apache.org/jira/browse/HBASE-13446
Project: HBase
Issue Type: Task
Components: documentation
Affects Versions: 0.98.0, 1.0.0
Reporter: Sean Busbey
Assignee: Misty Stanley-Jones
Priority: Critical
Fix For: 2.0.0, 0.98.14, 1.0.3
Attachments: HBASE-13446.patch
From conversation at the end of HBASE-13262:
[~davelatham]
{quote}
Should we put a warning somewhere (mailing list? book?) about this? Something
like:
IF (client OR server is = 0.98.11/1.0.0) AND server has a smaller value for
hbase.client.scanner.max.result.size than client does, THEN scan requests
that reach the server's hbase.client.scanner.max.result.size are likely to
miss data. In particular, 0.98.11 defaults
hbase.client.scanner.max.result.size to 2MB but other versions default to
larger values, so be very careful using 0.98.11 servers with any other client
version.
{quote}
[~busbey]
{quote}
How about we add a note in the ref guide for upgrades and for
troubleshooting?
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13924) Description for hbase.dynamic.jars.dir is wrong
[
https://issues.apache.org/jira/browse/HBASE-13924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679437#comment-14679437
]
Sean Busbey commented on HBASE-13924:
-
Contains a bunch of unrelated changes. Please either rescope the JIRA
description or the patxh.
Description for hbase.dynamic.jars.dir is wrong
---
Key: HBASE-13924
URL: https://issues.apache.org/jira/browse/HBASE-13924
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0.1
Reporter: Lars George
Assignee: Misty Stanley-Jones
Labels: beginner
Fix For: 2.0.0, 1.3.0
Attachments: HBASE-13924.patch
The description in the following is wrong:
{noformat}
property
namehbase.dynamic.jars.dir/name
value${hbase.rootdir}/lib/value
description
The directory from which the custom filter/co-processor jars can be
loaded
dynamically by the region server without the need to restart. However,
an already loaded filter/co-processor class would not be un-loaded. See
HBASE-1936 for more details.
/description
/property
{noformat}
The {{DynamicClassLoader}} is *not* used for coprocessors, but only for
filters, comparators, and exceptions. Fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12983) HBase book mentions hadoop.ssl.enabled when it should be hbase.ssl.enabled
[
https://issues.apache.org/jira/browse/HBASE-12983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679440#comment-14679440
]
Hadoop QA commented on HBASE-12983:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749495/HBASE-12983.patch
against master branch at commit 5bdb0eb91290e306213bca62cea82c5d1b24d317.
ATTACHMENT ID: 12749495
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+To enable secure HTTP (HTTPS) connections instead, set `hbase.ssl.enabled`
to `true` in _hbase-site.xml_.
+ZooKeeper has a pluggable authentication mechanism to enable access from
clients using different methods. ZooKeeper even allows authenticated and
un-authenticated clients at the same time. The access to znodes can be
restricted by providing Access Control Lists (ACLs) per znode. An ACL contains
two components, the authentication method and the principal. ACLs are NOT
enforced hierarchically. See
link:https://zookeeper.apache.org/doc/r3.3.6/zookeeperProgrammers.html#sc_ZooKeeperPluggableAuthentication[ZooKeeper
Programmers Guide] for details.
+HBase daemons authenticate to ZooKeeper via SASL and kerberos (See
zk.sasl.auth). HBase sets up the znode ACLs so that only the HBase user and
the configured hbase superuser (`hbase.superuser`) can access and modify the
data. In cases where ZooKeeper is used for service discovery or sharing state
with the client, the znodes created by HBase will also allow anyone (regardless
of authentication) to read these znodes (clusterId, master address, meta
location, etc), but only the HBase user can modify them.
+All of the data under management is kept under the root directory in the file
system (`hbase.rootdir`). Access to the data and WAL files in the filesystem
should be restricted so that users cannot bypass the HBase layer, and peek at
the underlying data files from the file system. HBase assumes the filesystem
used (HDFS or other) enforces permissions hierarchically. If sufficient
protection from the file system (both authorization and authentication) is not
provided, HBase level authorization control (ACLs, visibility labels, etc) is
meaningless since the user can always access the data from the file system.
+In secure mode, SecureBulkLoadEndpoint should be configured and used for
properly handing of users files created from MR jobs to the HBase daemons and
HBase user. The staging directory in the distributed file system used for bulk
load (`hbase.bulkload.staging.dir`, defaults to `/tmp/hbase-staging`) should
have (mode 711, or `rwx--x--x`) so that users can access the staging directory
created under that parent directory, but cannot do any other operation. See
hbase.secure.bulkload for how to configure SecureBulkLoadEndPoint.
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.util.TestDrainBarrier.testStopIsBlockedByOps(TestDrainBarrier.java:98)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15018//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15018//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15018//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15018//console
This message is automatically generated.
HBase book mentions hadoop.ssl.enabled when it should be hbase.ssl.enabled
--
[jira] [Commented] (HBASE-13129) Add troubleshooting hints around WAL retention from replication
[ https://issues.apache.org/jira/browse/HBASE-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679524#comment-14679524 ] Sean Busbey commented on HBASE-13129: - I don't think so. HBASE-14071 doesn't mention that having replication turned on for a table will cause us to retain WALs longer, and specifically if it's turned on with all peers disabled we'll build up WALs indefinitely. Add troubleshooting hints around WAL retention from replication --- Key: HBASE-13129 URL: https://issues.apache.org/jira/browse/HBASE-13129 Project: HBase Issue Type: Improvement Components: documentation, Replication Reporter: Sean Busbey Labels: operations, supportability There's been some confusion on the mailing list about when WALs get retained / cleaned up once replication is on at all in a cluster. (ref [this thread|http://mail-archives.apache.org/mod_mbox/hbase-user/201502.mbox/%3ccamuu0w9aovbo7kgulim9txrulirqs9fm-3ra3pqccypw_17...@mail.gmail.com%3E]) We should add a NOTE in the replication section that wals are saved across enable/disable so long as there are peers. There looks like there might also be some confusing language around replication being enabled in the configs vs the enable/disable suspension mechanism. We should also add a troubleshooting item specific for my HDFS space keeps growing and it's all in oldWALs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13924) Description for hbase.dynamic.jars.dir is wrong
[
https://issues.apache.org/jira/browse/HBASE-13924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679528#comment-14679528
]
Hadoop QA commented on HBASE-13924:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749503/HBASE-13924-v1.patch
against master branch at commit 5bdb0eb91290e306213bca62cea82c5d1b24d317.
ATTACHMENT ID: 12749503
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. 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:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.master.TestDistributedLogSplitting
{color:red}-1 core zombie tests{color}. There are 5 zombie test(s):
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testExportFileSystemState(TestExportSnapshot.java:288)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testExportFileSystemState(TestExportSnapshot.java:262)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testEmptyExportFileSystemState(TestExportSnapshot.java:206)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testExportFileSystemState(TestExportSnapshot.java:288)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testExportFileSystemState(TestExportSnapshot.java:262)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testSnapshotWithRefsExportFileSystemState(TestExportSnapshot.java:256)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testSnapshotWithRefsExportFileSystemState(TestExportSnapshot.java:236)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testExportFileSystemState(TestMobExportSnapshot.java:285)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testExportFileSystemState(TestMobExportSnapshot.java:259)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testExportWithTargetName(TestMobExportSnapshot.java:217)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15022//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15022//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15022//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15022//console
This message is automatically generated.
Description for hbase.dynamic.jars.dir is wrong
---
Key: HBASE-13924
URL: https://issues.apache.org/jira/browse/HBASE-13924
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0.1
Reporter: Lars George
Assignee: Misty Stanley-Jones
Labels: beginner
Fix For: 2.0.0, 1.3.0
Attachments: HBASE-13924-v1.patch, HBASE-13924.patch
The description in the following is wrong:
{noformat}
property
namehbase.dynamic.jars.dir/name
value${hbase.rootdir}/lib/value
description
The directory from which the custom filter/co-processor jars can be
loaded
dynamically by the region server without the need to restart. However,
an already loaded filter/co-processor class would not be un-loaded. See
HBASE-1936 for more details.
/description
/property
{noformat}
The {{DynamicClassLoader}} is *not* used for coprocessors, but only for
filters, comparators, and exceptions. Fix.
--
This message was sent by
[jira] [Updated] (HBASE-12256) Update patch submission guidelines to call out binary file support
[
https://issues.apache.org/jira/browse/HBASE-12256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-12256:
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.0.0
Status: Resolved (was: Patch Available)
Pushed to master.
Update patch submission guidelines to call out binary file support
--
Key: HBASE-12256
URL: https://issues.apache.org/jira/browse/HBASE-12256
Project: HBase
Issue Type: Improvement
Components: documentation
Reporter: Sean Busbey
Assignee: Misty Stanley-Jones
Priority: Minor
Labels: git
Fix For: 2.0.0
Attachments: HBASE-12256.patch
Our guidelines should call out where users need to take special care if they
have binary files in their diff. (binary files here means anything {{file}}
detects as data)
By default {{git diff}} won't include binary files, instead it'll just say
something like binary files differ. That'll render the patch useless.
* Update reasons to favor format-patch to include can handle binary files
changing by default.
* Add a note on {{git diff}} (or change the default args) to use {{--binary}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13478) Document the change of default master ports being used .
[
https://issues.apache.org/jira/browse/HBASE-13478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679603#comment-14679603
]
Hadoop QA commented on HBASE-13478:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749512/HBASE-13478.patch
against master branch at commit 5bdb0eb91290e306213bca62cea82c5d1b24d317.
ATTACHMENT ID: 12749512
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.mapreduce.TestImportExport
org.apache.hadoop.hbase.util.TestProcessBasedCluster
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15025//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15025//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15025//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15025//console
This message is automatically generated.
Document the change of default master ports being used .
Key: HBASE-13478
URL: https://issues.apache.org/jira/browse/HBASE-13478
Project: HBase
Issue Type: Sub-task
Components: documentation
Reporter: Srikanth Srungarapu
Assignee: Misty Stanley-Jones
Priority: Minor
Attachments: HBASE-13478.patch
In 1.0.x, master by default binds to the region server ports. But in 1.1 and
2.0 branches, we have undone this changes and brought back the usage of old
master ports to make the migration from 0.98 - 1.1 hassle free. Please see
the parent jira for more background.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13924) Description for hbase.dynamic.jars.dir is wrong
[
https://issues.apache.org/jira/browse/HBASE-13924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-13924:
Attachment: HBASE-13924-v1.patch
Description for hbase.dynamic.jars.dir is wrong
---
Key: HBASE-13924
URL: https://issues.apache.org/jira/browse/HBASE-13924
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0.1
Reporter: Lars George
Assignee: Misty Stanley-Jones
Labels: beginner
Fix For: 2.0.0, 1.3.0
Attachments: HBASE-13924-v1.patch, HBASE-13924.patch
The description in the following is wrong:
{noformat}
property
namehbase.dynamic.jars.dir/name
value${hbase.rootdir}/lib/value
description
The directory from which the custom filter/co-processor jars can be
loaded
dynamically by the region server without the need to restart. However,
an already loaded filter/co-processor class would not be un-loaded. See
HBASE-1936 for more details.
/description
/property
{noformat}
The {{DynamicClassLoader}} is *not* used for coprocessors, but only for
filters, comparators, and exceptions. Fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (HBASE-12256) Update patch submission guidelines to call out binary file support
[
https://issues.apache.org/jira/browse/HBASE-12256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones reassigned HBASE-12256:
---
Assignee: Misty Stanley-Jones
Update patch submission guidelines to call out binary file support
--
Key: HBASE-12256
URL: https://issues.apache.org/jira/browse/HBASE-12256
Project: HBase
Issue Type: Improvement
Components: documentation
Reporter: Sean Busbey
Assignee: Misty Stanley-Jones
Priority: Minor
Labels: git
Our guidelines should call out where users need to take special care if they
have binary files in their diff. (binary files here means anything {{file}}
detects as data)
By default {{git diff}} won't include binary files, instead it'll just say
something like binary files differ. That'll render the patch useless.
* Update reasons to favor format-patch to include can handle binary files
changing by default.
* Add a note on {{git diff}} (or change the default args) to use {{--binary}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (HBASE-13478) Document the change of default master ports being used .
[ https://issues.apache.org/jira/browse/HBASE-13478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones reassigned HBASE-13478: --- Assignee: Misty Stanley-Jones Document the change of default master ports being used . Key: HBASE-13478 URL: https://issues.apache.org/jira/browse/HBASE-13478 Project: HBase Issue Type: Sub-task Components: documentation Reporter: Srikanth Srungarapu Assignee: Misty Stanley-Jones Priority: Minor In 1.0.x, master by default binds to the region server ports. But in 1.1 and 2.0 branches, we have undone this changes and brought back the usage of old master ports to make the migration from 0.98 - 1.1 hassle free. Please see the parent jira for more background. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14189) BlockCache options should consider CF Level BlockCacheEnabled setting
[
https://issues.apache.org/jira/browse/HBASE-14189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Heng Chen updated HBASE-14189:
--
Attachment: HBASE-14189.patch
retry
BlockCache options should consider CF Level BlockCacheEnabled setting
-
Key: HBASE-14189
URL: https://issues.apache.org/jira/browse/HBASE-14189
Project: HBase
Issue Type: Improvement
Components: BlockCache
Affects Versions: 2.0.0
Reporter: Heng Chen
Assignee: Heng Chen
Attachments: HBASE-14189.patch
While using BlockCache, we use {{cacheDataOnRead}}({{cacheDataOnWrite}})
represents for whether we should cache block after read(write) block from(to)
hdfs. We should honour BC setting and CF Level cache setting while using
BlockCache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14189) BlockCache options should consider CF Level BlockCacheEnabled setting
[
https://issues.apache.org/jira/browse/HBASE-14189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Heng Chen updated HBASE-14189:
--
Attachment: (was: HBASE-14189.patch)
BlockCache options should consider CF Level BlockCacheEnabled setting
-
Key: HBASE-14189
URL: https://issues.apache.org/jira/browse/HBASE-14189
Project: HBase
Issue Type: Improvement
Components: BlockCache
Affects Versions: 2.0.0
Reporter: Heng Chen
Assignee: Heng Chen
Attachments: HBASE-14189.patch
While using BlockCache, we use {{cacheDataOnRead}}({{cacheDataOnWrite}})
represents for whether we should cache block after read(write) block from(to)
hdfs. We should honour BC setting and CF Level cache setting while using
BlockCache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13483) [docs] onheap is not a valid bucket cache IO engine.
[
https://issues.apache.org/jira/browse/HBASE-13483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679493#comment-14679493
]
Hadoop QA commented on HBASE-13483:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749496/HBASE-13483.patch
against master branch at commit 5bdb0eb91290e306213bca62cea82c5d1b24d317.
ATTACHMENT ID: 12749496
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:red}-1 findbugs{color}. The patch appears to cause Findbugs
(version 2.0.3) to fail.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.mapreduce.TestImportExport
org.apache.hadoop.hbase.util.TestProcessBasedCluster
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.activemq.artemis.rest.test.ClientAckQueueTest.testAckTimeout(ClientAckQueueTest.java:90)
at
org.apache.activemq.artemis.rest.test.ClientAckQueueTest.testAckTimeoutX2(ClientAckQueueTest.java:55)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15021//testReport/
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15021//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15021//console
This message is automatically generated.
[docs] onheap is not a valid bucket cache IO engine.
Key: HBASE-13483
URL: https://issues.apache.org/jira/browse/HBASE-13483
Project: HBase
Issue Type: Bug
Components: documentation
Affects Versions: 2.0.0
Reporter: Esteban Gutierrez
Assignee: Misty Stanley-Jones
Attachments: HBASE-13483.patch
From the HBase book:
http://hbase.apache.org/book.html#hbase_default_configurations
:
{code}
hbase.bucketcache.ioengine
Description
Where to store the contents of the bucketcache. One of: *onheap*, offheap, or
file. If a file, set it to file:PATH_TO_FILE. See
https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/io/hfile/CacheConfig.html
for more information.
{code}
Instead of onheap it should be heap.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13446) Add docs warning about missing data for downstream on versions prior to HBASE-13262
[
https://issues.apache.org/jira/browse/HBASE-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679521#comment-14679521
]
Sean Busbey commented on HBASE-13446:
-
+1
Add docs warning about missing data for downstream on versions prior to
HBASE-13262
---
Key: HBASE-13446
URL: https://issues.apache.org/jira/browse/HBASE-13446
Project: HBase
Issue Type: Task
Components: documentation
Affects Versions: 0.98.0, 1.0.0
Reporter: Sean Busbey
Assignee: Misty Stanley-Jones
Priority: Critical
Fix For: 2.0.0, 0.98.14, 1.0.3
Attachments: HBASE-13446.patch
From conversation at the end of HBASE-13262:
[~davelatham]
{quote}
Should we put a warning somewhere (mailing list? book?) about this? Something
like:
IF (client OR server is = 0.98.11/1.0.0) AND server has a smaller value for
hbase.client.scanner.max.result.size than client does, THEN scan requests
that reach the server's hbase.client.scanner.max.result.size are likely to
miss data. In particular, 0.98.11 defaults
hbase.client.scanner.max.result.size to 2MB but other versions default to
larger values, so be very careful using 0.98.11 servers with any other client
version.
{quote}
[~busbey]
{quote}
How about we add a note in the ref guide for upgrades and for
troubleshooting?
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13924) Description for hbase.dynamic.jars.dir is wrong
[
https://issues.apache.org/jira/browse/HBASE-13924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-13924:
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: (was: 1.3.0)
Status: Resolved (was: Patch Available)
Committed to master.
Description for hbase.dynamic.jars.dir is wrong
---
Key: HBASE-13924
URL: https://issues.apache.org/jira/browse/HBASE-13924
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0.1
Reporter: Lars George
Assignee: Misty Stanley-Jones
Labels: beginner
Fix For: 2.0.0
Attachments: HBASE-13924-v1.patch, HBASE-13924.patch
The description in the following is wrong:
{noformat}
property
namehbase.dynamic.jars.dir/name
value${hbase.rootdir}/lib/value
description
The directory from which the custom filter/co-processor jars can be
loaded
dynamically by the region server without the need to restart. However,
an already loaded filter/co-processor class would not be un-loaded. See
HBASE-1936 for more details.
/description
/property
{noformat}
The {{DynamicClassLoader}} is *not* used for coprocessors, but only for
filters, comparators, and exceptions. Fix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14071) Document troubleshooting unexpected filesystem usage by snapshots and WALs
[ https://issues.apache.org/jira/browse/HBASE-14071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-14071: Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.0.0 Status: Resolved (was: Patch Available) Committed to master. Document troubleshooting unexpected filesystem usage by snapshots and WALs -- Key: HBASE-14071 URL: https://issues.apache.org/jira/browse/HBASE-14071 Project: HBase Issue Type: Task Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 2.0.0 Attachments: HBASE-14071.patch Document how to troubleshoot things like unexpected snapshot and WAL growth on the filesystem -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13062) Add documentation coverage for configuring dns server with thrift and rest gateways
[
https://issues.apache.org/jira/browse/HBASE-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679592#comment-14679592
]
Hadoop QA commented on HBASE-13062:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749510/HBASE-13062.patch
against master branch at commit 5bdb0eb91290e306213bca62cea82c5d1b24d317.
ATTACHMENT ID: 12749510
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15026//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15026//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15026//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15026//console
This message is automatically generated.
Add documentation coverage for configuring dns server with thrift and rest
gateways
---
Key: HBASE-13062
URL: https://issues.apache.org/jira/browse/HBASE-13062
Project: HBase
Issue Type: Bug
Components: documentation
Reporter: Srikanth Srungarapu
Assignee: Misty Stanley-Jones
Priority: Minor
Attachments: HBASE-13062.patch
Currently, the documentation doesn't cover about configuring DNS with thrift
or rest gateways, though code base does provide provision for doing so. The
following parameters are being used for accomplishing the same.
For REST:
* hbase.rest.dns.interface
* hbase.rest.dns.nameserver
For Thrift:
* hbase.thrift.dns.interface
* hbase.thrift.dns.nameserver
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14189) BlockCache options should consider CF Level BlockCacheEnabled setting
[
https://issues.apache.org/jira/browse/HBASE-14189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679606#comment-14679606
]
Hadoop QA commented on HBASE-14189:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12749511/HBASE-14189.patch
against master branch at commit 5bdb0eb91290e306213bca62cea82c5d1b24d317.
ATTACHMENT ID: 12749511
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 44 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
1863 checkstyle errors (more than the master's current 1862 errors).
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 8 zombie test(s):
at
org.apache.hadoop.hbase.snapshot.TestMobRestoreFlushSnapshotFromClient.testCloneSnapshot(TestMobRestoreFlushSnapshotFromClient.java:188)
at
org.apache.hadoop.hbase.snapshot.TestMobRestoreFlushSnapshotFromClient.testCloneSnapshot(TestMobRestoreFlushSnapshotFromClient.java:179)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testExportFileSystemState(TestExportSnapshot.java:288)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testExportFileSystemState(TestExportSnapshot.java:262)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testExportFileSystemState(TestExportSnapshot.java:195)
at
org.apache.hadoop.hbase.io.hfile.TestCacheOnWrite.testStoreFileCacheOnWriteInternals(TestCacheOnWrite.java:265)
at
org.apache.hadoop.hbase.io.hfile.TestCacheOnWrite.testStoreFileCacheOnWrite(TestCacheOnWrite.java:492)
at
org.apache.hadoop.hbase.mapreduce.TestImportTSVWithVisibilityLabels.testBulkOutputWithTsvImporterTextMapper(TestImportTSVWithVisibilityLabels.java:256)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testExportFileSystemState(TestMobExportSnapshot.java:285)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testExportFileSystemState(TestMobExportSnapshot.java:259)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testSnapshotWithRefsExportFileSystemState(TestMobExportSnapshot.java:253)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testSnapshotWithRefsExportFileSystemState(TestMobExportSnapshot.java:233)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testExportFileSystemState(TestMobExportSnapshot.java:285)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testExportFileSystemState(TestMobExportSnapshot.java:259)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testExportFileSystemStateWithSkipTmp(TestMobExportSnapshot.java:198)
at
org.apache.hadoop.hbase.io.encoding.TestDataBlockEncoders.testSeekingOnSample(TestDataBlockEncoders.java:217)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15024//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15024//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15024//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15024//console
This message is automatically generated.
BlockCache options should consider CF Level BlockCacheEnabled setting
-
Key: HBASE-14189
URL: https://issues.apache.org/jira/browse/HBASE-14189
Project: HBase
Issue Type: Improvement
Components: BlockCache
Affects Versions: 2.0.0
Reporter: Heng Chen
Assignee: Heng Chen
Attachments: HBASE-14189.patch
While using
[jira] [Updated] (HBASE-14147) REST Support for Namespaces
[ https://issues.apache.org/jira/browse/HBASE-14147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Warhaftig updated HBASE-14147: --- Status: Patch Available (was: In Progress) REST Support for Namespaces --- Key: HBASE-14147 URL: https://issues.apache.org/jira/browse/HBASE-14147 Project: HBase Issue Type: Sub-task Components: REST Affects Versions: 1.1.1 Reporter: Rick Kellogg Assignee: Matt Warhaftig Priority: Minor Attachments: hbase-14147-v1.patch Expand REST services to include addition features: * Create namespace * Alter namespace * Describe namespace * Drop namespace * List tables in a specific namespace * List all namespaces. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (HBASE-14147) REST Support for Namespaces
[ https://issues.apache.org/jira/browse/HBASE-14147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-14147 started by Matt Warhaftig. -- REST Support for Namespaces --- Key: HBASE-14147 URL: https://issues.apache.org/jira/browse/HBASE-14147 Project: HBase Issue Type: Sub-task Components: REST Affects Versions: 1.1.1 Reporter: Rick Kellogg Assignee: Matt Warhaftig Priority: Minor Attachments: hbase-14147-v1.patch Expand REST services to include addition features: * Create namespace * Alter namespace * Describe namespace * Drop namespace * List tables in a specific namespace * List all namespaces. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14147) REST Support for Namespaces
[
https://issues.apache.org/jira/browse/HBASE-14147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Warhaftig updated HBASE-14147:
---
Attachment: hbase-14147-v1.patch
Attached patch 'hbase-14147-v1.patch' adds namespace CRUD functionality to
rest. A brief overview of the functionality:
|| REST Endpoint || REST Verb || Operation ||
| /namespaces | GET | list all namespaces|
| /namespaces/\{namespace\} | GET |describe namespace|
| /namespaces/\{namespace\}/tables | GET | list namespace tables|
| /namespaces/\{namespace\} | POST |create namespace|
| /namespaces/\{namespace\} | PUT | alter namespace|
| /namespaces/\{namespace\} | DELETE | delete namespace|
Please closely peer review this functionality as it is a large update.
Also note that the HBase REST documentation on the following wiki will need to
be updated to include the new fields:
https://wiki.apache.org/hadoop/Hbase/Stargate
REST Support for Namespaces
---
Key: HBASE-14147
URL: https://issues.apache.org/jira/browse/HBASE-14147
Project: HBase
Issue Type: Sub-task
Components: REST
Affects Versions: 1.1.1
Reporter: Rick Kellogg
Assignee: Matt Warhaftig
Priority: Minor
Attachments: hbase-14147-v1.patch
Expand REST services to include addition features:
* Create namespace
* Alter namespace
* Describe namespace
* Drop namespace
* List tables in a specific namespace
* List all namespaces.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
