[jira] [Commented] (HBASE-11815) Flush and compaction could just close the tmp writer if there is an exception
[
https://issues.apache.org/jira/browse/HBASE-11815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161527#comment-14161527
]
Hudson commented on HBASE-11815:
SUCCESS: Integrated in HBase-0.98 #579 (See
[https://builds.apache.org/job/HBase-0.98/579/])
HBASE-11815 - Flush and compaction could just close the tmp writer if
(ramkrishna: rev 401996efdb60b0f3395eca2bd2f5215cd33346bb)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreFlusher.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/DefaultCompactor.java
Flush and compaction could just close the tmp writer if there is an exception
-
Key: HBASE-11815
URL: https://issues.apache.org/jira/browse/HBASE-11815
Project: HBase
Issue Type: Bug
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Priority: Trivial
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: HBASE-11815.patch, HBASE-11815_0.98.patch,
HBASE-11815_1.patch, HBASE-11815_2.patch, HBASE-11815_2.patch
A minor change.
{code}
try {
flushed = performFlush(scanner, writer, smallestReadPoint);
} finally {
finalizeWriter(writer, cacheFlushId, status);
}
{code}
Whenever there is a failure during flush we should close the writer but
adding the meta data and setting the status would not be needed.
{code}
status.setStatus(Flushing + store + : appending metadata);
writer.appendMetadata(cacheFlushSeqNum, false);
status.setStatus(Flushing + store + : closing flushed file);
writer.close();
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12053) SecurityBulkLoadEndPoint set 777 permission on input data files
[
https://issues.apache.org/jira/browse/HBASE-12053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-12053:
---
Fix Version/s: (was: 0.98.7)
0.98.8
SecurityBulkLoadEndPoint set 777 permission on input data files
Key: HBASE-12053
URL: https://issues.apache.org/jira/browse/HBASE-12053
Project: HBase
Issue Type: Bug
Reporter: Jeffrey Zhong
Assignee: Jeffrey Zhong
Fix For: 2.0.0, 0.98.8, 0.99.1
Attachments: HBASE-12053.patch
We have code in SecureBulkLoadEndpoint#secureBulkLoadHFiles
{code}
LOG.trace(Setting permission for: + p);
fs.setPermission(p, PERM_ALL_ACCESS);
{code}
This is against the point we use staging folder for secure bulk load.
Currently we create a hidden staging folder which has ALL_ACCESS permission
and we use doAs to move input files into staging folder. Therefore, we
should not set 777 permission on the original input data files but files in
staging folder after move.
This may comprise security setting especially when there is an error we
move the file with 777 permission back.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12106) Move test annotations to test artifact
[ https://issues.apache.org/jira/browse/HBASE-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-12106: --- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to 0.98+ Move test annotations to test artifact -- Key: HBASE-12106 URL: https://issues.apache.org/jira/browse/HBASE-12106 Project: HBase Issue Type: Bug Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: 2.0.0, 0.98.7, 0.99.1 Attachments: hbase-12106_v1-0.98+0.99.patch, hbase-12106_v1.patch, hbase-12106_v1.patch, hbase-12106_v2.patch Test annotation interfaces used to be under hbase-common/src/test then moved to hbase-annotations/src/main. We should move them to hbase-annotations/src/test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11815) Flush and compaction could just close the tmp writer if there is an exception
[
https://issues.apache.org/jira/browse/HBASE-11815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161536#comment-14161536
]
Hudson commented on HBASE-11815:
FAILURE: Integrated in HBase-TRUNK #5627 (See
[https://builds.apache.org/job/HBase-TRUNK/5627/])
HBASE-11815 Flush and compaction could just close the tmp writer if there
(ramkrishna: rev eb6f196395b4462ebabbaf1049d919533ae1875f)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreFlusher.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/DefaultCompactor.java
Flush and compaction could just close the tmp writer if there is an exception
-
Key: HBASE-11815
URL: https://issues.apache.org/jira/browse/HBASE-11815
Project: HBase
Issue Type: Bug
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Priority: Trivial
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: HBASE-11815.patch, HBASE-11815_0.98.patch,
HBASE-11815_1.patch, HBASE-11815_2.patch, HBASE-11815_2.patch
A minor change.
{code}
try {
flushed = performFlush(scanner, writer, smallestReadPoint);
} finally {
finalizeWriter(writer, cacheFlushId, status);
}
{code}
Whenever there is a failure during flush we should close the writer but
adding the meta data and setting the status would not be needed.
{code}
status.setStatus(Flushing + store + : appending metadata);
writer.appendMetadata(cacheFlushSeqNum, false);
status.setStatus(Flushing + store + : closing flushed file);
writer.close();
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (HBASE-12039) Lower log level for TableNotFoundException log message when throwing
[ https://issues.apache.org/jira/browse/HBASE-12039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-12039. Resolution: Fixed Hadoop Flags: Reviewed Pushed to 0.94 and 0.98 Lower log level for TableNotFoundException log message when throwing Key: HBASE-12039 URL: https://issues.apache.org/jira/browse/HBASE-12039 Project: HBase Issue Type: Bug Reporter: James Taylor Assignee: stack Priority: Minor Fix For: 0.98.7, 0.94.25 Attachments: 12039-0.94.txt, 12039.txt Our HBase client tries to get the HTable descriptor for a table that may or may not exist. We catch and ignore the TableNotFoundException if it occurs, but the log message appear regardless of this which confuses our users. Would it be possible to lower the log level of this message since the exception is already being throw (making it up to the caller how they want to handle this). 14/09/20 20:01:54 WARN client.HConnectionManager$HConnectionImplementation: Encountered problems when prefetch META table: org.apache.hadoop.hbase.TableNotFoundException: Cannot find row in .META. for table: _IDX_TEST.TESTING, row=_IDX_TEST.TESTING,,99 at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:151) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:1059) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1121) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:1001) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:958) at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:251) at org.apache.hadoop.hbase.client.HTable.init(HTable.java:243) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[ https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-12016: --- Status: Open (was: Patch Available) Reduce number of versions in Meta table. Make it configurable - Key: HBASE-12016 URL: https://issues.apache.org/jira/browse/HBASE-12016 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Andrey Stepachev Assignee: Andrey Stepachev Priority: Minor Fix For: 2.0.0, 0.98.7, 0.99.1 Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch Currently meta keeps up to 10 versions of each KV. For big metas it leads to substantial memory overhead and scan slowdowns. (see https://issues.apache.org/jira/browse/HBASE-11165 ) Need to keep reasonable number of versions (suggested value is 3). Number of versions configurable via parameter: hbase.meta.versions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[ https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-12016: --- Fix Version/s: (was: 0.98.7) 0.98.8 Reduce number of versions in Meta table. Make it configurable - Key: HBASE-12016 URL: https://issues.apache.org/jira/browse/HBASE-12016 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Andrey Stepachev Assignee: Andrey Stepachev Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.1 Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch Currently meta keeps up to 10 versions of each KV. For big metas it leads to substantial memory overhead and scan slowdowns. (see https://issues.apache.org/jira/browse/HBASE-11165 ) Need to keep reasonable number of versions (suggested value is 3). Number of versions configurable via parameter: hbase.meta.versions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11996) Add Table Creator to the HTD
[ https://issues.apache.org/jira/browse/HBASE-11996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-11996: --- Fix Version/s: (was: 0.98.7) 0.98.8 Add Table Creator to the HTD -- Key: HBASE-11996 URL: https://issues.apache.org/jira/browse/HBASE-11996 Project: HBase Issue Type: New Feature Components: Admin, master, Operability Reporter: Matteo Bertozzi Assignee: Matteo Bertozzi Priority: Trivial Fix For: 2.0.0, 0.98.8, 0.99.1 It will be nice storing the user who created the table. It is useful in situations where you want to remove a table but you don't know who asking to. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[ https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161541#comment-14161541 ] Andrew Purtell commented on HBASE-12016: Unable to apply latest patch to trunk Reduce number of versions in Meta table. Make it configurable - Key: HBASE-12016 URL: https://issues.apache.org/jira/browse/HBASE-12016 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Andrey Stepachev Assignee: Andrey Stepachev Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.1 Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch Currently meta keeps up to 10 versions of each KV. For big metas it leads to substantial memory overhead and scan slowdowns. (see https://issues.apache.org/jira/browse/HBASE-11165 ) Need to keep reasonable number of versions (suggested value is 3). Number of versions configurable via parameter: hbase.meta.versions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11964) Improve spreading replication load from failed regionservers
[ https://issues.apache.org/jira/browse/HBASE-11964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-11964: --- Fix Version/s: (was: 0.98.7) 0.98.8 Improve spreading replication load from failed regionservers Key: HBASE-11964 URL: https://issues.apache.org/jira/browse/HBASE-11964 Project: HBase Issue Type: Sub-task Reporter: Andrew Purtell Assignee: Andrew Purtell Fix For: 2.0.0, 0.98.8, 0.99.1, 0.94.25 Attachments: HBASE-11964-0.98.patch, HBASE-11964-0.98.patch, HBASE-11964.patch, HBASE-11964.patch Improve replication source thread handling. Improve fanout when transferring queues. Ensure replication sources terminate properly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-9531) a command line (hbase shell) interface to retreive the replication metrics and show replication lag
[
https://issues.apache.org/jira/browse/HBASE-9531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-9531:
--
Fix Version/s: (was: 0.98.7)
0.98.8
a command line (hbase shell) interface to retreive the replication metrics
and show replication lag
---
Key: HBASE-9531
URL: https://issues.apache.org/jira/browse/HBASE-9531
Project: HBase
Issue Type: New Feature
Components: Replication
Affects Versions: 0.99.0
Reporter: Demai Ni
Assignee: Demai Ni
Fix For: 2.0.0, 0.98.8, 0.99.1
Attachments: HBASE-9531-master-v1.patch, HBASE-9531-master-v1.patch,
HBASE-9531-master-v1.patch, HBASE-9531-master-v2.patch,
HBASE-9531-master-v3.patch, HBASE-9531-master-v4.patch,
HBASE-9531-trunk-v0.patch, HBASE-9531-trunk-v0.patch
This jira is to provide a command line (hbase shell) interface to retreive
the replication metrics info such as:ageOfLastShippedOp,
timeStampsOfLastShippedOp, sizeOfLogQueue ageOfLastAppliedOp, and
timeStampsOfLastAppliedOp. And also to provide a point of time info of the
lag of replication(source only)
Understand that hbase is using Hadoop
metrics(http://hbase.apache.org/metrics.html), which is a common way to
monitor metric info. This Jira is to serve as a light-weight client
interface, comparing to a completed(certainly better, but heavier)GUI
monitoring package. I made the code works on 0.94.9 now, and like to use this
jira to get opinions about whether the feature is valuable to other
users/workshop. If so, I will build a trunk patch.
All inputs are greatly appreciated. Thank you!
The overall design is to reuse the existing logic which supports hbase shell
command 'status', and invent a new module, called ReplicationLoad. In
HRegionServer.buildServerLoad() , use the local replication service objects
to get their loads which could be wrapped in a ReplicationLoad object and
then simply pass it to the ServerLoad. In ReplicationSourceMetrics and
ReplicationSinkMetrics, a few getters and setters will be created, and ask
Replication to build a ReplicationLoad. (many thanks to Jean-Daniel for
his kindly suggestions through dev email list)
the replication lag will be calculated for source only, and use this formula:
{code:title=Replication lag|borderStyle=solid}
if sizeOfLogQueue != 0 then max(ageOfLastShippedOp, (current time -
timeStampsOfLastShippedOp)) //err on the large side
else if (current time - timeStampsOfLastShippedOp) 2*
ageOfLastShippedOp then lag = ageOfLastShippedOp // last shipped happen
recently
else lag = 0 // last shipped may happens last night, so NO real lag
although ageOfLastShippedOp is non-zero
{code}
External will look something like:
{code:title=status 'replication'|borderStyle=solid}
hbase(main):001:0 status 'replication'
version 0.94.9
3 live servers
hdtest017.svl.ibm.com:
SOURCE:PeerID=1, ageOfLastShippedOp=14, sizeOfLogQueue=0,
timeStampsOfLastShippedOp=Wed Sep 04 14:49:48 PDT 2013
SINK :AgeOfLastAppliedOp=0, TimeStampsOfLastAppliedOp=Wed Sep 04
14:48:48 PDT 2013
hdtest018.svl.ibm.com:
SOURCE:PeerID=1, ageOfLastShippedOp=0, sizeOfLogQueue=0,
timeStampsOfLastShippedOp=Wed Sep 04 14:48:48 PDT 2013
SINK :AgeOfLastAppliedOp=14, TimeStampsOfLastAppliedOp=Wed Sep 04
14:50:59 PDT 2013
hdtest015.svl.ibm.com:
SOURCE:PeerID=1, ageOfLastShippedOp=0, sizeOfLogQueue=0,
timeStampsOfLastShippedOp=Wed Sep 04 14:48:48 PDT 2013
SINK :AgeOfLastAppliedOp=0, TimeStampsOfLastAppliedOp=Wed Sep 04
14:48:48 PDT 2013
hbase(main):002:0 status 'replication','source'
version 0.94.9
3 live servers
hdtest017.svl.ibm.com:
SOURCE:PeerID=1, ageOfLastShippedOp=14, sizeOfLogQueue=0,
timeStampsOfLastShippedOp=Wed Sep 04 14:49:48 PDT 2013
hdtest018.svl.ibm.com:
SOURCE:PeerID=1, ageOfLastShippedOp=0, sizeOfLogQueue=0,
timeStampsOfLastShippedOp=Wed Sep 04 14:48:48 PDT 2013
hdtest015.svl.ibm.com:
SOURCE:PeerID=1, ageOfLastShippedOp=0, sizeOfLogQueue=0,
timeStampsOfLastShippedOp=Wed Sep 04 14:48:48 PDT 2013
hbase(main):003:0 status 'replication','sink'
version 0.94.9
3 live servers
hdtest017.svl.ibm.com:
SINK :AgeOfLastAppliedOp=0, TimeStampsOfLastAppliedOp=Wed Sep 04
14:48:48 PDT 2013
hdtest018.svl.ibm.com:
SINK :AgeOfLastAppliedOp=14, TimeStampsOfLastAppliedOp=Wed Sep 04
14:50:59 PDT 2013
hdtest015.svl.ibm.com:
SINK :AgeOfLastAppliedOp=0, TimeStampsOfLastAppliedOp=Wed Sep 04
14:48:48 PDT 2013
hbase(main):003:0 status 'replication','lag'
version 0.94.9
3 live servers
hdtest017.svl.ibm.com: lag = 0
[jira] [Updated] (HBASE-11962) Port HBASE-11897 Add append and remove peer table-cfs cmds for replication to 0.98
[ https://issues.apache.org/jira/browse/HBASE-11962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-11962: --- Fix Version/s: (was: 0.98.7) 0.98.8 Port HBASE-11897 Add append and remove peer table-cfs cmds for replication to 0.98 Key: HBASE-11962 URL: https://issues.apache.org/jira/browse/HBASE-11962 Project: HBase Issue Type: Improvement Reporter: Ted Yu Priority: Minor Fix For: 0.98.8 This issue is to backport the commands for appending and removing peer table-cfs for replication to 0.98 Two new commands, append_peer_tableCFs and remove_peer_tableCFs, are added to do the operation of adding and removing a table/table-column family. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11639) [Visibility controller] Replicate the visibility of Cells as strings
[ https://issues.apache.org/jira/browse/HBASE-11639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-11639: --- Fix Version/s: (was: 0.98.7) 0.98.8 [Visibility controller] Replicate the visibility of Cells as strings Key: HBASE-11639 URL: https://issues.apache.org/jira/browse/HBASE-11639 Project: HBase Issue Type: Improvement Components: Replication, security Affects Versions: 0.98.4 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Labels: VisibilityLabels Fix For: 2.0.0, 0.98.8, 0.99.1 This issue is aimed at persisting the visibility labels as strings in the WAL rather than Label ordinals. This would help in replicating the label ordinals to the replication cluster as strings directly and also that after HBASE-11553 would help because the replication cluster could have an implementation as string based visibility labels. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11692) Document how and why to do a manual region split
[
https://issues.apache.org/jira/browse/HBASE-11692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-11692:
Attachment: HBASE-11692-v1.patch
What I will commit, including feedback from stack
Document how and why to do a manual region split
Key: HBASE-11692
URL: https://issues.apache.org/jira/browse/HBASE-11692
Project: HBase
Issue Type: Task
Components: documentation
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
Attachments: HBASE-11692-v1.patch, HBASE-11692.patch
{quote}
-- Forwarded message --
From: Liu, Ming (HPIT-GADSC) ming.l...@hp.com
Date: Tue, Aug 5, 2014 at 11:28 PM
Subject: Why hbase need manual split?
To: u...@hbase.apache.org u...@hbase.apache.org
Hi, all,
As I understand, HBase will automatically split a region when the region is
too big.
So in what scenario, user needs to do a manual split? Could someone kindly
give me some examples that user need to do the region split explicitly via
HBase Shell or Java API?
Thanks very much.
Regards,
Ming
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12147) Porting Online Config Change from 89-fb
[ https://issues.apache.org/jira/browse/HBASE-12147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manukranth Kolloju updated HBASE-12147: --- Status: Patch Available (was: Open) Porting Online Config Change from 89-fb --- Key: HBASE-12147 URL: https://issues.apache.org/jira/browse/HBASE-12147 Project: HBase Issue Type: Sub-task Affects Versions: 1.0.0 Reporter: Manukranth Kolloju Assignee: Manukranth Kolloju Fix For: 1.0.0 Original Estimate: 168h Remaining Estimate: 168h This jira is to track the forward port of HBASE-8805 and HBASE-8544 implemented by [~gaurav.menghani] in 89-fb. This improves operational efficiency in managing clusters that are serving production traffic. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12147) Porting Online Config Change from 89-fb
[ https://issues.apache.org/jira/browse/HBASE-12147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manukranth Kolloju updated HBASE-12147: --- Attachment: 0001-Online-config-change.patch This is the initial patch, bringing together the Online Configuration with an application to update configs for compactions. Porting Online Config Change from 89-fb --- Key: HBASE-12147 URL: https://issues.apache.org/jira/browse/HBASE-12147 Project: HBase Issue Type: Sub-task Affects Versions: 1.0.0 Reporter: Manukranth Kolloju Assignee: Manukranth Kolloju Fix For: 1.0.0 Attachments: 0001-Online-config-change.patch Original Estimate: 168h Remaining Estimate: 168h This jira is to track the forward port of HBASE-8805 and HBASE-8544 implemented by [~gaurav.menghani] in 89-fb. This improves operational efficiency in managing clusters that are serving production traffic. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11692) Document how and why to do a manual region split
[
https://issues.apache.org/jira/browse/HBASE-11692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-11692:
Resolution: Fixed
Fix Version/s: 0.99.1
2.0.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Document how and why to do a manual region split
Key: HBASE-11692
URL: https://issues.apache.org/jira/browse/HBASE-11692
Project: HBase
Issue Type: Task
Components: documentation
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
Fix For: 2.0.0, 0.99.1
Attachments: HBASE-11692-v1.patch, HBASE-11692.patch
{quote}
-- Forwarded message --
From: Liu, Ming (HPIT-GADSC) ming.l...@hp.com
Date: Tue, Aug 5, 2014 at 11:28 PM
Subject: Why hbase need manual split?
To: u...@hbase.apache.org u...@hbase.apache.org
Hi, all,
As I understand, HBase will automatically split a region when the region is
too big.
So in what scenario, user needs to do a manual split? Could someone kindly
give me some examples that user need to do the region split explicitly via
HBase Shell or Java API?
Thanks very much.
Regards,
Ming
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11981) Document how to find the units of measure for a given HBase metric
[ https://issues.apache.org/jira/browse/HBASE-11981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-11981: Resolution: Fixed Fix Version/s: 0.99.1 2.0.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Document how to find the units of measure for a given HBase metric -- Key: HBASE-11981 URL: https://issues.apache.org/jira/browse/HBASE-11981 Project: HBase Issue Type: Task Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 2.0.0, 0.99.1 Attachments: HBASE-11981.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11791) Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload
[ https://issues.apache.org/jira/browse/HBASE-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-11791: Attachment: HBASE-11791-v18.patch Thanks all. v18 is what I will commit. I'll add it to the RB too for completeness. Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload --- Key: HBASE-11791 URL: https://issues.apache.org/jira/browse/HBASE-11791 Project: HBase Issue Type: Task Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Attachments: HBASE-11791-v1.patch, HBASE-11791-v10.patch, HBASE-11791-v11.patch, HBASE-11791-v12.patch, HBASE-11791-v13.patch, HBASE-11791-v14.patch, HBASE-11791-v15.patch, HBASE-11791-v16.patch, HBASE-11791-v17-rebased.patch, HBASE-11791-v17.patch, HBASE-11791-v18.patch, HBASE-11791-v2.patch, HBASE-11791-v3.patch, HBASE-11791-v4.patch, HBASE-11791-v5.patch, HBASE-11791-v6.patch, HBASE-11791-v7.patch, HBASE-11791-v9.patch, HBase Security Features Operators Guide - HBaseCon 2014 - v5.pptx, LDAPScanLabelGenerator.png Do a pass on the ACL and tag docs and make sure they are up to date and accurate, expand to cover HBASE-10885, HBASE-11001, HBASE-11002, HBASE-11434 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11791) Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload
[ https://issues.apache.org/jira/browse/HBASE-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-11791: Resolution: Fixed Fix Version/s: 2.0.0 Status: Resolved (was: Patch Available) Does not apply cleanly to branch-1. If it is important for it to go there, reopen and I will refactor it. Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload --- Key: HBASE-11791 URL: https://issues.apache.org/jira/browse/HBASE-11791 Project: HBase Issue Type: Task Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 2.0.0 Attachments: HBASE-11791-v1.patch, HBASE-11791-v10.patch, HBASE-11791-v11.patch, HBASE-11791-v12.patch, HBASE-11791-v13.patch, HBASE-11791-v14.patch, HBASE-11791-v15.patch, HBASE-11791-v16.patch, HBASE-11791-v17-rebased.patch, HBASE-11791-v17.patch, HBASE-11791-v18.patch, HBASE-11791-v2.patch, HBASE-11791-v3.patch, HBASE-11791-v4.patch, HBASE-11791-v5.patch, HBASE-11791-v6.patch, HBASE-11791-v7.patch, HBASE-11791-v9.patch, HBase Security Features Operators Guide - HBaseCon 2014 - v5.pptx, LDAPScanLabelGenerator.png Do a pass on the ACL and tag docs and make sure they are up to date and accurate, expand to cover HBASE-10885, HBASE-11001, HBASE-11002, HBASE-11434 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (HBASE-12106) Move test annotations to test artifact
[ https://issues.apache.org/jira/browse/HBASE-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell reopened HBASE-12106: I'm going to need to commit an addendum momentarily to get 'mvn test' passing with this change Move test annotations to test artifact -- Key: HBASE-12106 URL: https://issues.apache.org/jira/browse/HBASE-12106 Project: HBase Issue Type: Bug Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: 2.0.0, 0.98.7, 0.99.1 Attachments: hbase-12106_v1-0.98+0.99.patch, hbase-12106_v1.patch, hbase-12106_v1.patch, hbase-12106_v2.patch Test annotation interfaces used to be under hbase-common/src/test then moved to hbase-annotations/src/main. We should move them to hbase-annotations/src/test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12106) Move test annotations to test artifact
[
https://issues.apache.org/jira/browse/HBASE-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-12106:
---
Attachment: HBASE-12106-addendum.patch
Attached addendum I pushed to 0.98+. We need to add hbase-annotations as a
test-jar dep to hbase-testing-util or 'mvn test' will fail at that module. This
is from a 0.98 build:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test
(secondPartTestsExecution) on project hbase-testing-util: Execution
secondPartTestsExecution of goal
org.apache.maven.plugins:maven-surefire-plugin:2.12-TRUNK-HBASE-2:test failed:
java.lang.reflect.InvocationTargetException; nested exception is
java.lang.reflect.InvocationTargetException: null: Unable to load category:
org.apache.hadoop.hbase.MediumTests - [Help 1]
{noformat}
Move test annotations to test artifact
--
Key: HBASE-12106
URL: https://issues.apache.org/jira/browse/HBASE-12106
Project: HBase
Issue Type: Bug
Reporter: Enis Soztutar
Assignee: Enis Soztutar
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: HBASE-12106-addendum.patch,
hbase-12106_v1-0.98+0.99.patch, hbase-12106_v1.patch, hbase-12106_v1.patch,
hbase-12106_v2.patch
Test annotation interfaces used to be under hbase-common/src/test then moved
to hbase-annotations/src/main. We should move them to
hbase-annotations/src/test.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (HBASE-12106) Move test annotations to test artifact
[ https://issues.apache.org/jira/browse/HBASE-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-12106. Resolution: Fixed Move test annotations to test artifact -- Key: HBASE-12106 URL: https://issues.apache.org/jira/browse/HBASE-12106 Project: HBase Issue Type: Bug Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: 2.0.0, 0.99.1, 0.98.7 Attachments: HBASE-12106-addendum.patch, hbase-12106_v1-0.98+0.99.patch, hbase-12106_v1.patch, hbase-12106_v1.patch, hbase-12106_v2.patch Test annotation interfaces used to be under hbase-common/src/test then moved to hbase-annotations/src/main. We should move them to hbase-annotations/src/test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-10411) [Book] Add a kerberos 'request is a replay (34)' issue at troubleshooting section
[ https://issues.apache.org/jira/browse/HBASE-10411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161610#comment-14161610 ] Hudson commented on HBASE-10411: SUCCESS: Integrated in HBase-1.0 #280 (See [https://builds.apache.org/job/HBase-1.0/280/]) HBASE-10411 Add a kerberos 'request is a replay (34)' issue in the Troubleshooting chapter (Takeshi Miao) (mstanleyjones: rev 24cb52be3713ce183a69b5e83c0fad076c7a8639) * src/main/docbkx/troubleshooting.xml [Book] Add a kerberos 'request is a replay (34)' issue at troubleshooting section - Key: HBASE-10411 URL: https://issues.apache.org/jira/browse/HBASE-10411 Project: HBase Issue Type: Improvement Components: documentation, security Reporter: takeshi.miao Assignee: takeshi.miao Priority: Minor Fix For: 2.0.0, 0.99.1 Attachments: HBASE-10411-trunk-v01.patch, HBASE-10411-v01.odt For kerberos 'request is a replay (34)' issue (HBASE-10379), adding it to the troubleshooting section in HBase book -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11815) Flush and compaction could just close the tmp writer if there is an exception
[
https://issues.apache.org/jira/browse/HBASE-11815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161609#comment-14161609
]
Hudson commented on HBASE-11815:
SUCCESS: Integrated in HBase-1.0 #280 (See
[https://builds.apache.org/job/HBase-1.0/280/])
HBASE-11815 - Flush and compaction could just close the tmp writer if
(ramkrishna: rev de15b1fd98da9f960a782c4dd2c0cd1dd852cf7c)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/DefaultCompactor.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreFlusher.java
Flush and compaction could just close the tmp writer if there is an exception
-
Key: HBASE-11815
URL: https://issues.apache.org/jira/browse/HBASE-11815
Project: HBase
Issue Type: Bug
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Priority: Trivial
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: HBASE-11815.patch, HBASE-11815_0.98.patch,
HBASE-11815_1.patch, HBASE-11815_2.patch, HBASE-11815_2.patch
A minor change.
{code}
try {
flushed = performFlush(scanner, writer, smallestReadPoint);
} finally {
finalizeWriter(writer, cacheFlushId, status);
}
{code}
Whenever there is a failure during flush we should close the writer but
adding the meta data and setting the status would not be needed.
{code}
status.setStatus(Flushing + store + : appending metadata);
writer.appendMetadata(cacheFlushSeqNum, false);
status.setStatus(Flushing + store + : closing flushed file);
writer.close();
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-9005) Improve documentation around KEEP_DELETED_CELLS, time range scans, and delete markers
[ https://issues.apache.org/jira/browse/HBASE-9005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161611#comment-14161611 ] Hudson commented on HBASE-9005: --- SUCCESS: Integrated in HBase-1.0 #280 (See [https://builds.apache.org/job/HBase-1.0/280/]) HBASE-9005 Improve documentation around KEEP_DELETED_CELLS, time range scans, and delete markers (mstanleyjones: rev 226873f1ae2050320bac3834a4ec6f097a7de8a7) * src/main/docbkx/schema_design.xml Improve documentation around KEEP_DELETED_CELLS, time range scans, and delete markers - Key: HBASE-9005 URL: https://issues.apache.org/jira/browse/HBASE-9005 Project: HBase Issue Type: Bug Components: documentation Reporter: Lars Hofhansl Assignee: Misty Stanley-Jones Priority: Minor Fix For: 2.0.0, 0.99.1 Attachments: 9005.txt, HBASE-9005-1.patch, HBASE-9005-v1.patch Without KEEP_DELETED_CELLS all timerange queries are broken if their range covers a delete marker. As some internal discussions with colleagues showed, this feature is not well understand and documented. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12106) Move test annotations to test artifact
[ https://issues.apache.org/jira/browse/HBASE-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161617#comment-14161617 ] Hudson commented on HBASE-12106: FAILURE: Integrated in HBase-0.98 #580 (See [https://builds.apache.org/job/HBase-0.98/580/]) HBASE-12106 Move test annotations to test artifact (Enis Soztutar) (apurtell: rev 9efe354798d75f6b68c9e5e9cdef5fdff66b6e7c) * hbase-thrift/pom.xml * hbase-annotations/src/main/java/org/apache/hadoop/hbase/MediumTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/IntegrationTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/LargeTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/LargeTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/SmallTests.java * pom.xml * hbase-annotations/src/test/java/org/apache/hadoop/hbase/SmallTests.java * hbase-client/pom.xml * hbase-server/pom.xml * hbase-prefix-tree/pom.xml * hbase-annotations/src/test/java/org/apache/hadoop/hbase/IntegrationTests.java * hbase-examples/pom.xml * hbase-annotations/src/test/java/org/apache/hadoop/hbase/MediumTests.java * hbase-shell/pom.xml * hbase-it/pom.xml * hbase-common/pom.xml Move test annotations to test artifact -- Key: HBASE-12106 URL: https://issues.apache.org/jira/browse/HBASE-12106 Project: HBase Issue Type: Bug Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: 2.0.0, 0.98.7, 0.99.1 Attachments: HBASE-12106-addendum.patch, hbase-12106_v1-0.98+0.99.patch, hbase-12106_v1.patch, hbase-12106_v1.patch, hbase-12106_v2.patch Test annotation interfaces used to be under hbase-common/src/test then moved to hbase-annotations/src/main. We should move them to hbase-annotations/src/test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12039) Lower log level for TableNotFoundException log message when throwing
[ https://issues.apache.org/jira/browse/HBASE-12039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161618#comment-14161618 ] Hudson commented on HBASE-12039: FAILURE: Integrated in HBase-0.98 #580 (See [https://builds.apache.org/job/HBase-0.98/580/]) HBASE-12039 Lower log level for TableNotFoundException log message when throwing (stack) (apurtell: rev 2cf4df0e4c816fe95a5750e539935686ba5a5f3f) * hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java Lower log level for TableNotFoundException log message when throwing Key: HBASE-12039 URL: https://issues.apache.org/jira/browse/HBASE-12039 Project: HBase Issue Type: Bug Reporter: James Taylor Assignee: stack Priority: Minor Fix For: 0.98.7, 0.94.25 Attachments: 12039-0.94.txt, 12039.txt Our HBase client tries to get the HTable descriptor for a table that may or may not exist. We catch and ignore the TableNotFoundException if it occurs, but the log message appear regardless of this which confuses our users. Would it be possible to lower the log level of this message since the exception is already being throw (making it up to the caller how they want to handle this). 14/09/20 20:01:54 WARN client.HConnectionManager$HConnectionImplementation: Encountered problems when prefetch META table: org.apache.hadoop.hbase.TableNotFoundException: Cannot find row in .META. for table: _IDX_TEST.TESTING, row=_IDX_TEST.TESTING,,99 at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:151) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:1059) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1121) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:1001) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:958) at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:251) at org.apache.hadoop.hbase.client.HTable.init(HTable.java:243) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11815) Flush and compaction could just close the tmp writer if there is an exception
[
https://issues.apache.org/jira/browse/HBASE-11815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161622#comment-14161622
]
Hudson commented on HBASE-11815:
SUCCESS: Integrated in HBase-0.98-on-Hadoop-1.1 #550 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/550/])
HBASE-11815 - Flush and compaction could just close the tmp writer if
(ramkrishna: rev 401996efdb60b0f3395eca2bd2f5215cd33346bb)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/DefaultCompactor.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreFlusher.java
Flush and compaction could just close the tmp writer if there is an exception
-
Key: HBASE-11815
URL: https://issues.apache.org/jira/browse/HBASE-11815
Project: HBase
Issue Type: Bug
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Priority: Trivial
Fix For: 2.0.0, 0.98.7, 0.99.1
Attachments: HBASE-11815.patch, HBASE-11815_0.98.patch,
HBASE-11815_1.patch, HBASE-11815_2.patch, HBASE-11815_2.patch
A minor change.
{code}
try {
flushed = performFlush(scanner, writer, smallestReadPoint);
} finally {
finalizeWriter(writer, cacheFlushId, status);
}
{code}
Whenever there is a failure during flush we should close the writer but
adding the meta data and setting the status would not be needed.
{code}
status.setStatus(Flushing + store + : appending metadata);
writer.appendMetadata(cacheFlushSeqNum, false);
status.setStatus(Flushing + store + : closing flushed file);
writer.close();
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12039) Lower log level for TableNotFoundException log message when throwing
[ https://issues.apache.org/jira/browse/HBASE-12039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161627#comment-14161627 ] Hudson commented on HBASE-12039: SUCCESS: Integrated in HBase-0.94 #1432 (See [https://builds.apache.org/job/HBase-0.94/1432/]) HBASE-12039 Lower log level for TableNotFoundException log message when throwing (stack) (apurtell: rev f8bc9fd0cdcb484dfb1decf75bbc0ddaf0d67388) * src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java Lower log level for TableNotFoundException log message when throwing Key: HBASE-12039 URL: https://issues.apache.org/jira/browse/HBASE-12039 Project: HBase Issue Type: Bug Reporter: James Taylor Assignee: stack Priority: Minor Fix For: 0.98.7, 0.94.25 Attachments: 12039-0.94.txt, 12039.txt Our HBase client tries to get the HTable descriptor for a table that may or may not exist. We catch and ignore the TableNotFoundException if it occurs, but the log message appear regardless of this which confuses our users. Would it be possible to lower the log level of this message since the exception is already being throw (making it up to the caller how they want to handle this). 14/09/20 20:01:54 WARN client.HConnectionManager$HConnectionImplementation: Encountered problems when prefetch META table: org.apache.hadoop.hbase.TableNotFoundException: Cannot find row in .META. for table: _IDX_TEST.TESTING, row=_IDX_TEST.TESTING,,99 at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:151) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:1059) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1121) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:1001) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:958) at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:251) at org.apache.hadoop.hbase.client.HTable.init(HTable.java:243) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12039) Lower log level for TableNotFoundException log message when throwing
[ https://issues.apache.org/jira/browse/HBASE-12039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161632#comment-14161632 ] Hudson commented on HBASE-12039: FAILURE: Integrated in HBase-0.94-security #546 (See [https://builds.apache.org/job/HBase-0.94-security/546/]) HBASE-12039 Lower log level for TableNotFoundException log message when throwing (stack) (apurtell: rev f8bc9fd0cdcb484dfb1decf75bbc0ddaf0d67388) * src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java Lower log level for TableNotFoundException log message when throwing Key: HBASE-12039 URL: https://issues.apache.org/jira/browse/HBASE-12039 Project: HBase Issue Type: Bug Reporter: James Taylor Assignee: stack Priority: Minor Fix For: 0.98.7, 0.94.25 Attachments: 12039-0.94.txt, 12039.txt Our HBase client tries to get the HTable descriptor for a table that may or may not exist. We catch and ignore the TableNotFoundException if it occurs, but the log message appear regardless of this which confuses our users. Would it be possible to lower the log level of this message since the exception is already being throw (making it up to the caller how they want to handle this). 14/09/20 20:01:54 WARN client.HConnectionManager$HConnectionImplementation: Encountered problems when prefetch META table: org.apache.hadoop.hbase.TableNotFoundException: Cannot find row in .META. for table: _IDX_TEST.TESTING, row=_IDX_TEST.TESTING,,99 at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:151) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:1059) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1121) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:1001) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:958) at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:251) at org.apache.hadoop.hbase.client.HTable.init(HTable.java:243) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12039) Lower log level for TableNotFoundException log message when throwing
[ https://issues.apache.org/jira/browse/HBASE-12039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161633#comment-14161633 ] Hudson commented on HBASE-12039: SUCCESS: Integrated in HBase-0.94-JDK7 #201 (See [https://builds.apache.org/job/HBase-0.94-JDK7/201/]) HBASE-12039 Lower log level for TableNotFoundException log message when throwing (stack) (apurtell: rev f8bc9fd0cdcb484dfb1decf75bbc0ddaf0d67388) * src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java Lower log level for TableNotFoundException log message when throwing Key: HBASE-12039 URL: https://issues.apache.org/jira/browse/HBASE-12039 Project: HBase Issue Type: Bug Reporter: James Taylor Assignee: stack Priority: Minor Fix For: 0.98.7, 0.94.25 Attachments: 12039-0.94.txt, 12039.txt Our HBase client tries to get the HTable descriptor for a table that may or may not exist. We catch and ignore the TableNotFoundException if it occurs, but the log message appear regardless of this which confuses our users. Would it be possible to lower the log level of this message since the exception is already being throw (making it up to the caller how they want to handle this). 14/09/20 20:01:54 WARN client.HConnectionManager$HConnectionImplementation: Encountered problems when prefetch META table: org.apache.hadoop.hbase.TableNotFoundException: Cannot find row in .META. for table: _IDX_TEST.TESTING, row=_IDX_TEST.TESTING,,99 at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:151) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:1059) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1121) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:1001) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:958) at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:251) at org.apache.hadoop.hbase.client.HTable.init(HTable.java:243) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11791) Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload
[ https://issues.apache.org/jira/browse/HBASE-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161635#comment-14161635 ] Anoop Sam John commented on HBASE-11791: Doc we normally commit to master alone. 0.99 release will copy it while RC. Am I wrong? Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload --- Key: HBASE-11791 URL: https://issues.apache.org/jira/browse/HBASE-11791 Project: HBase Issue Type: Task Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 2.0.0 Attachments: HBASE-11791-v1.patch, HBASE-11791-v10.patch, HBASE-11791-v11.patch, HBASE-11791-v12.patch, HBASE-11791-v13.patch, HBASE-11791-v14.patch, HBASE-11791-v15.patch, HBASE-11791-v16.patch, HBASE-11791-v17-rebased.patch, HBASE-11791-v17.patch, HBASE-11791-v18.patch, HBASE-11791-v2.patch, HBASE-11791-v3.patch, HBASE-11791-v4.patch, HBASE-11791-v5.patch, HBASE-11791-v6.patch, HBASE-11791-v7.patch, HBASE-11791-v9.patch, HBase Security Features Operators Guide - HBaseCon 2014 - v5.pptx, LDAPScanLabelGenerator.png Do a pass on the ACL and tag docs and make sure they are up to date and accurate, expand to cover HBASE-10885, HBASE-11001, HBASE-11002, HBASE-11434 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11981) Document how to find the units of measure for a given HBase metric
[ https://issues.apache.org/jira/browse/HBASE-11981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161637#comment-14161637 ] Hudson commented on HBASE-11981: SUCCESS: Integrated in HBase-TRUNK #5628 (See [https://builds.apache.org/job/HBase-TRUNK/5628/]) HBASE-11981 Document how to find the units of measure for a given HBase metric (mstanleyjones: rev 64df10b61b26111a15e8c3cf168d8f11a8da7c1d) * src/main/docbkx/ops_mgt.xml Document how to find the units of measure for a given HBase metric -- Key: HBASE-11981 URL: https://issues.apache.org/jira/browse/HBASE-11981 Project: HBase Issue Type: Task Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 2.0.0, 0.99.1 Attachments: HBASE-11981.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11692) Document how and why to do a manual region split
[
https://issues.apache.org/jira/browse/HBASE-11692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161638#comment-14161638
]
Hudson commented on HBASE-11692:
SUCCESS: Integrated in HBase-TRUNK #5628 (See
[https://builds.apache.org/job/HBase-TRUNK/5628/])
HBASE-11692 Document how and why to do a manual region split (mstanleyjones:
rev a3b65c45ad3c55fc5ce12e6d69701a2bcd84f055)
* src/main/docbkx/performance.xml
* src/main/docbkx/ops_mgt.xml
* src/main/docbkx/book.xml
* src/main/docbkx/configuration.xml
Document how and why to do a manual region split
Key: HBASE-11692
URL: https://issues.apache.org/jira/browse/HBASE-11692
Project: HBase
Issue Type: Task
Components: documentation
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
Fix For: 2.0.0, 0.99.1
Attachments: HBASE-11692-v1.patch, HBASE-11692.patch
{quote}
-- Forwarded message --
From: Liu, Ming (HPIT-GADSC) ming.l...@hp.com
Date: Tue, Aug 5, 2014 at 11:28 PM
Subject: Why hbase need manual split?
To: u...@hbase.apache.org u...@hbase.apache.org
Hi, all,
As I understand, HBase will automatically split a region when the region is
too big.
So in what scenario, user needs to do a manual split? Could someone kindly
give me some examples that user need to do the region split explicitly via
HBase Shell or Java API?
Thanks very much.
Regards,
Ming
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12106) Move test annotations to test artifact
[ https://issues.apache.org/jira/browse/HBASE-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161639#comment-14161639 ] Hudson commented on HBASE-12106: SUCCESS: Integrated in HBase-TRUNK #5628 (See [https://builds.apache.org/job/HBase-TRUNK/5628/]) HBASE-12106 Move test annotations to test artifact (Enis Soztutar) (apurtell: rev 3557a3235210b178d9c6cd3355c68d0a7155243e) * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/VerySlowMapReduceTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/IntegrationTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/IOTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/CoprocessorTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/MapReduceTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/MediumTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/CoprocessorTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/FlakeyTests.java * hbase-server/pom.xml * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/VerySlowRegionServerTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/RestTests.java * pom.xml * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/VerySlowRegionServerTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/FilterTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/MiscTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/FlakeyTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/MiscTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/RPCTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/RegionServerTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/LargeTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/RestTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/RegionServerTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/ClientTests.java * hbase-prefix-tree/pom.xml * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/MapReduceTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/ClientTests.java * hbase-common/pom.xml * hbase-client/pom.xml * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/IntegrationTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/FilterTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/SmallTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/MasterTests.java * hbase-it/pom.xml * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/RPCTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/SmallTests.java * hbase-thrift/pom.xml * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/ReplicationTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/VerySlowMapReduceTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/SecurityTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/testclassification/MasterTests.java * hbase-shell/pom.xml * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/ReplicationTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/MediumTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/SecurityTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/IOTests.java * hbase-examples/pom.xml * hbase-annotations/src/main/java/org/apache/hadoop/hbase/testclassification/LargeTests.java Move test annotations to test artifact -- Key: HBASE-12106 URL: https://issues.apache.org/jira/browse/HBASE-12106 Project: HBase Issue Type: Bug Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: 2.0.0, 0.98.7, 0.99.1 Attachments: HBASE-12106-addendum.patch, hbase-12106_v1-0.98+0.99.patch, hbase-12106_v1.patch, hbase-12106_v1.patch, hbase-12106_v2.patch Test annotation interfaces used to be under hbase-common/src/test then moved to hbase-annotations/src/main. We should move them to
[jira] [Commented] (HBASE-12147) Porting Online Config Change from 89-fb
[
https://issues.apache.org/jira/browse/HBASE-12147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161640#comment-14161640
]
Hadoop QA commented on HBASE-12147:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12673302/0001-Online-config-change.patch
against trunk revision .
ATTACHMENT ID: 12673302
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 12 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2
warning messages.
{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 site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.util.TestHBaseFsck
org.apache.hadoop.hbase.TestZooKeeper
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11233//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11233//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11233//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11233//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11233//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11233//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11233//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11233//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11233//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11233//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11233//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11233//artifact/trunk/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11233//console
This message is automatically generated.
Porting Online Config Change from 89-fb
---
Key: HBASE-12147
URL: https://issues.apache.org/jira/browse/HBASE-12147
Project: HBase
Issue Type: Sub-task
Affects Versions: 1.0.0
Reporter: Manukranth Kolloju
Assignee: Manukranth Kolloju
Fix For: 1.0.0
Attachments: 0001-Online-config-change.patch
Original Estimate: 168h
Remaining Estimate: 168h
This jira is to track the forward port of HBASE-8805 and HBASE-8544
implemented by [~gaurav.menghani] in 89-fb. This improves operational
efficiency in managing clusters that are serving production traffic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[ https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated HBASE-12016: - Attachment: HBASE-12016.patch Reduce number of versions in Meta table. Make it configurable - Key: HBASE-12016 URL: https://issues.apache.org/jira/browse/HBASE-12016 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Andrey Stepachev Assignee: Andrey Stepachev Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.1 Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch Currently meta keeps up to 10 versions of each KV. For big metas it leads to substantial memory overhead and scan slowdowns. (see https://issues.apache.org/jira/browse/HBASE-11165 ) Need to keep reasonable number of versions (suggested value is 3). Number of versions configurable via parameter: hbase.meta.versions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[ https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated HBASE-12016: - Status: Patch Available (was: Open) Reduce number of versions in Meta table. Make it configurable - Key: HBASE-12016 URL: https://issues.apache.org/jira/browse/HBASE-12016 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Andrey Stepachev Assignee: Andrey Stepachev Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.1 Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch Currently meta keeps up to 10 versions of each KV. For big metas it leads to substantial memory overhead and scan slowdowns. (see https://issues.apache.org/jira/browse/HBASE-11165 ) Need to keep reasonable number of versions (suggested value is 3). Number of versions configurable via parameter: hbase.meta.versions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-10974) Improve DBEs read performance by avoiding byte array deep copies for key[] and value[]
[ https://issues.apache.org/jira/browse/HBASE-10974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161646#comment-14161646 ] ramkrishna.s.vasudevan commented on HBASE-10974: [~saint@gmail.com] This patch tries to avoid repeated key[] to be copied. But for this patch to proceed we may have to find what could be the actual key length in that block so that we could create a key[] of that size and copy key to it. Currently the copy happens to a 512 bytes size byte[] and this expands if needed. (Here a copy happens again). Improve DBEs read performance by avoiding byte array deep copies for key[] and value[] -- Key: HBASE-10974 URL: https://issues.apache.org/jira/browse/HBASE-10974 Project: HBase Issue Type: Improvement Components: Scanners Affects Versions: 0.99.0 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 0.99.1 Attachments: HBASE-10974_1.patch As part of HBASE-10801, we tried to reduce the copy of the value [] in forming the KV from the DBEs. The keys required copying and this was restricting us in using Cells and always wanted to copy to be done. The idea here is to replace the key byte[] as ByteBuffer and create a consecutive stream of the keys (currently the same byte[] is used and hence the copy). Use offset and length to track this key bytebuffer. The copy of the encoded format to normal Key format is definitely needed and can't be avoided but we could always avoid the deep copy of the bytes to form a KV and thus use cells effectively. Working on a patch, will post it soon. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11791) Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload
[
https://issues.apache.org/jira/browse/HBASE-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161648#comment-14161648
]
Hadoop QA commented on HBASE-11791:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12673304/HBASE-11791-v18.patch
against trunk revision .
ATTACHMENT ID: 12673304
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 7 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{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:
+ valueorg.apache.hadoop.hbase.security.access.AccessController,
org.apache.hadoop.hbase.security.token.TokenProvider/value
+
filenamehbase-server/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessController.java/filename
+
filenamehbase-server/src/test/java/org/apache/hadoop/hbase/security/access/SecureTestUtil.java/filename./para
+ screenhbase userinputgrant 'service', 'RWXCA',
'@test-NS'/userinput/screen
+ screenhbase userinputgrant '@developers', 'RW', 'user',
'i'/userinput/screen
+ screenhbase userinputgrant 'service, 'RW', 'user', 'i',
'foo'/userinput/screen
+ paraHBase Shell support for granting and revoking access is
for testing and verification
+
filenamehbase-client/src/test/java/org/apache/hadoop/hbase/client/TestScan.java/filename.
+
filenamehbase-server/src/test/java/org/apache/hadoop/hbase/security/visibility/TestVisibilityLabelsWithCustomVisLabService.java/filename
+
filenamehbase-server/src/test/java/org/apache/hadoop/hbase/security/visibility/TestVisibilityLabels.java/filename.
{color:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11234//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11234//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11234//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11234//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11234//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11234//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11234//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11234//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11234//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11234//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11234//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11234//console
This message is automatically generated.
Update docs on visibility tags and ACLs, transparent encryption, secure bulk
upload
---
Key: HBASE-11791
URL: https://issues.apache.org/jira/browse/HBASE-11791
Project: HBase
Issue Type: Task
Components: documentation
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
Fix For: 2.0.0
Attachments: HBASE-11791-v1.patch, HBASE-11791-v10.patch,
HBASE-11791-v11.patch, HBASE-11791-v12.patch, HBASE-11791-v13.patch,
HBASE-11791-v14.patch, HBASE-11791-v15.patch, HBASE-11791-v16.patch,
[jira] [Commented] (HBASE-12106) Move test annotations to test artifact
[ https://issues.apache.org/jira/browse/HBASE-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161690#comment-14161690 ] Hudson commented on HBASE-12106: SUCCESS: Integrated in HBase-TRUNK #5629 (See [https://builds.apache.org/job/HBase-TRUNK/5629/]) Amend HBASE-12106 Move test annotations to test artifact (Enis Soztutar) (apurtell: rev da440d586eb1e1f0fff8e0f427fd3ff729fd8f51) * hbase-testing-util/pom.xml Move test annotations to test artifact -- Key: HBASE-12106 URL: https://issues.apache.org/jira/browse/HBASE-12106 Project: HBase Issue Type: Bug Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: 2.0.0, 0.98.7, 0.99.1 Attachments: HBASE-12106-addendum.patch, hbase-12106_v1-0.98+0.99.patch, hbase-12106_v1.patch, hbase-12106_v1.patch, hbase-12106_v2.patch Test annotation interfaces used to be under hbase-common/src/test then moved to hbase-annotations/src/main. We should move them to hbase-annotations/src/test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11791) Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload
[ https://issues.apache.org/jira/browse/HBASE-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161691#comment-14161691 ] Hudson commented on HBASE-11791: SUCCESS: Integrated in HBase-TRUNK #5629 (See [https://builds.apache.org/job/HBase-TRUNK/5629/]) HBASE-11791 Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload (mstanleyjones: rev 38bc5360c598e632b9e901c34ba261be6eb43580) * src/main/docbkx/security.xml * src/main/docbkx/book.xml Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload --- Key: HBASE-11791 URL: https://issues.apache.org/jira/browse/HBASE-11791 Project: HBase Issue Type: Task Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 2.0.0 Attachments: HBASE-11791-v1.patch, HBASE-11791-v10.patch, HBASE-11791-v11.patch, HBASE-11791-v12.patch, HBASE-11791-v13.patch, HBASE-11791-v14.patch, HBASE-11791-v15.patch, HBASE-11791-v16.patch, HBASE-11791-v17-rebased.patch, HBASE-11791-v17.patch, HBASE-11791-v18.patch, HBASE-11791-v2.patch, HBASE-11791-v3.patch, HBASE-11791-v4.patch, HBASE-11791-v5.patch, HBASE-11791-v6.patch, HBASE-11791-v7.patch, HBASE-11791-v9.patch, HBase Security Features Operators Guide - HBaseCon 2014 - v5.pptx, LDAPScanLabelGenerator.png Do a pass on the ACL and tag docs and make sure they are up to date and accurate, expand to cover HBASE-10885, HBASE-11001, HBASE-11002, HBASE-11434 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12106) Move test annotations to test artifact
[ https://issues.apache.org/jira/browse/HBASE-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161705#comment-14161705 ] Hudson commented on HBASE-12106: FAILURE: Integrated in HBase-0.98 #581 (See [https://builds.apache.org/job/HBase-0.98/581/]) Amend HBASE-12106 Move test annotations to test artifact (Enis Soztutar) (apurtell: rev f3860bc376cf0a80ef3abb07b8bed1d529d354cc) * hbase-testing-util/pom.xml Move test annotations to test artifact -- Key: HBASE-12106 URL: https://issues.apache.org/jira/browse/HBASE-12106 Project: HBase Issue Type: Bug Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: 2.0.0, 0.98.7, 0.99.1 Attachments: HBASE-12106-addendum.patch, hbase-12106_v1-0.98+0.99.patch, hbase-12106_v1.patch, hbase-12106_v1.patch, hbase-12106_v2.patch Test annotation interfaces used to be under hbase-common/src/test then moved to hbase-annotations/src/main. We should move them to hbase-annotations/src/test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12185) Deadlock in HConnectionManager$HConnectionImplementation
Michael Tamm created HBASE-12185:
Summary: Deadlock in HConnectionManager$HConnectionImplementation
Key: HBASE-12185
URL: https://issues.apache.org/jira/browse/HBASE-12185
Project: HBase
Issue Type: Bug
Components: Client
Affects Versions: 0.94.2
Environment: CDH 4.2.0
Reporter: Michael Tamm
Priority: Critical
Here you can see the relevant section of a thread dump:
{noformat}
Found one Java-level deadlock:
=
AsyncSave-700512-Worker-EventThread:
waiting to lock monitor 0x7f8d90eecd20 (object 0x0005c0a8e1d0, a
org.apache.hadoop.hbase.zookeeper.RootRegionTracker),
which is held by AsyncSave-700546-Worker
AsyncSave-700546-Worker:
waiting to lock monitor 0x7f8d90149700 (object 0x000571404180, a
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation),
which is held by AsyncSave-700512-Worker-EventThread
Java stack information for the threads listed above:
===
AsyncSave-700512-Worker-EventThread:
at
org.apache.hadoop.hbase.zookeeper.ZooKeeperNodeTracker.stop(ZooKeeperNodeTracker.java:98)
- waiting to lock 0x0005c0a8e1d0 (a
org.apache.hadoop.hbase.zookeeper.RootRegionTracker)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.resetZooKeeperTrackers(HConnectionManager.java:603)
- locked 0x000571404180 (a
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.abort(HConnectionManager.java:1681)
at
org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher.connectionEvent(ZooKeeperWatcher.java:389)
at
org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher.process(ZooKeeperWatcher.java:286)
at
org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:519)
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:495)
AsyncSave-700546-Worker:
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.resetZooKeeperTrackers(HConnectionManager.java:598)
- waiting to lock 0x000571404180 (a
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.abort(HConnectionManager.java:1681)
at
org.apache.hadoop.hbase.zookeeper.ZooKeeperNodeTracker.blockUntilAvailable(ZooKeeperNodeTracker.java:132)
- locked 0x0005c0a8e1d0 (a
org.apache.hadoop.hbase.zookeeper.RootRegionTracker)
at
org.apache.hadoop.hbase.zookeeper.RootRegionTracker.waitRootRegionLocation(RootRegionTracker.java:83)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:841)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:954)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:852)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:954)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:856)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:813)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1503)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1388)
at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:955)
at
org.apache.hadoop.hbase.client.HTablePool$PooledHTable.flushCommits(HTablePool.java:449)
at ...
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11981) Document how to find the units of measure for a given HBase metric
[ https://issues.apache.org/jira/browse/HBASE-11981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161713#comment-14161713 ] Hudson commented on HBASE-11981: SUCCESS: Integrated in HBase-1.0 #281 (See [https://builds.apache.org/job/HBase-1.0/281/]) HBASE-11981 Document how to find the units of measure for a given HBase metric (mstanleyjones: rev 7525fa93869c7343c80b7b64344dcb520b8e9fdf) * src/main/docbkx/ops_mgt.xml Document how to find the units of measure for a given HBase metric -- Key: HBASE-11981 URL: https://issues.apache.org/jira/browse/HBASE-11981 Project: HBase Issue Type: Task Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 2.0.0, 0.99.1 Attachments: HBASE-11981.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12106) Move test annotations to test artifact
[ https://issues.apache.org/jira/browse/HBASE-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161715#comment-14161715 ] Hudson commented on HBASE-12106: SUCCESS: Integrated in HBase-1.0 #281 (See [https://builds.apache.org/job/HBase-1.0/281/]) HBASE-12106 Move test annotations to test artifact (Enis Soztutar) (apurtell: rev 695261c4a9704f043fb006caa24a8eada1656ae1) * pom.xml * hbase-annotations/src/test/java/org/apache/hadoop/hbase/LargeTests.java * hbase-server/pom.xml * hbase-annotations/src/main/java/org/apache/hadoop/hbase/IntegrationTests.java * hbase-it/pom.xml * hbase-thrift/pom.xml * hbase-annotations/src/test/java/org/apache/hadoop/hbase/MediumTests.java * hbase-common/pom.xml * hbase-client/pom.xml * hbase-examples/pom.xml * hbase-annotations/src/main/java/org/apache/hadoop/hbase/LargeTests.java * hbase-prefix-tree/pom.xml * hbase-annotations/src/main/java/org/apache/hadoop/hbase/SmallTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/SmallTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/IntegrationTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/MediumTests.java * hbase-shell/pom.xml Amend HBASE-12106 Move test annotations to test artifact (Enis Soztutar) (apurtell: rev e323a484d95f59fa9e7c522e209eee69e9abc8a8) * hbase-testing-util/pom.xml Move test annotations to test artifact -- Key: HBASE-12106 URL: https://issues.apache.org/jira/browse/HBASE-12106 Project: HBase Issue Type: Bug Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: 2.0.0, 0.98.7, 0.99.1 Attachments: HBASE-12106-addendum.patch, hbase-12106_v1-0.98+0.99.patch, hbase-12106_v1.patch, hbase-12106_v1.patch, hbase-12106_v2.patch Test annotation interfaces used to be under hbase-common/src/test then moved to hbase-annotations/src/main. We should move them to hbase-annotations/src/test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11692) Document how and why to do a manual region split
[
https://issues.apache.org/jira/browse/HBASE-11692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161714#comment-14161714
]
Hudson commented on HBASE-11692:
SUCCESS: Integrated in HBase-1.0 #281 (See
[https://builds.apache.org/job/HBase-1.0/281/])
HBASE-11692 Document how and why to do a manual region split (mstanleyjones:
rev 141e31b7bdc96b8be57b057c513c370010dfdff3)
* src/main/docbkx/configuration.xml
* src/main/docbkx/book.xml
* src/main/docbkx/performance.xml
* src/main/docbkx/ops_mgt.xml
Document how and why to do a manual region split
Key: HBASE-11692
URL: https://issues.apache.org/jira/browse/HBASE-11692
Project: HBase
Issue Type: Task
Components: documentation
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
Fix For: 2.0.0, 0.99.1
Attachments: HBASE-11692-v1.patch, HBASE-11692.patch
{quote}
-- Forwarded message --
From: Liu, Ming (HPIT-GADSC) ming.l...@hp.com
Date: Tue, Aug 5, 2014 at 11:28 PM
Subject: Why hbase need manual split?
To: u...@hbase.apache.org u...@hbase.apache.org
Hi, all,
As I understand, HBase will automatically split a region when the region is
too big.
So in what scenario, user needs to do a manual split? Could someone kindly
give me some examples that user need to do the region split explicitly via
HBase Shell or Java API?
Thanks very much.
Regards,
Ming
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-12186) Formatting error in Table 8.2. Examples of Visibility Expressions
Misty Stanley-Jones created HBASE-12186: --- Summary: Formatting error in Table 8.2. Examples of Visibility Expressions Key: HBASE-12186 URL: https://issues.apache.org/jira/browse/HBASE-12186 Project: HBase Issue Type: Bug Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones The value of one of the cells of the table got lost somehow during the commit of HBASE-11791. Investigate and fix. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[
https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161720#comment-14161720
]
Hadoop QA commented on HBASE-12016:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12673314/HBASE-12016.patch
against trunk revision .
ATTACHMENT ID: 12673314
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 48 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{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:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.util.TestFSTableDescriptors
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11235//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11235//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11235//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11235//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11235//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11235//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11235//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11235//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11235//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11235//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11235//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11235//console
This message is automatically generated.
Reduce number of versions in Meta table. Make it configurable
-
Key: HBASE-12016
URL: https://issues.apache.org/jira/browse/HBASE-12016
Project: HBase
Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Andrey Stepachev
Assignee: Andrey Stepachev
Priority: Minor
Fix For: 2.0.0, 0.98.8, 0.99.1
Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch,
HBASE-12016.patch
Currently meta keeps up to 10 versions of each KV.
For big metas it leads to substantial memory overhead and scan slowdowns.
(see https://issues.apache.org/jira/browse/HBASE-11165 )
Need to keep reasonable number of versions (suggested value is 3).
Number of versions configurable via parameter: hbase.meta.versions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11791) Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload
[ https://issues.apache.org/jira/browse/HBASE-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161721#comment-14161721 ] Misty Stanley-Jones commented on HBASE-11791: - [~jmhsieh] had asked me to commit things to master and branch-1 as a rule, if I understood him correctly. Maybe I misunderstood? Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload --- Key: HBASE-11791 URL: https://issues.apache.org/jira/browse/HBASE-11791 Project: HBase Issue Type: Task Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 2.0.0 Attachments: HBASE-11791-v1.patch, HBASE-11791-v10.patch, HBASE-11791-v11.patch, HBASE-11791-v12.patch, HBASE-11791-v13.patch, HBASE-11791-v14.patch, HBASE-11791-v15.patch, HBASE-11791-v16.patch, HBASE-11791-v17-rebased.patch, HBASE-11791-v17.patch, HBASE-11791-v18.patch, HBASE-11791-v2.patch, HBASE-11791-v3.patch, HBASE-11791-v4.patch, HBASE-11791-v5.patch, HBASE-11791-v6.patch, HBASE-11791-v7.patch, HBASE-11791-v9.patch, HBase Security Features Operators Guide - HBaseCon 2014 - v5.pptx, LDAPScanLabelGenerator.png Do a pass on the ACL and tag docs and make sure they are up to date and accurate, expand to cover HBASE-10885, HBASE-11001, HBASE-11002, HBASE-11434 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12168) Document Rest gateway SPNEGO-based authentication for client
[ https://issues.apache.org/jira/browse/HBASE-12168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161722#comment-14161722 ] Misty Stanley-Jones commented on HBASE-12168: - Please feel free to document this as you go, or at least take notes and leave them here. Document Rest gateway SPNEGO-based authentication for client Key: HBASE-12168 URL: https://issues.apache.org/jira/browse/HBASE-12168 Project: HBase Issue Type: Task Components: documentation, REST, security Reporter: Jerry He Fix For: 0.98.8, 0.99.1 After HBASE-5050, we seem to support SPNEGO-based authentication from client on Rest gateway. But I had a tough time finding the info. The support is not mentioned in Security book. In the security book, we still have: bq. It should be possible for clients to authenticate with the HBase cluster through the REST gateway in a pass-through manner via SPEGNO HTTP authentication. This is future work. The release note in HBASE-5050 seems to be obsolete as well. e.g. hbase.rest.kerberos.spnego.principal seems to be obsolete. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11791) Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload
[ https://issues.apache.org/jira/browse/HBASE-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161723#comment-14161723 ] Anoop Sam John commented on HBASE-11791: For 0.98 releases [~apurtell] used to copy the docs from trunk part. This I know from previous communications. What is the rule? Can some one clarify? Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload --- Key: HBASE-11791 URL: https://issues.apache.org/jira/browse/HBASE-11791 Project: HBase Issue Type: Task Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 2.0.0 Attachments: HBASE-11791-v1.patch, HBASE-11791-v10.patch, HBASE-11791-v11.patch, HBASE-11791-v12.patch, HBASE-11791-v13.patch, HBASE-11791-v14.patch, HBASE-11791-v15.patch, HBASE-11791-v16.patch, HBASE-11791-v17-rebased.patch, HBASE-11791-v17.patch, HBASE-11791-v18.patch, HBASE-11791-v2.patch, HBASE-11791-v3.patch, HBASE-11791-v4.patch, HBASE-11791-v5.patch, HBASE-11791-v6.patch, HBASE-11791-v7.patch, HBASE-11791-v9.patch, HBase Security Features Operators Guide - HBaseCon 2014 - v5.pptx, LDAPScanLabelGenerator.png Do a pass on the ACL and tag docs and make sure they are up to date and accurate, expand to cover HBASE-10885, HBASE-11001, HBASE-11002, HBASE-11434 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HBASE-11937) Update patch submission guidelines to stop using --no-prefix
[
https://issues.apache.org/jira/browse/HBASE-11937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones reassigned HBASE-11937:
---
Assignee: Misty Stanley-Jones
Update patch submission guidelines to stop using --no-prefix
Key: HBASE-11937
URL: https://issues.apache.org/jira/browse/HBASE-11937
Project: HBase
Issue Type: Improvement
Components: documentation
Reporter: Sean Busbey
Assignee: Misty Stanley-Jones
Priority: Minor
Right now the submission guidelines include the use of --no-prefix in the
Methods to Create Patches section:
{quote}
Git
git format-patch is preferred because it preserves commit messages. Use git
squash first, to combine smaller commits into a single larger one.
* git format-patch --no-prefix origin/master --stdout HBASE-.patch
* git diff --no-prefix origin/master HBASE-.patch
{quote}
The use of --no-prefix means that users of {{git apply}} and {{git am}} have
to know to specify {{-p0}} and (which strips 0 levels of prefix). Both of
those tools default to stripping the 1 level of prefix git makes by default.
The guide for HBase committers section on reviewing doesn't give any
suggestions on how to apply patches from contributors. It should probably
give examples for using {{git am}} and {{git apply}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12039) Lower log level for TableNotFoundException log message when throwing
[ https://issues.apache.org/jira/browse/HBASE-12039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161735#comment-14161735 ] Hudson commented on HBASE-12039: FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #551 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/551/]) HBASE-12039 Lower log level for TableNotFoundException log message when throwing (stack) (apurtell: rev 2cf4df0e4c816fe95a5750e539935686ba5a5f3f) * hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java Lower log level for TableNotFoundException log message when throwing Key: HBASE-12039 URL: https://issues.apache.org/jira/browse/HBASE-12039 Project: HBase Issue Type: Bug Reporter: James Taylor Assignee: stack Priority: Minor Fix For: 0.98.7, 0.94.25 Attachments: 12039-0.94.txt, 12039.txt Our HBase client tries to get the HTable descriptor for a table that may or may not exist. We catch and ignore the TableNotFoundException if it occurs, but the log message appear regardless of this which confuses our users. Would it be possible to lower the log level of this message since the exception is already being throw (making it up to the caller how they want to handle this). 14/09/20 20:01:54 WARN client.HConnectionManager$HConnectionImplementation: Encountered problems when prefetch META table: org.apache.hadoop.hbase.TableNotFoundException: Cannot find row in .META. for table: _IDX_TEST.TESTING, row=_IDX_TEST.TESTING,,99 at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:151) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:1059) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1121) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:1001) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:958) at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:251) at org.apache.hadoop.hbase.client.HTable.init(HTable.java:243) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12106) Move test annotations to test artifact
[ https://issues.apache.org/jira/browse/HBASE-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161734#comment-14161734 ] Hudson commented on HBASE-12106: FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #551 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/551/]) HBASE-12106 Move test annotations to test artifact (Enis Soztutar) (apurtell: rev 9efe354798d75f6b68c9e5e9cdef5fdff66b6e7c) * hbase-thrift/pom.xml * hbase-annotations/src/main/java/org/apache/hadoop/hbase/LargeTests.java * hbase-annotations/src/test/java/org/apache/hadoop/hbase/MediumTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/MediumTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/SmallTests.java * hbase-examples/pom.xml * hbase-annotations/src/test/java/org/apache/hadoop/hbase/IntegrationTests.java * hbase-annotations/src/main/java/org/apache/hadoop/hbase/IntegrationTests.java * hbase-shell/pom.xml * hbase-server/pom.xml * hbase-it/pom.xml * hbase-annotations/src/test/java/org/apache/hadoop/hbase/SmallTests.java * hbase-common/pom.xml * hbase-annotations/src/test/java/org/apache/hadoop/hbase/LargeTests.java * pom.xml * hbase-prefix-tree/pom.xml * hbase-client/pom.xml Amend HBASE-12106 Move test annotations to test artifact (Enis Soztutar) (apurtell: rev f3860bc376cf0a80ef3abb07b8bed1d529d354cc) * hbase-testing-util/pom.xml Move test annotations to test artifact -- Key: HBASE-12106 URL: https://issues.apache.org/jira/browse/HBASE-12106 Project: HBase Issue Type: Bug Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: 2.0.0, 0.98.7, 0.99.1 Attachments: HBASE-12106-addendum.patch, hbase-12106_v1-0.98+0.99.patch, hbase-12106_v1.patch, hbase-12106_v1.patch, hbase-12106_v2.patch Test annotation interfaces used to be under hbase-common/src/test then moved to hbase-annotations/src/main. We should move them to hbase-annotations/src/test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11791) Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload
[ https://issues.apache.org/jira/browse/HBASE-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161810#comment-14161810 ] Jonathan Hsieh commented on HBASE-11791: My suggestion is master and branch-1 because 1) [~apurtell] copies docs from trunk, and 2) when we get 1.0 to be the sustaining branch we'll likely do what we've been doing with 0.94 which is to publush 0.94 docs [1] separately from the trunk docs. [1] http://hbase.apache.org/0.94/book.html. [2] http://hbase.apache.org/book.html Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload --- Key: HBASE-11791 URL: https://issues.apache.org/jira/browse/HBASE-11791 Project: HBase Issue Type: Task Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 2.0.0 Attachments: HBASE-11791-v1.patch, HBASE-11791-v10.patch, HBASE-11791-v11.patch, HBASE-11791-v12.patch, HBASE-11791-v13.patch, HBASE-11791-v14.patch, HBASE-11791-v15.patch, HBASE-11791-v16.patch, HBASE-11791-v17-rebased.patch, HBASE-11791-v17.patch, HBASE-11791-v18.patch, HBASE-11791-v2.patch, HBASE-11791-v3.patch, HBASE-11791-v4.patch, HBASE-11791-v5.patch, HBASE-11791-v6.patch, HBASE-11791-v7.patch, HBASE-11791-v9.patch, HBase Security Features Operators Guide - HBaseCon 2014 - v5.pptx, LDAPScanLabelGenerator.png Do a pass on the ACL and tag docs and make sure they are up to date and accurate, expand to cover HBASE-10885, HBASE-11001, HBASE-11002, HBASE-11434 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[ https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated HBASE-12016: - Status: Open (was: Patch Available) Reduce number of versions in Meta table. Make it configurable - Key: HBASE-12016 URL: https://issues.apache.org/jira/browse/HBASE-12016 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Andrey Stepachev Assignee: Andrey Stepachev Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.1 Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch Currently meta keeps up to 10 versions of each KV. For big metas it leads to substantial memory overhead and scan slowdowns. (see https://issues.apache.org/jira/browse/HBASE-11165 ) Need to keep reasonable number of versions (suggested value is 3). Number of versions configurable via parameter: hbase.meta.versions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[ https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated HBASE-12016: - Status: Patch Available (was: Open) Reduce number of versions in Meta table. Make it configurable - Key: HBASE-12016 URL: https://issues.apache.org/jira/browse/HBASE-12016 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Andrey Stepachev Assignee: Andrey Stepachev Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.1 Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch Currently meta keeps up to 10 versions of each KV. For big metas it leads to substantial memory overhead and scan slowdowns. (see https://issues.apache.org/jira/browse/HBASE-11165 ) Need to keep reasonable number of versions (suggested value is 3). Number of versions configurable via parameter: hbase.meta.versions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[ https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated HBASE-12016: - Attachment: HBASE-12016.patch adding HFILE_ARCHIVE_DIRECTORY to forbidden table names. Reduce number of versions in Meta table. Make it configurable - Key: HBASE-12016 URL: https://issues.apache.org/jira/browse/HBASE-12016 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Andrey Stepachev Assignee: Andrey Stepachev Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.1 Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch Currently meta keeps up to 10 versions of each KV. For big metas it leads to substantial memory overhead and scan slowdowns. (see https://issues.apache.org/jira/browse/HBASE-11165 ) Need to keep reasonable number of versions (suggested value is 3). Number of versions configurable via parameter: hbase.meta.versions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11542) Unit Test KeyStoreTestUtil.java compilation failure in IBM JDK
[ https://issues.apache.org/jira/browse/HBASE-11542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pascal oliva updated HBASE-11542: - Attachment: HBASE-11542-5.patch Here a new patch : HBASE-11542-5.patch to update generateCertificate function by using reflection java Test successful : Running org.apache.hadoop.hbase.http.TestSSLHttpServer Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.448 sec - in org.apache.hadoop.hbase.http.TestSSLHttpServer Unit Test KeyStoreTestUtil.java compilation failure in IBM JDK Key: HBASE-11542 URL: https://issues.apache.org/jira/browse/HBASE-11542 Project: HBase Issue Type: Improvement Components: build, test Affects Versions: 0.99.0 Environment: RHEL 6.3 ,IBM JDK 6 Reporter: LinseyPang Priority: Minor Fix For: 2.0.0 Attachments: HBASE-11542-4.patch, HBASE-11542-5.patch, HBASE_11542-1.patch, hbase11542-0.99-v3.patch, hbase11542-0.99-v3.patch, hbase11542-0.99-v3.patch, hbase_11542-v2.patch, sslkeystore.patch In trunk, jira HBase-10336 added a utility test KeyStoreTestUtil.java, which leverages the following sun classes: import sun.security.x509.AlgorithmId; import sun.security.x509.CertificateAlgorithmId; this cause hbase compiler failure if using IBM JDK, There are similar classes like below in IBM jdk: import com.ibm.security.x509.AlgorithmId; import com.ibm.security.x509.CertificateAlgorithmId; This jira is to add handling of the x509 references. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[
https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161879#comment-14161879
]
Hadoop QA commented on HBASE-12016:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12673344/HBASE-12016.patch
against trunk revision .
ATTACHMENT ID: 12673344
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 48 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{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:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestShell
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11236//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11236//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11236//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11236//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11236//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11236//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11236//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11236//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11236//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11236//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11236//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11236//console
This message is automatically generated.
Reduce number of versions in Meta table. Make it configurable
-
Key: HBASE-12016
URL: https://issues.apache.org/jira/browse/HBASE-12016
Project: HBase
Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Andrey Stepachev
Assignee: Andrey Stepachev
Priority: Minor
Fix For: 2.0.0, 0.98.8, 0.99.1
Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch,
HBASE-12016.patch, HBASE-12016.patch
Currently meta keeps up to 10 versions of each KV.
For big metas it leads to substantial memory overhead and scan slowdowns.
(see https://issues.apache.org/jira/browse/HBASE-11165 )
Need to keep reasonable number of versions (suggested value is 3).
Number of versions configurable via parameter: hbase.meta.versions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[ https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161953#comment-14161953 ] Matteo Bertozzi commented on HBASE-12016: - why are you adding back archive to the blacklist? with namespace archive is a valid name Reduce number of versions in Meta table. Make it configurable - Key: HBASE-12016 URL: https://issues.apache.org/jira/browse/HBASE-12016 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Andrey Stepachev Assignee: Andrey Stepachev Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.1 Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch Currently meta keeps up to 10 versions of each KV. For big metas it leads to substantial memory overhead and scan slowdowns. (see https://issues.apache.org/jira/browse/HBASE-11165 ) Need to keep reasonable number of versions (suggested value is 3). Number of versions configurable via parameter: hbase.meta.versions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11997) CopyTable with bulkload
[ https://issues.apache.org/jira/browse/HBASE-11997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Deng updated HBASE-11997: Attachment: 0001-HBASE-11997-Add-bulkload-for-CopyTable-1.patch Address Ted's comments. Remove long lines. CopyTable with bulkload --- Key: HBASE-11997 URL: https://issues.apache.org/jira/browse/HBASE-11997 Project: HBase Issue Type: Sub-task Components: Client Affects Versions: 1.0.0 Reporter: @deprecated Yi Deng Assignee: Yi Deng Priority: Minor Labels: bulkloader, copy, mapreduce Fix For: 1.0.0 Attachments: 0001-HBASE-11997-Add-bulkload-for-CopyTable-1.patch, 0001-HBASE-11997-Add-bulkload-for-CopyTable.patch CopyTable using bulkload for writing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[ https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161962#comment-14161962 ] Andrey Stepachev commented on HBASE-12016: -- Thank you [~mbertozzi], you are right. With roodir/data directory it is not a forbidden name. Reduce number of versions in Meta table. Make it configurable - Key: HBASE-12016 URL: https://issues.apache.org/jira/browse/HBASE-12016 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Andrey Stepachev Assignee: Andrey Stepachev Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.1 Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch Currently meta keeps up to 10 versions of each KV. For big metas it leads to substantial memory overhead and scan slowdowns. (see https://issues.apache.org/jira/browse/HBASE-11165 ) Need to keep reasonable number of versions (suggested value is 3). Number of versions configurable via parameter: hbase.meta.versions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[ https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated HBASE-12016: - Attachment: HBASE-12016.patch Reduce number of versions in Meta table. Make it configurable - Key: HBASE-12016 URL: https://issues.apache.org/jira/browse/HBASE-12016 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Andrey Stepachev Assignee: Andrey Stepachev Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.1 Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch Currently meta keeps up to 10 versions of each KV. For big metas it leads to substantial memory overhead and scan slowdowns. (see https://issues.apache.org/jira/browse/HBASE-11165 ) Need to keep reasonable number of versions (suggested value is 3). Number of versions configurable via parameter: hbase.meta.versions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[ https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated HBASE-12016: - Status: Open (was: Patch Available) Reduce number of versions in Meta table. Make it configurable - Key: HBASE-12016 URL: https://issues.apache.org/jira/browse/HBASE-12016 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Andrey Stepachev Assignee: Andrey Stepachev Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.1 Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch Currently meta keeps up to 10 versions of each KV. For big metas it leads to substantial memory overhead and scan slowdowns. (see https://issues.apache.org/jira/browse/HBASE-11165 ) Need to keep reasonable number of versions (suggested value is 3). Number of versions configurable via parameter: hbase.meta.versions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[ https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated HBASE-12016: - Status: Patch Available (was: Open) Reduce number of versions in Meta table. Make it configurable - Key: HBASE-12016 URL: https://issues.apache.org/jira/browse/HBASE-12016 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Andrey Stepachev Assignee: Andrey Stepachev Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.1 Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch Currently meta keeps up to 10 versions of each KV. For big metas it leads to substantial memory overhead and scan slowdowns. (see https://issues.apache.org/jira/browse/HBASE-11165 ) Need to keep reasonable number of versions (suggested value is 3). Number of versions configurable via parameter: hbase.meta.versions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12187) Review in source the paper Simple Testing Can Prevent Most Critical Failures
stack created HBASE-12187: - Summary: Review in source the paper Simple Testing Can Prevent Most Critical Failures Key: HBASE-12187 URL: https://issues.apache.org/jira/browse/HBASE-12187 Project: HBase Issue Type: Bug Reporter: stack Priority: Critical Review the helpful paper https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-yuan.pdf It describes 'catastrophic failures', especially issues where exceptions are thrown but not properly handled. Their static analysis tool Aspirator turns up a bunch of the obvious offenders (Lets add to test-patch.sh alongside findbugs?). This issue is about going through code base making sub-issues to root out these and others (Don't we have the test described in figure #6 already? I thought we did? If we don't, need to add). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12176) WALCellCodec Encoders support for non-KeyValue Cells
[ https://issues.apache.org/jira/browse/HBASE-12176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161979#comment-14161979 ] stack commented on HBASE-12176: --- Ok. Was wondering since only the write-side is changed. +1 Do we have any old WALs in the code base to try against as part of a unit test to ensure new WAL code can read old WAL files? We should add one or two. New issue. WALCellCodec Encoders support for non-KeyValue Cells Key: HBASE-12176 URL: https://issues.apache.org/jira/browse/HBASE-12176 Project: HBase Issue Type: Improvement Reporter: Anoop Sam John Assignee: Anoop Sam John Fix For: 2.0.0, 0.99.1 Attachments: HBASE-12176.patch Now in all Encoder returned by WALCellCodec and SecureWALCellCodec it is assumed that it will get only KeyValues. If not it just throws IOE. Now we support Cells through out in write path as well and these Encoders should support non KV cells as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11997) CopyTable with bulkload
[
https://issues.apache.org/jira/browse/HBASE-11997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162022#comment-14162022
]
Hadoop QA commented on HBASE-11997:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12673363/0001-HBASE-11997-Add-bulkload-for-CopyTable-1.patch
against trunk revision .
ATTACHMENT ID: 12673363
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
warning messages.
{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:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{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.http.TestHttpServerLifecycle.testStartedServerIsAlive(TestHttpServerLifecycle.java:71)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11237//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11237//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11237//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11237//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11237//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11237//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11237//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11237//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11237//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11237//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11237//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11237//artifact/trunk/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11237//console
This message is automatically generated.
CopyTable with bulkload
---
Key: HBASE-11997
URL: https://issues.apache.org/jira/browse/HBASE-11997
Project: HBase
Issue Type: Sub-task
Components: Client
Affects Versions: 1.0.0
Reporter: @deprecated Yi Deng
Assignee: Yi Deng
Priority: Minor
Labels: bulkloader, copy, mapreduce
Fix For: 1.0.0
Attachments: 0001-HBASE-11997-Add-bulkload-for-CopyTable-1.patch,
0001-HBASE-11997-Add-bulkload-for-CopyTable.patch
CopyTable using bulkload for writing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11997) CopyTable with bulkload
[ https://issues.apache.org/jira/browse/HBASE-11997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162027#comment-14162027 ] Ted Yu commented on HBASE-11997: TestHttpServerLifecycle is a small test - meaning, large tests were not run. Please run through QA bot one more time. 'mvn site' error is not related to patch. See if the javadoc warning is related. CopyTable with bulkload --- Key: HBASE-11997 URL: https://issues.apache.org/jira/browse/HBASE-11997 Project: HBase Issue Type: Sub-task Components: Client Affects Versions: 1.0.0 Reporter: @deprecated Yi Deng Assignee: Yi Deng Priority: Minor Labels: bulkloader, copy, mapreduce Fix For: 1.0.0 Attachments: 0001-HBASE-11997-Add-bulkload-for-CopyTable-1.patch, 0001-HBASE-11997-Add-bulkload-for-CopyTable.patch CopyTable using bulkload for writing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11791) Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload
[ https://issues.apache.org/jira/browse/HBASE-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162032#comment-14162032 ] stack commented on HBASE-11791: --- bq. ...when we get 1.0 to be the sustaining branch we'll likely do what we've been doing with 0.94 which is to publush 0.94 docs I'd suggest we wait till we release 1.0 before we bother doing the extra backport of doc patches. Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload --- Key: HBASE-11791 URL: https://issues.apache.org/jira/browse/HBASE-11791 Project: HBase Issue Type: Task Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 2.0.0 Attachments: HBASE-11791-v1.patch, HBASE-11791-v10.patch, HBASE-11791-v11.patch, HBASE-11791-v12.patch, HBASE-11791-v13.patch, HBASE-11791-v14.patch, HBASE-11791-v15.patch, HBASE-11791-v16.patch, HBASE-11791-v17-rebased.patch, HBASE-11791-v17.patch, HBASE-11791-v18.patch, HBASE-11791-v2.patch, HBASE-11791-v3.patch, HBASE-11791-v4.patch, HBASE-11791-v5.patch, HBASE-11791-v6.patch, HBASE-11791-v7.patch, HBASE-11791-v9.patch, HBase Security Features Operators Guide - HBaseCon 2014 - v5.pptx, LDAPScanLabelGenerator.png Do a pass on the ACL and tag docs and make sure they are up to date and accurate, expand to cover HBASE-10885, HBASE-11001, HBASE-11002, HBASE-11434 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12185) Deadlock in HConnectionManager$HConnectionImplementation
[
https://issues.apache.org/jira/browse/HBASE-12185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-12185:
--
Fix Version/s: 0.94.25
Deadlock in HConnectionManager$HConnectionImplementation
Key: HBASE-12185
URL: https://issues.apache.org/jira/browse/HBASE-12185
Project: HBase
Issue Type: Bug
Components: Client
Affects Versions: 0.94.2
Environment: CDH 4.2.0
Reporter: Michael Tamm
Priority: Critical
Fix For: 0.94.25
Here you can see the relevant section of a thread dump:
{noformat}
Found one Java-level deadlock:
=
AsyncSave-700512-Worker-EventThread:
waiting to lock monitor 0x7f8d90eecd20 (object 0x0005c0a8e1d0, a
org.apache.hadoop.hbase.zookeeper.RootRegionTracker),
which is held by AsyncSave-700546-Worker
AsyncSave-700546-Worker:
waiting to lock monitor 0x7f8d90149700 (object 0x000571404180, a
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation),
which is held by AsyncSave-700512-Worker-EventThread
Java stack information for the threads listed above:
===
AsyncSave-700512-Worker-EventThread:
at
org.apache.hadoop.hbase.zookeeper.ZooKeeperNodeTracker.stop(ZooKeeperNodeTracker.java:98)
- waiting to lock 0x0005c0a8e1d0 (a
org.apache.hadoop.hbase.zookeeper.RootRegionTracker)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.resetZooKeeperTrackers(HConnectionManager.java:603)
- locked 0x000571404180 (a
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.abort(HConnectionManager.java:1681)
at
org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher.connectionEvent(ZooKeeperWatcher.java:389)
at
org.apache.hadoop.hbase.zookeeper.ZooKeeperWatcher.process(ZooKeeperWatcher.java:286)
at
org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:519)
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:495)
AsyncSave-700546-Worker:
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.resetZooKeeperTrackers(HConnectionManager.java:598)
- waiting to lock 0x000571404180 (a
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.abort(HConnectionManager.java:1681)
at
org.apache.hadoop.hbase.zookeeper.ZooKeeperNodeTracker.blockUntilAvailable(ZooKeeperNodeTracker.java:132)
- locked 0x0005c0a8e1d0 (a
org.apache.hadoop.hbase.zookeeper.RootRegionTracker)
at
org.apache.hadoop.hbase.zookeeper.RootRegionTracker.waitRootRegionLocation(RootRegionTracker.java:83)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:841)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:954)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:852)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:954)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:856)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:813)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1503)
at
org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1388)
at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:955)
at
org.apache.hadoop.hbase.client.HTablePool$PooledHTable.flushCommits(HTablePool.java:449)
at ...
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11990) Make setting the start and stop row for a specific prefix easier
[
https://issues.apache.org/jira/browse/HBASE-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162048#comment-14162048
]
stack commented on HBASE-11990:
---
+1 on this patch. Comes of a user's experience banging his head against our
API. Unless objection, will commit in a day or so. [~lhofhansl], [~enis], and
[~jmspaggi], you fellas good w/ that?
Make setting the start and stop row for a specific prefix easier
Key: HBASE-11990
URL: https://issues.apache.org/jira/browse/HBASE-11990
Project: HBase
Issue Type: New Feature
Components: Client
Reporter: Niels Basjes
Attachments: 11990v4.txt, HBASE-11990-20140916-v2.patch,
HBASE-11990-20140916-v3.patch, HBASE-11990-20140916-v5.patch,
HBASE-11990-20140916-v6.patch, HBASE-11990-20140916.patch,
HBASE-11990-20140917-v7.patch, HBASE-11990-20140919-v8.patch,
HBASE-11990-20140921-v9.patch, HBASE-11990-20140923-v10.patch
If you want to set a scan from your application to scan for a specific row
prefix this is actually quite hard.
As described in several places you can set the startRow to the prefix; yet
the stopRow should be set to the prefix '+1'
If the prefix 'ASCII' put into a byte[] then this is easy because you can
simply increment the last byte of the array.
But if your application uses real binary rowids you may run into the scenario
that your prefix is something like
{code}{ 0x12, 0x23, 0xFF, 0xFF }{code} Then the increment should be {code}{
0x12, 0x24 }{code}
I have prepared a proposed patch that makes setting these values correctly a
lot easier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11990) Make setting the start and stop row for a specific prefix easier
[
https://issues.apache.org/jira/browse/HBASE-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-11990:
--
Attachment: HBASE-11990-20140923-v10.patch
Retry to see if still applies and to see if any issues now tests have been
stabilized (mostly)
Make setting the start and stop row for a specific prefix easier
Key: HBASE-11990
URL: https://issues.apache.org/jira/browse/HBASE-11990
Project: HBase
Issue Type: New Feature
Components: Client
Reporter: Niels Basjes
Attachments: 11990v4.txt, HBASE-11990-20140916-v2.patch,
HBASE-11990-20140916-v3.patch, HBASE-11990-20140916-v5.patch,
HBASE-11990-20140916-v6.patch, HBASE-11990-20140916.patch,
HBASE-11990-20140917-v7.patch, HBASE-11990-20140919-v8.patch,
HBASE-11990-20140921-v9.patch, HBASE-11990-20140923-v10.patch,
HBASE-11990-20140923-v10.patch
If you want to set a scan from your application to scan for a specific row
prefix this is actually quite hard.
As described in several places you can set the startRow to the prefix; yet
the stopRow should be set to the prefix '+1'
If the prefix 'ASCII' put into a byte[] then this is easy because you can
simply increment the last byte of the array.
But if your application uses real binary rowids you may run into the scenario
that your prefix is something like
{code}{ 0x12, 0x23, 0xFF, 0xFF }{code} Then the increment should be {code}{
0x12, 0x24 }{code}
I have prepared a proposed patch that makes setting these values correctly a
lot easier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[
https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162059#comment-14162059
]
Ted Yu commented on HBASE-12016:
Looks good overall.
{code}
+ public static int DEFAULT_HBASE_META_BLOCK_SIZE = 8 * 1024;
{code}
How was the block size determined ?
{code}
+ public static void setInfoFamilyCachingForMeta(HTableDescriptor
metaDescriptor, final boolean b) {
{code}
Since table descriptor is an argument, method name can be changed to
setInfoFamilyCaching.
Reduce number of versions in Meta table. Make it configurable
-
Key: HBASE-12016
URL: https://issues.apache.org/jira/browse/HBASE-12016
Project: HBase
Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Andrey Stepachev
Assignee: Andrey Stepachev
Priority: Minor
Fix For: 2.0.0, 0.98.8, 0.99.1
Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch,
HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch
Currently meta keeps up to 10 versions of each KV.
For big metas it leads to substantial memory overhead and scan slowdowns.
(see https://issues.apache.org/jira/browse/HBASE-11165 )
Need to keep reasonable number of versions (suggested value is 3).
Number of versions configurable via parameter: hbase.meta.versions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11990) Make setting the start and stop row for a specific prefix easier
[
https://issues.apache.org/jira/browse/HBASE-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162060#comment-14162060
]
Hadoop QA commented on HBASE-11990:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12673378/HBASE-11990-20140923-v10.patch
against trunk revision .
ATTACHMENT ID: 12673378
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 7 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11239//console
This message is automatically generated.
Make setting the start and stop row for a specific prefix easier
Key: HBASE-11990
URL: https://issues.apache.org/jira/browse/HBASE-11990
Project: HBase
Issue Type: New Feature
Components: Client
Reporter: Niels Basjes
Attachments: 11990v4.txt, HBASE-11990-20140916-v2.patch,
HBASE-11990-20140916-v3.patch, HBASE-11990-20140916-v5.patch,
HBASE-11990-20140916-v6.patch, HBASE-11990-20140916.patch,
HBASE-11990-20140917-v7.patch, HBASE-11990-20140919-v8.patch,
HBASE-11990-20140921-v9.patch, HBASE-11990-20140923-v10.patch,
HBASE-11990-20140923-v10.patch
If you want to set a scan from your application to scan for a specific row
prefix this is actually quite hard.
As described in several places you can set the startRow to the prefix; yet
the stopRow should be set to the prefix '+1'
If the prefix 'ASCII' put into a byte[] then this is easy because you can
simply increment the last byte of the array.
But if your application uses real binary rowids you may run into the scenario
that your prefix is something like
{code}{ 0x12, 0x23, 0xFF, 0xFF }{code} Then the increment should be {code}{
0x12, 0x24 }{code}
I have prepared a proposed patch that makes setting these values correctly a
lot easier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[
https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162086#comment-14162086
]
Hadoop QA commented on HBASE-12016:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12673364/HBASE-12016.patch
against trunk revision .
ATTACHMENT ID: 12673364
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 48 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{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:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestShell
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11238//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11238//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11238//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11238//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11238//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11238//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11238//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11238//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11238//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11238//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11238//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11238//console
This message is automatically generated.
Reduce number of versions in Meta table. Make it configurable
-
Key: HBASE-12016
URL: https://issues.apache.org/jira/browse/HBASE-12016
Project: HBase
Issue Type: Improvement
Affects Versions: 2.0.0
Reporter: Andrey Stepachev
Assignee: Andrey Stepachev
Priority: Minor
Fix For: 2.0.0, 0.98.8, 0.99.1
Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch,
HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch
Currently meta keeps up to 10 versions of each KV.
For big metas it leads to substantial memory overhead and scan slowdowns.
(see https://issues.apache.org/jira/browse/HBASE-11165 )
Need to keep reasonable number of versions (suggested value is 3).
Number of versions configurable via parameter: hbase.meta.versions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-5954) Allow proper fsync support for HBase
[ https://issues.apache.org/jira/browse/HBASE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-5954: --- Component/s: wal HFile Allow proper fsync support for HBase Key: HBASE-5954 URL: https://issues.apache.org/jira/browse/HBASE-5954 Project: HBase Issue Type: Improvement Components: HFile, wal Reporter: Lars Hofhansl Assignee: Lars Hofhansl Priority: Critical Attachments: 5954-trunk-hdfs-trunk-v2.txt, 5954-trunk-hdfs-trunk-v3.txt, 5954-trunk-hdfs-trunk-v4.txt, 5954-trunk-hdfs-trunk-v5.txt, 5954-trunk-hdfs-trunk-v6.txt, 5954-trunk-hdfs-trunk.txt, hbase-hdfs-744.txt At least get recommendation into 0.96 doc and some numbers running w/ this hdfs feature enabled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11791) Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload
[ https://issues.apache.org/jira/browse/HBASE-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162092#comment-14162092 ] Jonathan Hsieh commented on HBASE-11791: We should bring up on the mailing list -- but I suspect that if we only commit docs to master, we'll get to a state where up to date docs about 1.0 will only be in master, docs about 1.0 will be out of date and if/when we follow through with revamping/restarting docs for 2.0, the up to date 1.0 docs will be removed from the master branch or end up having to be kept around in a defunct path in the master branch. Some of the 1.x branch stuff that hasn't been document will likely get deprecated/changed by 2.0 and it seems strange to have docs for 1.x branch long lived in master. Because of this and because we've already created branch-1, it seems prudent to keep master and 1.0 docs up to date in sync for 1.x features, and have only the 2.0 features docs commit to master branch. Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload --- Key: HBASE-11791 URL: https://issues.apache.org/jira/browse/HBASE-11791 Project: HBase Issue Type: Task Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 2.0.0 Attachments: HBASE-11791-v1.patch, HBASE-11791-v10.patch, HBASE-11791-v11.patch, HBASE-11791-v12.patch, HBASE-11791-v13.patch, HBASE-11791-v14.patch, HBASE-11791-v15.patch, HBASE-11791-v16.patch, HBASE-11791-v17-rebased.patch, HBASE-11791-v17.patch, HBASE-11791-v18.patch, HBASE-11791-v2.patch, HBASE-11791-v3.patch, HBASE-11791-v4.patch, HBASE-11791-v5.patch, HBASE-11791-v6.patch, HBASE-11791-v7.patch, HBASE-11791-v9.patch, HBase Security Features Operators Guide - HBaseCon 2014 - v5.pptx, LDAPScanLabelGenerator.png Do a pass on the ACL and tag docs and make sure they are up to date and accurate, expand to cover HBASE-10885, HBASE-11001, HBASE-11002, HBASE-11434 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12016) Reduce number of versions in Meta table. Make it configurable
[ https://issues.apache.org/jira/browse/HBASE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162097#comment-14162097 ] Ted Yu commented on HBASE-12016: TestShell failure is related to the patch. Reduce number of versions in Meta table. Make it configurable - Key: HBASE-12016 URL: https://issues.apache.org/jira/browse/HBASE-12016 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Andrey Stepachev Assignee: Andrey Stepachev Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.1 Attachments: HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch, HBASE-12016.patch Currently meta keeps up to 10 versions of each KV. For big metas it leads to substantial memory overhead and scan slowdowns. (see https://issues.apache.org/jira/browse/HBASE-11165 ) Need to keep reasonable number of versions (suggested value is 3). Number of versions configurable via parameter: hbase.meta.versions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HBASE-11838) Enable PREFIX_TREE in integration tests
[ https://issues.apache.org/jira/browse/HBASE-11838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang resolved HBASE-11838. - Resolution: Fixed Fix Version/s: 0.99.1 2.0.0 Hadoop Flags: Reviewed With HBASE-11728 and HBASE-12078, ITBLL with PREFIX_TREE encoding works fine for me now. Integrated the patch to branch 1 and master. ITBLL tests all supported data encodings from now on. Thanks. Enable PREFIX_TREE in integration tests --- Key: HBASE-11838 URL: https://issues.apache.org/jira/browse/HBASE-11838 Project: HBase Issue Type: Test Components: test Reporter: Jimmy Xiang Assignee: Jimmy Xiang Priority: Minor Fix For: 2.0.0, 0.99.1 Attachments: hbase-11838.patch HBASE-11728 fixed a PREFIX_TREE encoding bug. Let's try to enable the encoding in integration tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11542) Unit Test KeyStoreTestUtil.java compilation failure in IBM JDK
[ https://issues.apache.org/jira/browse/HBASE-11542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pascal oliva updated HBASE-11542: - Status: Patch Available (was: Open) new HBASE-11542-5.patch using reflexion java to load sun.security.* or com.ibm.security.* regarding the JVM used. Unit Test KeyStoreTestUtil.java compilation failure in IBM JDK Key: HBASE-11542 URL: https://issues.apache.org/jira/browse/HBASE-11542 Project: HBase Issue Type: Improvement Components: build, test Affects Versions: 0.99.0 Environment: RHEL 6.3 ,IBM JDK 6 Reporter: LinseyPang Priority: Minor Fix For: 2.0.0 Attachments: HBASE-11542-4.patch, HBASE-11542-5.patch, HBASE_11542-1.patch, hbase11542-0.99-v3.patch, hbase11542-0.99-v3.patch, hbase11542-0.99-v3.patch, hbase_11542-v2.patch, sslkeystore.patch In trunk, jira HBase-10336 added a utility test KeyStoreTestUtil.java, which leverages the following sun classes: import sun.security.x509.AlgorithmId; import sun.security.x509.CertificateAlgorithmId; this cause hbase compiler failure if using IBM JDK, There are similar classes like below in IBM jdk: import com.ibm.security.x509.AlgorithmId; import com.ibm.security.x509.CertificateAlgorithmId; This jira is to add handling of the x509 references. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12142) Truncate command does not preserve ACLs table
[ https://issues.apache.org/jira/browse/HBASE-12142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-12142: - Attachment: HBASE-12142_2.patch The latest patch removed the config parameter. Truncate command does not preserve ACLs table - Key: HBASE-12142 URL: https://issues.apache.org/jira/browse/HBASE-12142 Project: HBase Issue Type: Bug Affects Versions: 0.98.6 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Labels: security Attachments: HBASE-12142_0.patch, HBASE-12142_1.patch, HBASE-12142_2.patch The current truncate command does not preserve acls on a table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11912) Catch some bad practices at compile time with error-prone
[ https://issues.apache.org/jira/browse/HBASE-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162129#comment-14162129 ] Andrew Purtell commented on HBASE-11912: The static analysis described in the paper referred to by HBASE-12187 might be a good thing to try implementing with this framework, to determine what's possible with it. Catch some bad practices at compile time with error-prone - Key: HBASE-11912 URL: https://issues.apache.org/jira/browse/HBASE-11912 Project: HBase Issue Type: Improvement Reporter: Andrew Purtell Attachments: HBASE-11912.patch, HBASE-11912.patch Google's error-prone (https://code.google.com/p/error-prone/) wraps javac with some additional static analysis that will generate additional warnings or errors at compile time if certain bug patterns (https://code.google.com/p/error-prone/wiki/BugPatterns) are detected. What's nice about this approach, as opposed to findbugs, is the compile time detection and erroring out prevent the detected problems from getting into the codebase up front. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11791) Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload
[ https://issues.apache.org/jira/browse/HBASE-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162138#comment-14162138 ] stack commented on HBASE-11791: --- [~jmhsieh] Sounds like you want to institute new versioning system on doc, so yeah, mailing list to announce new policy. Need to build some stuff so we can publish different versions out on website. Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload --- Key: HBASE-11791 URL: https://issues.apache.org/jira/browse/HBASE-11791 Project: HBase Issue Type: Task Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 2.0.0 Attachments: HBASE-11791-v1.patch, HBASE-11791-v10.patch, HBASE-11791-v11.patch, HBASE-11791-v12.patch, HBASE-11791-v13.patch, HBASE-11791-v14.patch, HBASE-11791-v15.patch, HBASE-11791-v16.patch, HBASE-11791-v17-rebased.patch, HBASE-11791-v17.patch, HBASE-11791-v18.patch, HBASE-11791-v2.patch, HBASE-11791-v3.patch, HBASE-11791-v4.patch, HBASE-11791-v5.patch, HBASE-11791-v6.patch, HBASE-11791-v7.patch, HBASE-11791-v9.patch, HBase Security Features Operators Guide - HBaseCon 2014 - v5.pptx, LDAPScanLabelGenerator.png Do a pass on the ACL and tag docs and make sure they are up to date and accurate, expand to cover HBASE-10885, HBASE-11001, HBASE-11002, HBASE-11434 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11997) CopyTable with bulkload
[ https://issues.apache.org/jira/browse/HBASE-11997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-11997: --- Fix Version/s: (was: 1.0.0) 0.99.1 2.0.0 Hadoop Flags: Reviewed [~apurtell]: Do you want this in 0.98 ? CopyTable with bulkload --- Key: HBASE-11997 URL: https://issues.apache.org/jira/browse/HBASE-11997 Project: HBase Issue Type: Sub-task Components: Client Affects Versions: 1.0.0 Reporter: @deprecated Yi Deng Assignee: Yi Deng Priority: Minor Labels: bulkloader, copy, mapreduce Fix For: 2.0.0, 0.99.1 Attachments: 0001-HBASE-11997-Add-bulkload-for-CopyTable-1.patch, 0001-HBASE-11997-Add-bulkload-for-CopyTable.patch CopyTable using bulkload for writing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12109) user_permission command for namespace does not return correct result
[ https://issues.apache.org/jira/browse/HBASE-12109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12109: --- Fix Version/s: 0.99.1 0.98.8 2.0.0 Hadoop Flags: Reviewed user_permission command for namespace does not return correct result Key: HBASE-12109 URL: https://issues.apache.org/jira/browse/HBASE-12109 Project: HBase Issue Type: Bug Components: shell Affects Versions: 2.0.0 Reporter: Vandana Ayyalasomayajula Assignee: Vandana Ayyalasomayajula Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.1 Attachments: HBASE-12109_0.patch, HBASE-12109_1.patch, HBASE-12109_2.patch The existing user_permission command does not return permissions related to namespace. The permissions exist in the acl table, but the user_permission.rb does not handle namespaces. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11997) CopyTable with bulkload
[
https://issues.apache.org/jira/browse/HBASE-11997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162159#comment-14162159
]
Ted Yu commented on HBASE-11997:
Please fix the following:
{code}
[WARNING]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/CopyTable.java:85:
warning - @param argument conf is not a parameter name.
[WARNING]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableInputFormatBase.java:292:
warning - Tag @link: can't find initializeTable(Connection, TableName) in
org.apache.hadoop.hbase.mapreduce.TableInputFormatBase
{code}
CopyTable with bulkload
---
Key: HBASE-11997
URL: https://issues.apache.org/jira/browse/HBASE-11997
Project: HBase
Issue Type: Sub-task
Components: Client
Affects Versions: 1.0.0
Reporter: @deprecated Yi Deng
Assignee: Yi Deng
Priority: Minor
Labels: bulkloader, copy, mapreduce
Fix For: 2.0.0, 0.99.1
Attachments: 0001-HBASE-11997-Add-bulkload-for-CopyTable-1.patch,
0001-HBASE-11997-Add-bulkload-for-CopyTable.patch
CopyTable using bulkload for writing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-12188) Use AES-GCM as the preferred mode when encrypting HFiles
Andrew Purtell created HBASE-12188: -- Summary: Use AES-GCM as the preferred mode when encrypting HFiles Key: HBASE-12188 URL: https://issues.apache.org/jira/browse/HBASE-12188 Project: HBase Issue Type: Improvement Reporter: Andrew Purtell Priority: Minor Fix For: 2.0.0 Currently for encrypting HFiles we use AES in CTR mode. This protects data against plaintext recovery but does not offer data integrity verification. We must continue to rely on HDFS integrity protection mechanisms, or internal HFile checksums, which could be subverted. An attacker might be able to maliciously introduce corruption that would not be detected during decryption. GCM mode operates as a stream cipher like CTR mode while incrementally calculating a message authentication code (MAC) concurrent with encryption, in a way that affords efficient high performance parallel implementation. The process of decryption also verifies the integrity of the data in a cryptographically strong manner. Any tampering or corruption will result in a reported decryption failure. This provides a marginal improvement in security because tampering or corruption will be found at the HFile level and so the invalid data will not have a chance to be passed up into higher layers. We needed to use AES-CTR when initially developing HFile encryption because just about everyone was still using Java 6 in production. This has changed. We have dropped support for Java 6 as of branch-1. Conceivably we could introduce use of the new Java 7+ APIs for working with AEAD modes like GCM. Once doing so, the code will no longer compile if using the JDK 6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12188) Use AES-GCM as the preferred cipher when encrypting HFiles
[ https://issues.apache.org/jira/browse/HBASE-12188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-12188: --- Summary: Use AES-GCM as the preferred cipher when encrypting HFiles (was: Use AES-GCM as the preferred mode when encrypting HFiles) Use AES-GCM as the preferred cipher when encrypting HFiles -- Key: HBASE-12188 URL: https://issues.apache.org/jira/browse/HBASE-12188 Project: HBase Issue Type: Improvement Reporter: Andrew Purtell Priority: Minor Fix For: 2.0.0 Currently for encrypting HFiles we use AES in CTR mode. This protects data against plaintext recovery but does not offer data integrity verification. We must continue to rely on HDFS integrity protection mechanisms, or internal HFile checksums, which could be subverted. An attacker might be able to maliciously introduce corruption that would not be detected during decryption. GCM mode operates as a stream cipher like CTR mode while incrementally calculating a message authentication code (MAC) concurrent with encryption, in a way that affords efficient high performance parallel implementation. The process of decryption also verifies the integrity of the data in a cryptographically strong manner. Any tampering or corruption will result in a reported decryption failure. This provides a marginal improvement in security because tampering or corruption will be found at the HFile level and so the invalid data will not have a chance to be passed up into higher layers. We needed to use AES-CTR when initially developing HFile encryption because just about everyone was still using Java 6 in production. This has changed. We have dropped support for Java 6 as of branch-1. Conceivably we could introduce use of the new Java 7+ APIs for working with AEAD modes like GCM. Once doing so, the code will no longer compile if using the JDK 6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11997) CopyTable with bulkload
[ https://issues.apache.org/jira/browse/HBASE-11997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Deng updated HBASE-11997: Attachment: 0001-HBASE-11997-Add-bulkload-for-CopyTable-2.patch Fix the javadoc warning. CopyTable with bulkload --- Key: HBASE-11997 URL: https://issues.apache.org/jira/browse/HBASE-11997 Project: HBase Issue Type: Sub-task Components: Client Affects Versions: 1.0.0 Reporter: @deprecated Yi Deng Assignee: Yi Deng Priority: Minor Labels: bulkloader, copy, mapreduce Fix For: 2.0.0, 0.99.1 Attachments: 0001-HBASE-11997-Add-bulkload-for-CopyTable-1.patch, 0001-HBASE-11997-Add-bulkload-for-CopyTable-2.patch, 0001-HBASE-11997-Add-bulkload-for-CopyTable.patch CopyTable using bulkload for writing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11791) Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload
[ https://issues.apache.org/jira/browse/HBASE-11791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162182#comment-14162182 ] Andrew Purtell commented on HBASE-11791: Agreed we should discuss doc versioning on dev@. I don't have a strong opinion either way. We could do one big backport of trunk docs to the branches and then start committing deltas wherever appropriate for the features they discuss. I suppose I could prune out from 0.98 docs any mention of features or options that aren't supported there... Update docs on visibility tags and ACLs, transparent encryption, secure bulk upload --- Key: HBASE-11791 URL: https://issues.apache.org/jira/browse/HBASE-11791 Project: HBase Issue Type: Task Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Fix For: 2.0.0 Attachments: HBASE-11791-v1.patch, HBASE-11791-v10.patch, HBASE-11791-v11.patch, HBASE-11791-v12.patch, HBASE-11791-v13.patch, HBASE-11791-v14.patch, HBASE-11791-v15.patch, HBASE-11791-v16.patch, HBASE-11791-v17-rebased.patch, HBASE-11791-v17.patch, HBASE-11791-v18.patch, HBASE-11791-v2.patch, HBASE-11791-v3.patch, HBASE-11791-v4.patch, HBASE-11791-v5.patch, HBASE-11791-v6.patch, HBASE-11791-v7.patch, HBASE-11791-v9.patch, HBase Security Features Operators Guide - HBaseCon 2014 - v5.pptx, LDAPScanLabelGenerator.png Do a pass on the ACL and tag docs and make sure they are up to date and accurate, expand to cover HBASE-10885, HBASE-11001, HBASE-11002, HBASE-11434 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11997) CopyTable with bulkload
[ https://issues.apache.org/jira/browse/HBASE-11997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162186#comment-14162186 ] Yi Deng commented on HBASE-11997: - [~tedyu] The @link one was not introduced in this diff. CopyTable with bulkload --- Key: HBASE-11997 URL: https://issues.apache.org/jira/browse/HBASE-11997 Project: HBase Issue Type: Sub-task Components: Client Affects Versions: 1.0.0 Reporter: @deprecated Yi Deng Assignee: Yi Deng Priority: Minor Labels: bulkloader, copy, mapreduce Fix For: 2.0.0, 0.99.1 Attachments: 0001-HBASE-11997-Add-bulkload-for-CopyTable-1.patch, 0001-HBASE-11997-Add-bulkload-for-CopyTable-2.patch, 0001-HBASE-11997-Add-bulkload-for-CopyTable.patch CopyTable using bulkload for writing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11838) Enable PREFIX_TREE in integration tests
[ https://issues.apache.org/jira/browse/HBASE-11838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-11838: --- Fix Version/s: 0.98.8 Cherry picked to 0.98 also Enable PREFIX_TREE in integration tests --- Key: HBASE-11838 URL: https://issues.apache.org/jira/browse/HBASE-11838 Project: HBase Issue Type: Test Components: test Reporter: Jimmy Xiang Assignee: Jimmy Xiang Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.1 Attachments: hbase-11838.patch HBASE-11728 fixed a PREFIX_TREE encoding bug. Let's try to enable the encoding in integration tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HBASE-10040) Fix Potential Resource Leak in HRegion
[ https://issues.apache.org/jira/browse/HBASE-10040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark resolved HBASE-10040. --- Resolution: Won't Fix Fix Potential Resource Leak in HRegion -- Key: HBASE-10040 URL: https://issues.apache.org/jira/browse/HBASE-10040 Project: HBase Issue Type: Sub-task Affects Versions: 0.98.0, 0.96.0 Reporter: Elliott Clark Assignee: Elliott Clark -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11542) Unit Test KeyStoreTestUtil.java compilation failure in IBM JDK
[ https://issues.apache.org/jira/browse/HBASE-11542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162199#comment-14162199 ] Andrew Purtell commented on HBASE-11542: Instead of using internal security APIs which are 1) nonstandard and 2) at least in the case of Oracle Java going to disappear, can we instead use keytool once to generate a test file, stringify it, and use this in the test ? Thanks Unit Test KeyStoreTestUtil.java compilation failure in IBM JDK Key: HBASE-11542 URL: https://issues.apache.org/jira/browse/HBASE-11542 Project: HBase Issue Type: Improvement Components: build, test Affects Versions: 0.99.0 Environment: RHEL 6.3 ,IBM JDK 6 Reporter: LinseyPang Priority: Minor Fix For: 2.0.0 Attachments: HBASE-11542-4.patch, HBASE-11542-5.patch, HBASE_11542-1.patch, hbase11542-0.99-v3.patch, hbase11542-0.99-v3.patch, hbase11542-0.99-v3.patch, hbase_11542-v2.patch, sslkeystore.patch In trunk, jira HBase-10336 added a utility test KeyStoreTestUtil.java, which leverages the following sun classes: import sun.security.x509.AlgorithmId; import sun.security.x509.CertificateAlgorithmId; this cause hbase compiler failure if using IBM JDK, There are similar classes like below in IBM jdk: import com.ibm.security.x509.AlgorithmId; import com.ibm.security.x509.CertificateAlgorithmId; This jira is to add handling of the x509 references. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12189) Fix new issues found by static analysis
Elliott Clark created HBASE-12189: - Summary: Fix new issues found by static analysis Key: HBASE-12189 URL: https://issues.apache.org/jira/browse/HBASE-12189 Project: HBase Issue Type: Bug Reporter: Elliott Clark Assignee: Elliott Clark -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12190) Split thread pool larger than one results in fatal failure during region splits
Vladimir Rodionov created HBASE-12190:
-
Summary: Split thread pool larger than one results in fatal
failure during region splits
Key: HBASE-12190
URL: https://issues.apache.org/jira/browse/HBASE-12190
Project: HBase
Issue Type: Bug
Components: regionserver
Affects Versions: 2.0.0
Reporter: Vladimir Rodionov
I have been playing with different sizes for long/short compaction and split
thread poll sizes. It is definitely clear, that any size of split thread pool
large than 1 (one) results in a fatal errors during region splits.
Here is the log file snippet of a local test case :
{code}
2014-10-07 11:04:48,441
[INFO|org.apache.hadoop.hbase.regionserver.HRegionFileSystem|HRegionFileSystem]
The
hdfs://localhost:50215/user/vrodionov/hbase/data/default/TABLE_A/0ace9f564c05043a45cb44b2867432f8/.splits
directory exists. Hence deleting it to recreate it
put: 23
2014-10-07 11:04:48,697 [INFO|BlockStateChange|BlockManager] BLOCK*
addStoredBlock: blockMap updated: 127.0.0.1:50216 is added to
blk_1073741862_1038{blockUCState=COMMITTED, primaryNodeIndex=-1,
replicas=[ReplicaUnderConstruction[[DISK]DS-0b95bff8-1354-42cc-bd16-a5eafcb5bb27:NORMAL|RBW]]}
size 22106983
2014-10-07 11:04:49,100
[INFO|org.apache.hadoop.hbase.regionserver.DefaultStoreFlusher|DefaultStoreFlusher]
Flushed, sequenceid=495, memsize=63.2 M, hasBloomFilter=true, into tmp file
hdfs://localhost:50215/user/vrodionov/hbase/data/default/TABLE_A/0ace9f564c05043a45cb44b2867432f8/.tmp/8d746dd585df4669a505fe2ba0ddafe1
2014-10-07 11:04:49,110
[INFO|org.apache.hadoop.hbase.regionserver.HStore|HStore] Added
hdfs://localhost:50215/user/vrodionov/hbase/data/default/TABLE_A/0ace9f564c05043a45cb44b2867432f8/fam_a/8d746dd585df4669a505fe2ba0ddafe1,
entries=36, sequenceid=495, filesize=21.1 M
2014-10-07 11:04:49,111
[INFO|org.apache.hadoop.hbase.regionserver.HRegion|HRegion] Finished memstore
flush of ~63.17 MB/6624, currentsize=42.11 MB/4416 for region
TABLE_A,row00037607,1412705075738.0ace9f564c05043a45cb44b2867432f8. in
674ms, sequenceid=495, compaction requested=true
2014-10-07 11:04:49,111
[INFO|org.apache.hadoop.hbase.regionserver.HRegion|HRegion] Started memstore
flush for
TABLE_A,row00037607,1412705075738.0ace9f564c05043a45cb44b2867432f8.,
current region memstore size 42.11 MB
2014-10-07 11:04:49,267 [INFO|BlockStateChange|BlockManager] BLOCK*
addStoredBlock: blockMap updated: 127.0.0.1:50216 is added to
blk_1073741863_1039{blockUCState=COMMITTED, primaryNodeIndex=-1,
replicas=[ReplicaUnderConstruction[[DISK]DS-414e0e79-1c18-4469-9458-6842a0b96131:NORMAL|RBW]]}
size 14745108
2014-10-07 11:04:49,669
[INFO|org.apache.hadoop.hbase.regionserver.DefaultStoreFlusher|DefaultStoreFlusher]
Flushed, sequenceid=514, memsize=42.1 M, hasBloomFilter=true, into tmp file
hdfs://localhost:50215/user/vrodionov/hbase/data/default/TABLE_A/0ace9f564c05043a45cb44b2867432f8/.tmp/785a7048b1b849509e3e622cdaceb033
2014-10-07 11:04:49,682
[INFO|org.apache.hadoop.hbase.regionserver.HStore|HStore] Added
hdfs://localhost:50215/user/vrodionov/hbase/data/default/TABLE_A/0ace9f564c05043a45cb44b2867432f8/fam_a/785a7048b1b849509e3e622cdaceb033,
entries=24, sequenceid=514, filesize=14.1 M
2014-10-07 11:04:49,683
[INFO|org.apache.hadoop.hbase.regionserver.HRegion|HRegion] Finished memstore
flush of ~42.11 MB/4416, currentsize=0 B/0 for region
TABLE_A,row00037607,1412705075738.0ace9f564c05043a45cb44b2867432f8. in
572ms, sequenceid=514, compaction requested=true
2014-10-07 11:04:49,686
[INFO|org.apache.hadoop.hbase.regionserver.HStore|HStore] Closed fam_a
2014-10-07 11:04:49,687
[INFO|org.apache.hadoop.hbase.regionserver.HRegion|HRegion] Closed
TABLE_A,row00037607,1412705075738.0ace9f564c05043a45cb44b2867432f8.
2014-10-07 11:04:49,687
[WARN|org.apache.hadoop.hbase.regionserver.HRegion|HRegion] Region
TABLE_A,row00037607,1412705075738.0ace9f564c05043a45cb44b2867432f8. already
closed
2014-10-07 11:04:49,688
[INFO|org.apache.hadoop.hbase.regionserver.SplitRequest|SplitRequest] Running
rollback/cleanup of failed split of
TABLE_A,row00037607,1412705075738.0ace9f564c05043a45cb44b2867432f8.; Failed
to close region: already closed by another thread
java.io.IOException: Failed to close region: already closed by another thread
at
org.apache.hadoop.hbase.regionserver.SplitTransaction.clinit(SplitTransaction.java:190)
at
org.apache.hadoop.hbase.regionserver.SplitRequest.run(SplitRequest.java:65)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
2014-10-07 11:04:49,690
[ERROR|org.apache.hadoop.hbase.master.AssignmentManager|AssignmentManager]
Failed to transition region from
