[jira] [Commented] (HBASE-5437) HRegionThriftServer does not start because of a bug in HbaseHandlerMetricsProxy
[ https://issues.apache.org/jira/browse/HBASE-5437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215411#comment-13215411 ] Hudson commented on HBASE-5437: --- Integrated in HBase-TRUNK-security #121 (See [https://builds.apache.org/job/HBase-TRUNK-security/121/]) HBASE-5437 HRegionThriftServer does not start because of a bug in HbaseHandlerMetricsProxy (Scott Chen) (Revision 1293013) Result = SUCCESS tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/thrift/HbaseHandlerMetricsProxy.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/thrift/ThriftMetrics.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/thrift2/ThriftHBaseServiceHandler.java > HRegionThriftServer does not start because of a bug in > HbaseHandlerMetricsProxy > --- > > Key: HBASE-5437 > URL: https://issues.apache.org/jira/browse/HBASE-5437 > Project: HBase > Issue Type: Bug > Components: metrics, thrift >Reporter: Scott Chen >Assignee: Scott Chen > Fix For: 0.94.0 > > Attachments: HBASE-5437.D1857.1.patch, HBASE-5437.D1887.1.patch, > HBASE-5437.D1887.2.patch > > > 3.facebook.com,60020,1329865516120: Initialization of RS failed. Hence > aborting RS. > java.lang.ClassCastException: $Proxy9 cannot be cast to > org.apache.hadoop.hbase.thrift.generated.Hbase$Iface > at > org.apache.hadoop.hbase.thrift.HbaseHandlerMetricsProxy.newInstance(HbaseHandlerMetricsProxy.java:47) > at > org.apache.hadoop.hbase.thrift.ThriftServerRunner.(ThriftServerRunner.java:239) > at > org.apache.hadoop.hbase.regionserver.HRegionThriftServer.(HRegionThriftServer.java:74) > at > org.apache.hadoop.hbase.regionserver.HRegionServer.initializeThreads(HRegionServer.java:646) > at > org.apache.hadoop.hbase.regionserver.HRegionServer.preRegistrationInitialization(HRegionServer.java:546) > at > org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:658) > at java.lang.Thread.run(Thread.java:662) > 2012-02-21 15:05:18,749 FATAL org.apache.hadoop.h -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5415) FSTableDescriptors should handle random folders in hbase.root.dir better
[
https://issues.apache.org/jira/browse/HBASE-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215409#comment-13215409
]
Hudson commented on HBASE-5415:
---
Integrated in HBase-TRUNK-security #121 (See
[https://builds.apache.org/job/HBase-TRUNK-security/121/])
HBASE-5415 FSTableDescriptors should handle random folders in
hbase.root.dir better (Revision 1293042)
Result = SUCCESS
jdcryans :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/TableDescriptors.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/CatalogJanitor.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/DefaultLoadBalancer.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/handler/TableEventHandler.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/util/FSTableDescriptors.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/master/TestCatalogJanitor.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/util/TestFSTableDescriptors.java
> FSTableDescriptors should handle random folders in hbase.root.dir better
>
>
> Key: HBASE-5415
> URL: https://issues.apache.org/jira/browse/HBASE-5415
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.92.0
>Reporter: Jean-Daniel Cryans
>Assignee: Jean-Daniel Cryans
>Priority: Critical
> Fix For: 0.92.1, 0.94.0
>
> Attachments: HBASE-5415.patch
>
>
> I faked an upgrade on a test cluster using our dev data so I had to distcp
> the data between the two clusters, but after starting up and doing the
> migration and whatnot the web UI didn't show any table. The reason was in the
> master's log:
> {quote}
> org.apache.hadoop.hbase.TableExistsException: No descriptor for
> _distcp_logs_e0ehek
> at
> org.apache.hadoop.hbase.util.FSTableDescriptors.get(FSTableDescriptors.java:164)
> at
> org.apache.hadoop.hbase.util.FSTableDescriptors.getAll(FSTableDescriptors.java:182)
> at
> org.apache.hadoop.hbase.master.HMaster.getHTableDescriptors(HMaster.java:1554)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:364)
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1326)
> {quote}
> I don't think we need to show a full stack (just a WARN maybe), this
> shouldn't kill the request (still see tables in the web UI), and why is that
> a TableExistsException?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4218) Data Block Encoding of KeyValues (aka delta encoding / prefix compression)
[ https://issues.apache.org/jira/browse/HBASE-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215404#comment-13215404 ] Hudson commented on HBASE-4218: --- Integrated in HBase-TRUNK-security #121 (See [https://builds.apache.org/job/HBase-TRUNK-security/121/]) [jira] [HBASE-5470] Make DataBlockEncodingTool work correctly with no native compression codecs loaded Summary: DataBlockEncodingTool was fixed as part of porting data block encoding (HBASE-4218) to 89-fb (https://reviews.facebook.net/rHBASEEIGHTNINEFBBRANCH1245291, https://reviews.facebook.net/D1659). The bug being fixed here appeared when using GZ as baseline compression codec but not loading native Hadoop libraries, in which case the compressor instance would be null. Test Plan: Run DataBlockEncoding tool with GZ (no native codecs) and LZO (with native codecs) as baseline (Hadoop-level) compression codecs Reviewers: JIRA, Kannan, mcorgan, lhofhansl, todd, stack, tedyu Reviewed By: tedyu Differential Revision: https://reviews.facebook.net/D1917 (Revision 1293057) Result = SUCCESS mbautin : Files : * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/DataBlockEncodingTool.java > Data Block Encoding of KeyValues (aka delta encoding / prefix compression) > --- > > Key: HBASE-4218 > URL: https://issues.apache.org/jira/browse/HBASE-4218 > Project: HBase > Issue Type: Improvement > Components: io >Affects Versions: 0.94.0 >Reporter: Jacek Migdal >Assignee: Mikhail Bautin > Labels: compression > Fix For: 0.94.0 > > Attachments: 0001-Delta-encoding-fixed-encoded-scanners.patch, > 0001-Delta-encoding.patch, 4218-2012-01-14.txt, 4218-v16.txt, 4218.txt, > D1659.1.patch, D1659.2.patch, D1659.3.patch, D447.1.patch, D447.10.patch, > D447.11.patch, D447.12.patch, D447.13.patch, D447.14.patch, D447.15.patch, > D447.16.patch, D447.17.patch, D447.18.patch, D447.19.patch, D447.2.patch, > D447.20.patch, D447.21.patch, D447.22.patch, D447.23.patch, D447.24.patch, > D447.25.patch, D447.26.patch, D447.3.patch, D447.4.patch, D447.5.patch, > D447.6.patch, D447.7.patch, D447.8.patch, D447.9.patch, > Data-block-encoding-2011-12-23.patch, > Delta-encoding-2012-01-17_11_09_09.patch, > Delta-encoding-2012-01-25_00_45_29.patch, > Delta-encoding-2012-01-25_16_32_14.patch, > Delta-encoding.patch-2011-12-22_11_52_07.patch, > Delta-encoding.patch-2012-01-05_15_16_43.patch, > Delta-encoding.patch-2012-01-05_16_31_44.patch, > Delta-encoding.patch-2012-01-05_16_31_44_copy.patch, > Delta-encoding.patch-2012-01-05_18_50_47.patch, > Delta-encoding.patch-2012-01-07_14_12_48.patch, > Delta-encoding.patch-2012-01-13_12_20_07.patch, > Delta_encoding_with_memstore_TS.patch, open-source.diff > > > A compression for keys. Keys are sorted in HFile and they are usually very > similar. Because of that, it is possible to design better compression than > general purpose algorithms, > It is an additional step designed to be used in memory. It aims to save > memory in cache as well as speeding seeks within HFileBlocks. It should > improve performance a lot, if key lengths are larger than value lengths. For > example, it makes a lot of sense to use it when value is a counter. > Initial tests on real data (key length = ~ 90 bytes , value length = 8 bytes) > shows that I could achieve decent level of compression: > key compression ratio: 92% > total compression ratio: 85% > LZO on the same data: 85% > LZO after delta encoding: 91% > While having much better performance (20-80% faster decompression ratio than > LZO). Moreover, it should allow far more efficient seeking which should > improve performance a bit. > It seems that a simple compression algorithms are good enough. Most of the > savings are due to prefix compression, int128 encoding, timestamp diffs and > bitfields to avoid duplication. That way, comparisons of compressed data can > be much faster than a byte comparator (thanks to prefix compression and > bitfields). > In order to implement it in HBase two important changes in design will be > needed: > -solidify interface to HFileBlock / HFileReader Scanner to provide seeking > and iterating; access to uncompressed buffer in HFileBlock will have bad > performance > -extend comparators to support comparison assuming that N first bytes are > equal (or some fields are equal) > Link to a discussion about something similar: > http://search-hadoop.com/m/5aqGXJEnaD1/hbase+windows&subj=Re+prefix+compression -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see:
[jira] [Commented] (HBASE-5465) [book] changing "book" to "reference guide" (content only, not filenames)
[ https://issues.apache.org/jira/browse/HBASE-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215405#comment-13215405 ] Hudson commented on HBASE-5465: --- Integrated in HBase-TRUNK-security #121 (See [https://builds.apache.org/job/HBase-TRUNK-security/121/]) hbase-5465 book.xml, preface.xml - changing "book" to "reference guide" (Revision 1292921) Result = SUCCESS > [book] changing "book" to "reference guide" (content only, not filenames) > - > > Key: HBASE-5465 > URL: https://issues.apache.org/jira/browse/HBASE-5465 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: docbkx_hbase_5465.patch > > > book.xml > preface.xml > Changing "book" to "reference guide" > Note: the filenames are still the same. This is only a change to the way > the document refers to itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5468) [book] updating copyright in Reference Guide
[ https://issues.apache.org/jira/browse/HBASE-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215408#comment-13215408 ] Hudson commented on HBASE-5468: --- Integrated in HBase-TRUNK-security #121 (See [https://builds.apache.org/job/HBase-TRUNK-security/121/]) hbase-5468 book.xml - updating copyright to 2012 (Revision 1292998) Result = SUCCESS > [book] updating copyright in Reference Guide > > > Key: HBASE-5468 > URL: https://issues.apache.org/jira/browse/HBASE-5468 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Trivial > Attachments: book_hbase_5468.xml.patch > > > book.xml > updating copyright to 2012 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5466) Opening a table also opens the metatable and never closes it.
[ https://issues.apache.org/jira/browse/HBASE-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215406#comment-13215406 ] Hudson commented on HBASE-5466: --- Integrated in HBase-TRUNK-security #121 (See [https://builds.apache.org/job/HBase-TRUNK-security/121/]) HBASE-5466 Opening a table also opens the metatable and never closes it (Ashley Taylor) (Revision 1293047) Result = SUCCESS tedyu : Files : * /hbase/trunk/CHANGES.txt * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/MetaScanner.java > Opening a table also opens the metatable and never closes it. > - > > Key: HBASE-5466 > URL: https://issues.apache.org/jira/browse/HBASE-5466 > Project: HBase > Issue Type: Bug > Components: client >Affects Versions: 0.90.5, 0.92.0 >Reporter: Ashley Taylor >Assignee: Ashley Taylor > Fix For: 0.92.1 > > Attachments: MetaScanner_HBASE_5466(2).patch, > MetaScanner_HBASE_5466(3).patch, MetaScanner_HBASE_5466.patch > > > Having upgraded to CDH3U3 version of hbase we found we had a zookeeper > connection leak, tracking it down we found that closing the connection will > only close the zookeeper connection if all calls to get the connection have > been closed, there is incCount and decCount in the HConnection class, > When a table is opened it makes a call to the metascanner class which opens a > connection to the meta table, this table never gets closed. > This caused the count in the HConnection class to never return to zero > meaning that the zookeeper connection will not close when we close all the > tables or calling > HConnectionManager.deleteConnection(config, true); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5467) changing homepage to refer to 'reference guide'
[ https://issues.apache.org/jira/browse/HBASE-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215407#comment-13215407 ] Hudson commented on HBASE-5467: --- Integrated in HBase-TRUNK-security #121 (See [https://builds.apache.org/job/HBase-TRUNK-security/121/]) hbase-5467 - change homepage to refer to 'reference guide' (Revision 1292958) Result = SUCCESS > changing homepage to refer to 'reference guide' > --- > > Key: HBASE-5467 > URL: https://issues.apache.org/jira/browse/HBASE-5467 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: site_hbase_5467.patch > > > index.xml > site.xml > Changing reference from "book" to "reference guide" on home page and left-nav. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5415) FSTableDescriptors should handle random folders in hbase.root.dir better
[
https://issues.apache.org/jira/browse/HBASE-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215350#comment-13215350
]
Hudson commented on HBASE-5415:
---
Integrated in HBase-0.92 #301 (See
[https://builds.apache.org/job/HBase-0.92/301/])
HBASE-5415 FSTableDescriptors should handle random folders in
hbase.root.dir better (Revision 1293041)
Result = SUCCESS
jdcryans :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/TableDescriptors.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/CatalogJanitor.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/DefaultLoadBalancer.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/handler/TableEventHandler.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/util/FSTableDescriptors.java
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/master/TestCatalogJanitor.java
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/TestFSTableDescriptors.java
> FSTableDescriptors should handle random folders in hbase.root.dir better
>
>
> Key: HBASE-5415
> URL: https://issues.apache.org/jira/browse/HBASE-5415
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.92.0
>Reporter: Jean-Daniel Cryans
>Assignee: Jean-Daniel Cryans
>Priority: Critical
> Fix For: 0.92.1, 0.94.0
>
> Attachments: HBASE-5415.patch
>
>
> I faked an upgrade on a test cluster using our dev data so I had to distcp
> the data between the two clusters, but after starting up and doing the
> migration and whatnot the web UI didn't show any table. The reason was in the
> master's log:
> {quote}
> org.apache.hadoop.hbase.TableExistsException: No descriptor for
> _distcp_logs_e0ehek
> at
> org.apache.hadoop.hbase.util.FSTableDescriptors.get(FSTableDescriptors.java:164)
> at
> org.apache.hadoop.hbase.util.FSTableDescriptors.getAll(FSTableDescriptors.java:182)
> at
> org.apache.hadoop.hbase.master.HMaster.getHTableDescriptors(HMaster.java:1554)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:364)
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1326)
> {quote}
> I don't think we need to show a full stack (just a WARN maybe), this
> shouldn't kill the request (still see tables in the web UI), and why is that
> a TableExistsException?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5466) Opening a table also opens the metatable and never closes it.
[ https://issues.apache.org/jira/browse/HBASE-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215349#comment-13215349 ] Hudson commented on HBASE-5466: --- Integrated in HBase-0.92 #301 (See [https://builds.apache.org/job/HBase-0.92/301/]) HBASE-5466 Opening a table also opens the metatable and never closes it - place JIRA at the right position in CHANGES.txt (Ashley Taylor) (Revision 1293048) HBASE-5466 Opening a table also opens the metatable and never closes it (Ashley Taylor) (Revision 1293045) Result = SUCCESS tedyu : Files : * /hbase/branches/0.92/CHANGES.txt tedyu : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/client/MetaScanner.java > Opening a table also opens the metatable and never closes it. > - > > Key: HBASE-5466 > URL: https://issues.apache.org/jira/browse/HBASE-5466 > Project: HBase > Issue Type: Bug > Components: client >Affects Versions: 0.90.5, 0.92.0 >Reporter: Ashley Taylor >Assignee: Ashley Taylor > Fix For: 0.92.1 > > Attachments: MetaScanner_HBASE_5466(2).patch, > MetaScanner_HBASE_5466(3).patch, MetaScanner_HBASE_5466.patch > > > Having upgraded to CDH3U3 version of hbase we found we had a zookeeper > connection leak, tracking it down we found that closing the connection will > only close the zookeeper connection if all calls to get the connection have > been closed, there is incCount and decCount in the HConnection class, > When a table is opened it makes a call to the metascanner class which opens a > connection to the meta table, this table never gets closed. > This caused the count in the HConnection class to never return to zero > meaning that the zookeeper connection will not close when we close all the > tables or calling > HConnectionManager.deleteConnection(config, true); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5357) Use builder pattern in HColumnDescriptor
[
https://issues.apache.org/jira/browse/HBASE-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215249#comment-13215249
]
Hudson commented on HBASE-5357:
---
Integrated in HBase-TRUNK #2668 (See
[https://builds.apache.org/job/HBase-TRUNK/2668/])
[jira] [HBASE-5357] Refactoring: use the builder pattern for
HColumnDescriptor
Summary: Deprecate three ugly HColumnDescriptor constructors and use a "builder"
pattern instead, e.g. new
HColumnDescriptor(cfName).setMaxVersions(5).setBlockSize(8192), etc. Setters
have now become "builder" methods.
Test Plan: Run unit tests
Reviewers: JIRA, todd, stack, tedyu, Kannan, Karthik, Liyin
Reviewed By: tedyu
Differential Revision: https://reviews.facebook.net/D1851 (Revision 1293026)
Result = SUCCESS
mbautin :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/HTableDescriptor.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/UnmodifyableHColumnDescriptor.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/thrift/ThriftUtilities.java
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/HBaseTestCase.java
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/TestSerialization.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/io/encoding/TestEncodedSeekers.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/io/hfile/TestCacheOnWrite.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/io/hfile/TestForceCacheImportantBlocks.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/io/hfile/TestScannerSelectionUsingTTL.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/mapreduce/TestHFileOutputFormat.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportExport.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestBlocksRead.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestColumnSeeking.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestFSErrorsExposed.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestMultiColumnScanner.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestScanWithBloomError.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestScanner.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestSeekOptimizations.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestWideScanner.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/thrift2/TestThriftHBaseServiceHandler.java
> Use builder pattern in HColumnDescriptor
>
>
> Key: HBASE-5357
> URL: https://issues.apache.org/jira/browse/HBASE-5357
> Project: HBase
> Issue Type: Improvement
>Reporter: Mikhail Bautin
>Assignee: Mikhail Bautin
> Attachments: D1851.1.patch, D1851.2.patch, D1851.3.patch,
> D1851.4.patch,
> Use-builder-pattern-for-HColumnDescriptor-2012-02-21_19_13_35.patch,
> Use-builder-pattern-for-HColumnDescriptor-2012-02-23_12_42_49.patch,
> Use-builder-pattern-for-HColumnDescriptor-20120223113155-e387d251.patch
>
>
> We have five ways to create an HFile writer, two ways to create a StoreFile
> writer, and the sets of parameters keep changing, creating a lot of
> confusion, especially when porting patches across branches. The same thing is
> happening to HColumnDescriptor. I think we should move to a "builder pattern"
> solution, e.g.
> {code:java}
> HFileWriter w = HFile.getWriterBuilder(conf, )
> .setParameter1(value1)
> .setParameter2(value2)
> ...
> .build();
> {code}
> Each parameter setter being on its own line will make merges/cherry-pick work
> properly, we will not have to even mention default parameters again, and we
> can eliminate a dozen impossible-to-remember constructors.
> This particular JIRA addresses the HColumnDescriptor refactoring. For
> StoreFile/HFile refactoring see HBASE-5442.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5468) [book] updating copyright in Reference Guide
[ https://issues.apache.org/jira/browse/HBASE-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215246#comment-13215246 ] Hudson commented on HBASE-5468: --- Integrated in HBase-TRUNK #2668 (See [https://builds.apache.org/job/HBase-TRUNK/2668/]) hbase-5468 book.xml - updating copyright to 2012 (Revision 1292998) Result = SUCCESS > [book] updating copyright in Reference Guide > > > Key: HBASE-5468 > URL: https://issues.apache.org/jira/browse/HBASE-5468 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Trivial > Attachments: book_hbase_5468.xml.patch > > > book.xml > updating copyright to 2012 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5460) Add protobuf as M/R dependency jar
[ https://issues.apache.org/jira/browse/HBASE-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215247#comment-13215247 ] Hudson commented on HBASE-5460: --- Integrated in HBase-TRUNK #2668 (See [https://builds.apache.org/job/HBase-TRUNK/2668/]) HBASE-5460 Add protobuf as M/R dependency jar (Revision 1292656) Result = SUCCESS larsh : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java > Add protobuf as M/R dependency jar > -- > > Key: HBASE-5460 > URL: https://issues.apache.org/jira/browse/HBASE-5460 > Project: HBase > Issue Type: Sub-task > Components: mapreduce >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl > Fix For: 0.94.0 > > Attachments: 5460.txt > > > Getting this from M/R jobs (Export for example): > Error: java.lang.ClassNotFoundException: com.google.protobuf.Message > at java.net.URLClassLoader$1.run(URLClassLoader.java:217) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:205) > at java.lang.ClassLoader.loadClass(ClassLoader.java:321) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294) > at java.lang.ClassLoader.loadClass(ClassLoader.java:266) > at > org.apache.hadoop.hbase.io.HbaseObjectWritable.(HbaseObjectWritable.java:262) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5467) changing homepage to refer to 'reference guide'
[ https://issues.apache.org/jira/browse/HBASE-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215245#comment-13215245 ] Hudson commented on HBASE-5467: --- Integrated in HBase-TRUNK #2668 (See [https://builds.apache.org/job/HBase-TRUNK/2668/]) hbase-5467 - change homepage to refer to 'reference guide' (Revision 1292958) Result = SUCCESS > changing homepage to refer to 'reference guide' > --- > > Key: HBASE-5467 > URL: https://issues.apache.org/jira/browse/HBASE-5467 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: site_hbase_5467.patch > > > index.xml > site.xml > Changing reference from "book" to "reference guide" on home page and left-nav. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5437) HRegionThriftServer does not start because of a bug in HbaseHandlerMetricsProxy
[ https://issues.apache.org/jira/browse/HBASE-5437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215248#comment-13215248 ] Hudson commented on HBASE-5437: --- Integrated in HBase-TRUNK #2668 (See [https://builds.apache.org/job/HBase-TRUNK/2668/]) HBASE-5437 HRegionThriftServer does not start because of a bug in HbaseHandlerMetricsProxy (Scott Chen) (Revision 1293013) Result = SUCCESS tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/thrift/HbaseHandlerMetricsProxy.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/thrift/ThriftMetrics.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/thrift2/ThriftHBaseServiceHandler.java > HRegionThriftServer does not start because of a bug in > HbaseHandlerMetricsProxy > --- > > Key: HBASE-5437 > URL: https://issues.apache.org/jira/browse/HBASE-5437 > Project: HBase > Issue Type: Bug > Components: metrics, thrift >Reporter: Scott Chen >Assignee: Scott Chen > Fix For: 0.94.0 > > Attachments: HBASE-5437.D1857.1.patch, HBASE-5437.D1887.1.patch, > HBASE-5437.D1887.2.patch > > > 3.facebook.com,60020,1329865516120: Initialization of RS failed. Hence > aborting RS. > java.lang.ClassCastException: $Proxy9 cannot be cast to > org.apache.hadoop.hbase.thrift.generated.Hbase$Iface > at > org.apache.hadoop.hbase.thrift.HbaseHandlerMetricsProxy.newInstance(HbaseHandlerMetricsProxy.java:47) > at > org.apache.hadoop.hbase.thrift.ThriftServerRunner.(ThriftServerRunner.java:239) > at > org.apache.hadoop.hbase.regionserver.HRegionThriftServer.(HRegionThriftServer.java:74) > at > org.apache.hadoop.hbase.regionserver.HRegionServer.initializeThreads(HRegionServer.java:646) > at > org.apache.hadoop.hbase.regionserver.HRegionServer.preRegistrationInitialization(HRegionServer.java:546) > at > org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:658) > at java.lang.Thread.run(Thread.java:662) > 2012-02-21 15:05:18,749 FATAL org.apache.hadoop.h -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5465) [book] changing "book" to "reference guide" (content only, not filenames)
[ https://issues.apache.org/jira/browse/HBASE-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215244#comment-13215244 ] Hudson commented on HBASE-5465: --- Integrated in HBase-TRUNK #2668 (See [https://builds.apache.org/job/HBase-TRUNK/2668/]) hbase-5465 book.xml, preface.xml - changing "book" to "reference guide" (Revision 1292921) Result = SUCCESS > [book] changing "book" to "reference guide" (content only, not filenames) > - > > Key: HBASE-5465 > URL: https://issues.apache.org/jira/browse/HBASE-5465 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: docbkx_hbase_5465.patch > > > book.xml > preface.xml > Changing "book" to "reference guide" > Note: the filenames are still the same. This is only a change to the way > the document refers to itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5424) HTable meet NPE when call getRegionInfo()
[ https://issues.apache.org/jira/browse/HBASE-5424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214347#comment-13214347 ] Hudson commented on HBASE-5424: --- Integrated in HBase-TRUNK #2667 (See [https://builds.apache.org/job/HBase-TRUNK/2667/]) HBASE-5424 HTable meet NPE when call getRegionInfo() -- REVERT (Revision 1292646) HBASE-5424 HTable meet NPE when call getRegionInfo() (Revision 1292645) Result = FAILURE stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/HTable.java stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/HTable.java > HTable meet NPE when call getRegionInfo() > - > > Key: HBASE-5424 > URL: https://issues.apache.org/jira/browse/HBASE-5424 > Project: HBase > Issue Type: Bug >Affects Versions: 0.90.1, 0.90.5 >Reporter: junhua yang > Attachments: 5424-v3.patch, 5424-v3.patch, HBASE-5424.patch, > HBase-5424_v2.patch > > Original Estimate: 48h > Remaining Estimate: 48h > > We meet NPE when call getRegionInfo() in testing environment. > Exception in thread "main" java.lang.NullPointerException > at org.apache.hadoop.hbase.util.Writables.getWritable(Writables.java:75) > at org.apache.hadoop.hbase.util.Writables.getHRegionInfo(Writables.java:119) > at org.apache.hadoop.hbase.client.HTable$2.processRow(HTable.java:395) > at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:190) > at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:95) > at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:73) > at org.apache.hadoop.hbase.client.HTable.getRegionsInfo(HTable.java:418) > This NPE also make the table.jsp can't show the region information of this > table. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5423) Regionserver may block forever on waitOnAllRegionsToClose when aborting
[ https://issues.apache.org/jira/browse/HBASE-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214348#comment-13214348 ] Hudson commented on HBASE-5423: --- Integrated in HBase-TRUNK #2667 (See [https://builds.apache.org/job/HBase-TRUNK/2667/]) HBASE-5423 Regionserver may block forever on waitOnAllRegionsToClose when aborting (Revision 1292647) Result = FAILURE stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java > Regionserver may block forever on waitOnAllRegionsToClose when aborting > --- > > Key: HBASE-5423 > URL: https://issues.apache.org/jira/browse/HBASE-5423 > Project: HBase > Issue Type: Bug > Components: regionserver >Reporter: chunhui shen >Assignee: chunhui shen > Fix For: 0.94.0 > > Attachments: hbase-5423.patch, hbase-5423v2.patch > > > If closeRegion throws any exception (It would be caused by FS ) when RS is > aborting, > RS will block forever on waitOnAllRegionsToClose(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5424) HTable meet NPE when call getRegionInfo()
[ https://issues.apache.org/jira/browse/HBASE-5424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214336#comment-13214336 ] Hudson commented on HBASE-5424: --- Integrated in HBase-TRUNK-security #120 (See [https://builds.apache.org/job/HBase-TRUNK-security/120/]) HBASE-5424 HTable meet NPE when call getRegionInfo() (Revision 1292645) Result = FAILURE stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/HTable.java > HTable meet NPE when call getRegionInfo() > - > > Key: HBASE-5424 > URL: https://issues.apache.org/jira/browse/HBASE-5424 > Project: HBase > Issue Type: Bug >Affects Versions: 0.90.1, 0.90.5 >Reporter: junhua yang > Attachments: 5424-v3.patch, 5424-v3.patch, HBASE-5424.patch, > HBase-5424_v2.patch > > Original Estimate: 48h > Remaining Estimate: 48h > > We meet NPE when call getRegionInfo() in testing environment. > Exception in thread "main" java.lang.NullPointerException > at org.apache.hadoop.hbase.util.Writables.getWritable(Writables.java:75) > at org.apache.hadoop.hbase.util.Writables.getHRegionInfo(Writables.java:119) > at org.apache.hadoop.hbase.client.HTable$2.processRow(HTable.java:395) > at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:190) > at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:95) > at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:73) > at org.apache.hadoop.hbase.client.HTable.getRegionsInfo(HTable.java:418) > This NPE also make the table.jsp can't show the region information of this > table. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5209) HConnection/HMasterInterface should allow for way to get hostname of currently active master in multi-master HBase setup
[ https://issues.apache.org/jira/browse/HBASE-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213390#comment-13213390 ] Hudson commented on HBASE-5209: --- Integrated in HBase-0.92-security #93 (See [https://builds.apache.org/job/HBase-0.92-security/93/]) HBASE-5209 Addendum adds znode creation call (David Wang) (Revision 1292068) Result = FAILURE tedyu : Files : * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperWatcher.java > HConnection/HMasterInterface should allow for way to get hostname of > currently active master in multi-master HBase setup > > > Key: HBASE-5209 > URL: https://issues.apache.org/jira/browse/HBASE-5209 > Project: HBase > Issue Type: Improvement > Components: master >Affects Versions: 0.94.0, 0.90.5, 0.92.0 >Reporter: Aditya Acharya >Assignee: David S. Wang > Fix For: 0.94.0, 0.92.1 > > Attachments: 5209.addendum, HBASE_5209_v5.diff > > > I have a multi-master HBase set up, and I'm trying to programmatically > determine which of the masters is currently active. But the API does not > allow me to do this. There is a getMaster() method in the HConnection class, > but it returns an HMasterInterface, whose methods do not allow me to find out > which master won the last race. The API should have a > getActiveMasterHostname() or something to that effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5209) HConnection/HMasterInterface should allow for way to get hostname of currently active master in multi-master HBase setup
[ https://issues.apache.org/jira/browse/HBASE-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213167#comment-13213167 ] Hudson commented on HBASE-5209: --- Integrated in HBase-0.92 #296 (See [https://builds.apache.org/job/HBase-0.92/296/]) HBASE-5209 Addendum adds znode creation call (David Wang) (Revision 1292068) Result = FAILURE tedyu : Files : * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperWatcher.java > HConnection/HMasterInterface should allow for way to get hostname of > currently active master in multi-master HBase setup > > > Key: HBASE-5209 > URL: https://issues.apache.org/jira/browse/HBASE-5209 > Project: HBase > Issue Type: Improvement > Components: master >Affects Versions: 0.94.0, 0.90.5, 0.92.0 >Reporter: Aditya Acharya >Assignee: David S. Wang > Fix For: 0.94.0, 0.92.1 > > Attachments: 5209.addendum, HBASE_5209_v5.diff > > > I have a multi-master HBase set up, and I'm trying to programmatically > determine which of the masters is currently active. But the API does not > allow me to do this. There is a getMaster() method in the HConnection class, > but it returns an HMasterInterface, whose methods do not allow me to find out > which master won the last race. The API should have a > getActiveMasterHostname() or something to that effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5209) HConnection/HMasterInterface should allow for way to get hostname of currently active master in multi-master HBase setup
[ https://issues.apache.org/jira/browse/HBASE-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212650#comment-13212650 ] Hudson commented on HBASE-5209: --- Integrated in HBase-0.92-security #92 (See [https://builds.apache.org/job/HBase-0.92-security/92/]) HBASE-5209 HConnection/HMasterInterface should allow for way to get hostname of currently active master in multi-master HBase setup -- FIX BUILD ON 0.92; ADDENDUM (Revision 1291592) Result = FAILURE stack : Files : * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/master/TestMasterFailover.java > HConnection/HMasterInterface should allow for way to get hostname of > currently active master in multi-master HBase setup > > > Key: HBASE-5209 > URL: https://issues.apache.org/jira/browse/HBASE-5209 > Project: HBase > Issue Type: Improvement > Components: master >Affects Versions: 0.94.0, 0.90.5, 0.92.0 >Reporter: Aditya Acharya >Assignee: David S. Wang > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE_5209_v5.diff > > > I have a multi-master HBase set up, and I'm trying to programmatically > determine which of the masters is currently active. But the API does not > allow me to do this. There is a getMaster() method in the HConnection class, > but it returns an HMasterInterface, whose methods do not allow me to find out > which master won the last race. The API should have a > getActiveMasterHostname() or something to that effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5209) HConnection/HMasterInterface should allow for way to get hostname of currently active master in multi-master HBase setup
[ https://issues.apache.org/jira/browse/HBASE-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212457#comment-13212457 ] Hudson commented on HBASE-5209: --- Integrated in HBase-0.92 #294 (See [https://builds.apache.org/job/HBase-0.92/294/]) HBASE-5209 HConnection/HMasterInterface should allow for way to get hostname of currently active master in multi-master HBase setup -- FIX BUILD ON 0.92; ADDENDUM (Revision 1291592) Result = FAILURE stack : Files : * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/master/TestMasterFailover.java > HConnection/HMasterInterface should allow for way to get hostname of > currently active master in multi-master HBase setup > > > Key: HBASE-5209 > URL: https://issues.apache.org/jira/browse/HBASE-5209 > Project: HBase > Issue Type: Improvement > Components: master >Affects Versions: 0.94.0, 0.90.5, 0.92.0 >Reporter: Aditya Acharya >Assignee: David S. Wang > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE_5209_v5.diff > > > I have a multi-master HBase set up, and I'm trying to programmatically > determine which of the masters is currently active. But the API does not > allow me to do this. There is a getMaster() method in the HConnection class, > but it returns an HMasterInterface, whose methods do not allow me to find out > which master won the last race. The API should have a > getActiveMasterHostname() or something to that effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5436) Right-size the map when reading attributes.
[ https://issues.apache.org/jira/browse/HBASE-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212393#comment-13212393 ] Hudson commented on HBASE-5436: --- Integrated in HBase-TRUNK-security #118 (See [https://builds.apache.org/job/HBase-TRUNK-security/118/]) HBASE-5436 Right-size the map when reading attributes. (Revision 1291463) Result = FAILURE stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/OperationWithAttributes.java > Right-size the map when reading attributes. > --- > > Key: HBASE-5436 > URL: https://issues.apache.org/jira/browse/HBASE-5436 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.92.0 >Reporter: Benoit Sigoure >Assignee: Benoit Sigoure >Priority: Trivial > Labels: performance > Fix For: 0.94.0 > > Attachments: 0001-Right-size-the-map-when-reading-attributes.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5195) [Coprocessors] preGet hook does not allow overriding or wrapping filter on incoming Get
[ https://issues.apache.org/jira/browse/HBASE-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212160#comment-13212160 ] Hudson commented on HBASE-5195: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5195 [Coprocessors] preGet hook does not allow overriding or wrapping filter on incoming Get (Revision 1245765) Result = FAILURE stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java > [Coprocessors] preGet hook does not allow overriding or wrapping filter on > incoming Get > --- > > Key: HBASE-5195 > URL: https://issues.apache.org/jira/browse/HBASE-5195 > Project: HBase > Issue Type: Bug >Affects Versions: 0.94.0, 0.92.0 >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-5195.patch > > > Without the ability to wrap the internal Scan on the Get, we can't override > (or protect, in the case of access control) Gets as we can Scans. The result > is inconsistent behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5364) Fix source files missing licenses in 0.92 and trunk
[ https://issues.apache.org/jira/browse/HBASE-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212162#comment-13212162 ] Hudson commented on HBASE-5364: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5364 Fix source files missing licenses in 0.92 and trunk (Revision 1242899) Result = FAILURE jmhsieh : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/docbkx/build.xml > Fix source files missing licenses in 0.92 and trunk > --- > > Key: HBASE-5364 > URL: https://issues.apache.org/jira/browse/HBASE-5364 > Project: HBase > Issue Type: Bug >Affects Versions: 0.94.0, 0.92.0 >Reporter: Jonathan Hsieh >Assignee: Elliott Clark >Priority: Blocker > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-5364-1.patch, hbase-5364-0.92.patch, > hbase-5364-v2.patch > > > running 'mvn rat:check' shows that a few files have snuck in that do not have > proper apache licenses. Ideally we should fix these before we cut another > release/release candidate. > This is a blocker for 0.94, and probably should be for the other branches as > well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5197) [replication] Handle socket timeouts in ReplicationSource to prevent DDOS
[ https://issues.apache.org/jira/browse/HBASE-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212163#comment-13212163 ] Hudson commented on HBASE-5197: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5197 [replication] Handle socket timeouts in ReplicationSource to prevent DDOS (Revision 1243736) Result = FAILURE jdcryans : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java > [replication] Handle socket timeouts in ReplicationSource to prevent DDOS > - > > Key: HBASE-5197 > URL: https://issues.apache.org/jira/browse/HBASE-5197 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.90.5 >Reporter: Jean-Daniel Cryans >Assignee: Jean-Daniel Cryans > Fix For: 0.94.0, 0.90.6, 0.92.1 > > Attachments: HBASE-5197-v2.patch, HBASE-5197.patch > > > Kind of like HBASE-4462 but for replication. If while replicating you get a > socket timeout, the last thing you want to do is to retry it right away. > Since we can't fail the replication thread, the best I can think of is to > sleep a really long amount of time. > Planning to bring this to all branches. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5209) HConnection/HMasterInterface should allow for way to get hostname of currently active master in multi-master HBase setup
[ https://issues.apache.org/jira/browse/HBASE-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212165#comment-13212165 ] Hudson commented on HBASE-5209: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5209 HConnection/HMasterInterface should allow for way to get hostname of currently active master in multi-master HBase setup (Revision 1290943) Result = FAILURE stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/ClusterStatus.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/ActiveMasterManager.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/zookeeper/ZKUtil.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperWatcher.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/master/TestActiveMasterManager.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/master/TestMasterFailover.java > HConnection/HMasterInterface should allow for way to get hostname of > currently active master in multi-master HBase setup > > > Key: HBASE-5209 > URL: https://issues.apache.org/jira/browse/HBASE-5209 > Project: HBase > Issue Type: Improvement > Components: master >Affects Versions: 0.94.0, 0.90.5, 0.92.0 >Reporter: Aditya Acharya >Assignee: David S. Wang > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE_5209_v5.diff > > > I have a multi-master HBase set up, and I'm trying to programmatically > determine which of the masters is currently active. But the API does not > allow me to do this. There is a getMaster() method in the HConnection class, > but it returns an HMasterInterface, whose methods do not allow me to find out > which master won the last race. The API should have a > getActiveMasterHostname() or something to that effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5398) HBase shell disable_all/enable_all/drop_all promp wrong tables for confirmation
[ https://issues.apache.org/jira/browse/HBASE-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212164#comment-13212164 ] Hudson commented on HBASE-5398: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5398 HBase shell disable_all/enable_all/drop_all promp wrong tables for confirmation (Revision 1244171) Result = FAILURE stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/ruby/shell/commands/disable_all.rb * /hbase/branches/0.92/src/main/ruby/shell/commands/drop_all.rb * /hbase/branches/0.92/src/main/ruby/shell/commands/enable_all.rb > HBase shell disable_all/enable_all/drop_all promp wrong tables for > confirmation > --- > > Key: HBASE-5398 > URL: https://issues.apache.org/jira/browse/HBASE-5398 > Project: HBase > Issue Type: Bug > Components: scripts >Affects Versions: 0.94.0, 0.92.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.94.0, 0.92.1 > > Attachments: hbase-5398.patch > > > When using hbase shell to disable_all/enable_all/drop_all tables, the tables > prompted for confirmation are wrong. > For example, disable_all 'test*' > will ask form confirmation to diable tables like: > mytest1 > test123 > Fortunately, these tables will not be disabled actually since Java pattern > doesn't match this way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5279) NPE in Master after upgrading to 0.92.0
[
https://issues.apache.org/jira/browse/HBASE-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212159#comment-13212159
]
Hudson commented on HBASE-5279:
---
Integrated in HBase-0.92-security #91 (See
[https://builds.apache.org/job/HBase-0.92-security/91/])
HBASE-5279 NPE in Master after upgrading to 0.92.0 (Revision 1245769)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/catalog/MetaReader.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
> NPE in Master after upgrading to 0.92.0
> ---
>
> Key: HBASE-5279
> URL: https://issues.apache.org/jira/browse/HBASE-5279
> Project: HBase
> Issue Type: Bug
> Components: master
>Affects Versions: 0.92.0
>Reporter: Tobias Herbert
>Priority: Critical
> Fix For: 0.92.1
>
> Attachments: HBASE-5279-v2.patch, HBASE-5279.patch
>
>
> I have upgraded my environment from 0.90.4 to 0.92.0
> after the table migration I get the following error in the master (permanent)
> {noformat}
> 2012-01-25 18:23:48,648 FATAL master-namenode,6,1327512209588
> org.apache.hadoop.hbase.master.HMaster - Unhandled exception. Starting
> shutdown.
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.AssignmentManager.rebuildUserRegions(AssignmentManager.java:2190)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.joinCluster(AssignmentManager.java:323)
> at
> org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:501)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:326)
> at java.lang.Thread.run(Thread.java:662)
> 2012-01-25 18:23:48,650 INFO namenode,6,1327512209588
> org.apache.hadoop.hbase.master.HMaster - Aborting
> {noformat}
> I think that's because I had a hard crash in the cluster a while ago - and
> the following WARN since then
> {noformat}
> 2012-01-25 21:20:47,121 WARN namenode,6,1327513078123-CatalogJanitor
> org.apache.hadoop.hbase.master.CatalogJanitor - REGIONINFO_QUALIFIER is empty
> in keyvalues={emails,,xxx./info:server/1314336400471/Put/vlen=38,
> emails,,1314189353300.xxx./info:serverstartcode/1314336400471/Put/vlen=8}
> {noformat}
> my patch was simple to go around the NPE (as the other code around the lines)
> but I don't know if that's correct
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5200) AM.ProcessRegionInTransition() and AM.handleRegion() race thus leaving the region assignment inconsistent
[
https://issues.apache.org/jira/browse/HBASE-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212158#comment-13212158
]
Hudson commented on HBASE-5200:
---
Integrated in HBase-0.92-security #91 (See
[https://builds.apache.org/job/HBase-0.92-security/91/])
HBASE-5200 AM.ProcessRegionInTransition() and AM.handleRegion() race thus
leaving the region assignment inconsistent (Revision 1290855)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
> AM.ProcessRegionInTransition() and AM.handleRegion() race thus leaving the
> region assignment inconsistent
> -
>
> Key: HBASE-5200
> URL: https://issues.apache.org/jira/browse/HBASE-5200
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.90.5
>Reporter: ramkrishna.s.vasudevan
>Assignee: ramkrishna.s.vasudevan
> Fix For: 0.94.0, 0.92.1
>
> Attachments: 5200-test.txt, 5200-v2.txt, 5200-v3.txt,
> 5200-v4-092.txt, 5200-v4.txt, 5200-v4no-prefix.txt, HBASE-5200.patch,
> HBASE-5200_1.patch, HBASE-5200_trunk_latest_with_test_2.patch,
> TEST-org.apache.hadoop.hbase.master.TestRestartCluster.xml,
> hbase-5200_90_latest.patch, hbase-5200_90_latest_new.patch
>
>
> This is the scenario
> Consider a case where the balancer is going on thus trying to close regions
> in a RS.
> Before we could close a master switch happens.
> On Master switch the set of nodes that are in RIT is collected and we first
> get Data and start watching the node
> After that the node data is added into RIT.
> Now by this time (before adding to RIT) if the RS to which close was called
> does a transition in AM.handleRegion() we miss the handling saying RIT state
> was null.
> {code}
> 2012-01-13 10:50:46,358 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> a66d281d231dfcaea97c270698b26b6f from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,358 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> c12e53bfd48ddc5eec507d66821c4d23 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,358 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> 59ae13de8c1eb325a0dd51f4902d2052 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> f45bc9614d7575f35244849af85aa078 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> cc3ecd7054fe6cd4a1159ed92fd62641 from server
> HOST-192-168-47-204,20020,1326342744518 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> 3af40478a17fee96b4a192b22c90d5a2 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> e6096a8466e730463e10d3d61f809b92 from server
> HOST-192-168-47-204,20020,1326342744518 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> 4806781a1a23066f7baed22b4d237e24 from server
> HOST-192-168-47-204,20020,1326342744518 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> d69e104131accaefe21dcc01fddc7629 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> {code}
> In branch the CLOSING node is created by RS thus leading to more
> inconsistency.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIR
[jira] [Commented] (HBASE-5288) Security source code dirs missing from 0.92.0 release tarballs.
[ https://issues.apache.org/jira/browse/HBASE-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212161#comment-13212161 ] Hudson commented on HBASE-5288: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5288 Security source code dirs missing from 0.92.0 release tarballs (Revision 1242456) Result = FAILURE jmhsieh : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/assembly/all.xml > Security source code dirs missing from 0.92.0 release tarballs. > --- > > Key: HBASE-5288 > URL: https://issues.apache.org/jira/browse/HBASE-5288 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 0.94.0, 0.92.0 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh >Priority: Blocker > Fix For: 0.94.0, 0.92.1 > > Attachments: hbase-5288.patch > > > The release tarballs have a compiled version of the hbase jars and the > security tarball seems to have the compiled security bits. However, the > source code and resources for security implementation are missing from the > release tarballs in both distributions. They should be included in both. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5255) Use singletons for OperationStatus to save memory
[
https://issues.apache.org/jira/browse/HBASE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212156#comment-13212156
]
Hudson commented on HBASE-5255:
---
Integrated in HBase-0.92-security #91 (See
[https://builds.apache.org/job/HBase-0.92-security/91/])
HBASE-5432 Hunk missed applying 'hbase-5255 Use singletons for
OperationStatus to save memory' (Revision 1290862)
Result = FAILURE
> Use singletons for OperationStatus to save memory
> -
>
> Key: HBASE-5255
> URL: https://issues.apache.org/jira/browse/HBASE-5255
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
>Affects Versions: 0.90.5, 0.92.0
>Reporter: Benoit Sigoure
>Assignee: Benoit Sigoure
>Priority: Minor
> Labels: performance
> Fix For: 0.94.0, 0.92.1
>
> Attachments: 5255-92.txt, 5255-v2.txt,
> HBASE-5255-0.92-Use-singletons-to-remove-unnecessary-memory-allocati.patch,
> HBASE-5255-trunk-Use-singletons-to-remove-unnecessary-memory-allocati.patch
>
>
> Every single {{Put}} causes the allocation of at least one
> {{OperationStatus}}, yet {{OperationStatus}} is almost always stateless, so
> these allocations are unnecessary and could be avoided. Attached patch adds
> a few singletons and uses them, with no public API change. I didn't test the
> patches, but you get the idea.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5294) Make sure javadoc is included in tarball bundle when we release
[ https://issues.apache.org/jira/browse/HBASE-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212148#comment-13212148 ] Hudson commented on HBASE-5294: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5294 Make sure javadoc is included in tarball bundle when we release (Revision 1245826) Result = FAILURE stack : Files : * /hbase/branches/0.92/pom.xml > Make sure javadoc is included in tarball bundle when we release > --- > > Key: HBASE-5294 > URL: https://issues.apache.org/jira/browse/HBASE-5294 > Project: HBase > Issue Type: Task >Affects Versions: 0.92.0 >Reporter: stack >Assignee: Shaneal Manek >Priority: Critical > Fix For: 0.94.0, 0.92.1 > > Attachments: hbase-5294.patch > > > 0.92.0 doesn't have javadoc in the tarball. Fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5345) CheckAndPut doesn't work when value is empty byte[]
[ https://issues.apache.org/jira/browse/HBASE-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212151#comment-13212151 ] Hudson commented on HBASE-5345: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5345 CheckAndPut doesn't work when value is empty byte[] (Evert Arckens) (Revision 1241971) Result = FAILURE tedyu : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java > CheckAndPut doesn't work when value is empty byte[] > --- > > Key: HBASE-5345 > URL: https://issues.apache.org/jira/browse/HBASE-5345 > Project: HBase > Issue Type: Bug >Affects Versions: 0.92.0 >Reporter: Evert Arckens >Assignee: Evert Arckens > Fix For: 0.94.0, 0.92.1 > > Attachments: 5345-v2.txt, 5345.txt, > checkAndMutateEmpty-HBASE-5345.patch > > > When a value contains an empty byte[] and then a checkAndPut is performed > with an empty byte[] , the operation will fail. > For example: > Put put = new Put(row1); > put.add(fam1, qf1, new byte[0]); > table.put(put); > put = new Put(row1); > put.add(fam1, qf1, val1); > table.checkAndPut(row1, fam1, qf1, new byte[0], put); ---> false > I think this is related to HBASE-3793 and HBASE-3468. > Note that you will also get into this situation when first putting a null > value ( put.add(fam1,qf1,null) ), as this value will then be regarded and > returned as an empty byte[] upon a get. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5432) Hunk missed applying 'hbase-5255 Use singletons for OperationStatus to save memory'
[ https://issues.apache.org/jira/browse/HBASE-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212150#comment-13212150 ] Hudson commented on HBASE-5432: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5432 Hunk missed applying 'hbase-5255 Use singletons for OperationStatus to save memory' (Revision 1290862) Result = FAILURE stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java > Hunk missed applying 'hbase-5255 Use singletons for OperationStatus to save > memory' > --- > > Key: HBASE-5432 > URL: https://issues.apache.org/jira/browse/HBASE-5432 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack > Fix For: 0.92.1 > > Attachments: 5432.txt > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5327) Print a message when an invalid hbase.rootdir is passed
[
https://issues.apache.org/jira/browse/HBASE-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212152#comment-13212152
]
Hudson commented on HBASE-5327:
---
Integrated in HBase-0.92-security #91 (See
[https://builds.apache.org/job/HBase-0.92-security/91/])
HBASE-5327 Print a message when an invalid hbase.rootdir is passed (Jimmy
Xiang) (Revision 1243648)
Result = FAILURE
tedyu :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/MasterFileSystem.java
> Print a message when an invalid hbase.rootdir is passed
> ---
>
> Key: HBASE-5327
> URL: https://issues.apache.org/jira/browse/HBASE-5327
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.90.5
>Reporter: Jean-Daniel Cryans
>Assignee: Jimmy Xiang
> Fix For: 0.94.0, 0.90.6, 0.92.1
>
> Attachments: hbase-5327.txt, hbase-5327_v2.txt
>
>
> As seen on the mailing list:
> http://comments.gmane.org/gmane.comp.java.hadoop.hbase.user/24124
> If hbase.rootdir doesn't specify a folder on hdfs we crash while opening a
> path to .oldlogs:
> {noformat}
> 2012-02-02 23:07:26,292 FATAL org.apache.hadoop.hbase.master.HMaster:
> Unhandled exception. Starting shutdown.
> java.lang.IllegalArgumentException: java.net.URISyntaxException: Relative
> path in absolute URI: hdfs://sv4r11s38:9100.oldlogs
> at org.apache.hadoop.fs.Path.initialize(Path.java:148)
> at org.apache.hadoop.fs.Path.(Path.java:71)
> at org.apache.hadoop.fs.Path.(Path.java:50)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.(MasterFileSystem.java:112)
> at
> org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:448)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:326)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.net.URISyntaxException: Relative path in absolute URI:
> hdfs://sv4r11s38:9100.oldlogs
> at java.net.URI.checkPath(URI.java:1787)
> at java.net.URI.(URI.java:735)
> at org.apache.hadoop.fs.Path.initialize(Path.java:145)
> ... 6 more
> {noformat}
> It could also crash anywhere else, this just happens to be the first place we
> use hbase.rootdir. We need to verify that it's an actual folder.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5267) Add a configuration to disable the slab cache by default
[
https://issues.apache.org/jira/browse/HBASE-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212157#comment-13212157
]
Hudson commented on HBASE-5267:
---
Integrated in HBase-0.92-security #91 (See
[https://builds.apache.org/job/HBase-0.92-security/91/])
HBASE-5267 Add a configuration to disable the slab cache by default (Li
Pi) (Revision 1241643)
Result = FAILURE
tedyu :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/conf/hbase-env.sh
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheConfig.java
* /hbase/branches/0.92/src/main/resources/hbase-default.xml
> Add a configuration to disable the slab cache by default
>
>
> Key: HBASE-5267
> URL: https://issues.apache.org/jira/browse/HBASE-5267
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.92.0
>Reporter: Jean-Daniel Cryans
>Assignee: Li Pi
>Priority: Blocker
> Fix For: 0.94.0, 0.92.1
>
> Attachments: 5267.txt, 5267v2.txt, 5267v3.txt, 5267v4.txt
>
>
> From what I commented at the tail of HBASE-4027:
> {quote}
> I changed the release note, the patch doesn't have a "hbase.offheapcachesize"
> configuration and it's enabled as soon as you set -XX:MaxDirectMemorySize
> (which is actually a big problem when you consider this:
> http://hbase.apache.org/book.html#trouble.client.oome.directmemory.leak).
> {quote}
> We need to add hbase.offheapcachesize and set it to false by default.
> Marking as a blocker for 0.92.1 and assigning to Li Pi at Todd's request.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5421) use hadoop-client/hadoop-minicluster artifacts for Hadoop 0.23 build
[ https://issues.apache.org/jira/browse/HBASE-5421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212153#comment-13212153 ] Hudson commented on HBASE-5421: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5421 use hadoop-client/hadoop-minicluster artifacts for Hadoop 0.23 build (Revision 1245742) Result = FAILURE stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/pom.xml > use hadoop-client/hadoop-minicluster artifacts for Hadoop 0.23 build > > > Key: HBASE-5421 > URL: https://issues.apache.org/jira/browse/HBASE-5421 > Project: HBase > Issue Type: Improvement > Components: build >Affects Versions: 0.92.0 >Reporter: Shaneal Manek >Assignee: Shaneal Manek >Priority: Minor > Labels: build > Fix For: 0.94.0, 0.92.1 > > Attachments: hbase-5421.patch > > > Hadoop recently added hadoop-client and hadoop-minicluster artifacts for > Hadoop 0.23+ that don't export all the internal dependencies (HADOOP-8009). > Let's use them instead of manually specifying transitive dependency exclusion > lists (which is error prone and annoying). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5317) Fix TestHFileOutputFormat to work against hadoop 0.23
[ https://issues.apache.org/jira/browse/HBASE-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212154#comment-13212154 ] Hudson commented on HBASE-5317: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5317 Fix testColumnFamilyCompression and test_TIMERANGE in TestHFileOutputFormat (Revision 1245724) Result = FAILURE stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/mapreduce/TestHFileOutputFormat.java > Fix TestHFileOutputFormat to work against hadoop 0.23 > - > > Key: HBASE-5317 > URL: https://issues.apache.org/jira/browse/HBASE-5317 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 0.94.0, 0.92.0 >Reporter: Gregory Chanan >Assignee: Gregory Chanan > Attachments: HBASE-5317-v0.patch, HBASE-5317-v1.patch, > HBASE-5317-v3.patch > > > Running > mvn -Dhadoop.profile=23 test -P localTests > -Dtest=org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat > yields this on 0.92: > Failed tests: > testColumnFamilyCompression(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat): > HFile for column family info-A not found > Tests in error: > test_TIMERANGE(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat): > /home/gchanan/workspace/apache92/target/test-data/276cbd0c-c771-4f81-9ba8-c464c9dd7486/test_TIMERANGE_present/_temporary/0/_temporary/_attempt_200707121733_0001_m_00_0 > (Is a directory) > > testMRIncrementalLoad(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat): > TestTable > > testMRIncrementalLoadWithSplit(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat): > TestTable > It looks like on trunk, this also results in an error: > > testExcludeMinorCompaction(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat): > TestTable > I have a patch that fixes testColumnFamilyCompression and test_TIMERANGE, but > haven't fixed the other 3 yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5425) Punt on the timeout doesn't work in BulkEnabler#waitUntilDone (master's EnableTableHandler)
[
https://issues.apache.org/jira/browse/HBASE-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212155#comment-13212155
]
Hudson commented on HBASE-5425:
---
Integrated in HBase-0.92-security #91 (See
[https://builds.apache.org/job/HBase-0.92-security/91/])
HBASE-5425 Punt on the timeout doesn't work in BulkEnabler#waitUntilDone
(master's EnableTableHandler) (Revision 1245676)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/handler/EnableTableHandler.java
> Punt on the timeout doesn't work in BulkEnabler#waitUntilDone (master's
> EnableTableHandler)
>
>
> Key: HBASE-5425
> URL: https://issues.apache.org/jira/browse/HBASE-5425
> Project: HBase
> Issue Type: Bug
> Components: master
>Affects Versions: 0.90.5, 0.92.0
>Reporter: terry zhang
> Fix For: 0.94.0
>
> Attachments: HBASE-5425.patch
>
>
> please take a look at the code below in EnableTableHandler(hbase master):
> {code:title=EnableTableHandler.java|borderStyle=solid}
> protected boolean waitUntilDone(long timeout)
> throws InterruptedException {
>
> .
> int lastNumberOfRegions = this.countOfRegionsInTable;
> while (!server.isStopped() && remaining > 0) {
> Thread.sleep(waitingTimeForEvents);
> regions = assignmentManager.getRegionsOfTable(tableName);
> if (isDone(regions)) break;
> // Punt on the timeout as long we make progress
> if (regions.size() > lastNumberOfRegions) {
> lastNumberOfRegions = regions.size();
> timeout += waitingTimeForEvents;
> }
> remaining = timeout - (System.currentTimeMillis() - startTime);
>
> }
> private boolean isDone(final List regions) {
> return regions != null && regions.size() >= this.countOfRegionsInTable;
> }
> {code}
> We can easily find out if we let lastNumberOfRegions =
> this.countOfRegionsInTable , the function of punt on timeout code will never
> be executed. I think initlize lastNumberOfRegions = 0 can make it work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5420) TestImportTsv does not shut down MR Cluster correctly (fails against 0.23 hadoop)
[ https://issues.apache.org/jira/browse/HBASE-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212149#comment-13212149 ] Hudson commented on HBASE-5420: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5420 TestImportTsv does not shut down MR Cluster correctly (fails against 0.23 hadoop) (Revision 1245796) Result = FAILURE stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java > TestImportTsv does not shut down MR Cluster correctly (fails against 0.23 > hadoop) > - > > Key: HBASE-5420 > URL: https://issues.apache.org/jira/browse/HBASE-5420 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 0.94.0, 0.92.0 >Reporter: Gregory Chanan >Assignee: Gregory Chanan > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-5420-v1.patch, HBASE-5420.patch > > > Test calls startMiniMapReduceCluster() but never calls > shutdownMiniMapReduceCluster(). > This causes failures with -Dhadoop.profile=23 when both testMROnTable and > testMROnTableWithCustomMapper are run, because the cluster cannot start up > properly for the second test. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5003) If the master is started with a wrong root dir, it gets stuck and can't be killed
[
https://issues.apache.org/jira/browse/HBASE-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212144#comment-13212144
]
Hudson commented on HBASE-5003:
---
Integrated in HBase-0.92-security #91 (See
[https://builds.apache.org/job/HBase-0.92-security/91/])
HBASE-5003 If the master is started with a wrong root dir, it gets stuck
and can't be killed (Revision 1290884)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/HConstants.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/MasterFileSystem.java
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
* /hbase/branches/0.92/src/main/resources/hbase-default.xml
> If the master is started with a wrong root dir, it gets stuck and can't be
> killed
> -
>
> Key: HBASE-5003
> URL: https://issues.apache.org/jira/browse/HBASE-5003
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.90.4
>Reporter: Jean-Daniel Cryans
>Assignee: Shaneal Manek
>Priority: Critical
> Labels: noob
> Fix For: 0.94.0, 0.92.1
>
> Attachments: hbase-5003-v2.patch, hbase-5003.patch
>
>
> Reported by a new user on IRC who tried to set hbase.rootdir to
> file:///~/hbase, the master gets stuck and cannot be killed. I tried
> something similar on my machine and it spins while logging:
> {quote}
> 2011-12-09 16:11:17,002 WARN org.apache.hadoop.hbase.util.FSUtils: Unable to
> create version file at file:/bin/hbase, retrying: Mkdirs failed to create
> file:/bin/hbase
> 2011-12-09 16:11:27,002 WARN org.apache.hadoop.hbase.util.FSUtils: Unable to
> create version file at file:/bin/hbase, retrying: Mkdirs failed to create
> file:/bin/hbase
> 2011-12-09 16:11:37,003 WARN org.apache.hadoop.hbase.util.FSUtils: Unable to
> create version file at file:/bin/hbase, retrying: Mkdirs failed to create
> file:/bin/hbase
> {quote}
> The reason it cannot be stopped is that the master's main thread is stuck in
> there and will never be notified:
> {quote}
> "Master:0;su-jdcryans-01.local,51116,1323475535684" prio=5 tid=7f92b7a3c000
> nid=0x1137ba000 waiting on condition [1137b9000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at org.apache.hadoop.hbase.util.FSUtils.setVersion(FSUtils.java:297)
> at org.apache.hadoop.hbase.util.FSUtils.setVersion(FSUtils.java:268)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.checkRootDir(MasterFileSystem.java:339)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.createInitialFileSystemLayout(MasterFileSystem.java:128)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.(MasterFileSystem.java:113)
> at
> org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:435)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:314)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster.run(HMasterCommandLine.java:218)
> at java.lang.Thread.run(Thread.java:680)
> {quote}
> It seems we should do a better handling of the exceptions we get in there,
> and die if we need to. It would make a better user experience.
> Maybe also do a check on hbase.rootdir before even starting the master.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5427) Upgrade our zk to 3.4.3
[ https://issues.apache.org/jira/browse/HBASE-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212145#comment-13212145 ] Hudson commented on HBASE-5427: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5427 Upgrade our zk to 3.4.3 (Revision 1245760) Result = FAILURE stack : Files : * /hbase/branches/0.92/pom.xml > Upgrade our zk to 3.4.3 > --- > > Key: HBASE-5427 > URL: https://issues.apache.org/jira/browse/HBASE-5427 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack > Fix For: 0.94.0, 0.92.1 > > Attachments: 5427.txt > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5395) CopyTable needs to use GenericOptionsParser
[ https://issues.apache.org/jira/browse/HBASE-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212146#comment-13212146 ] Hudson commented on HBASE-5395: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5395 CopyTable needs to use GenericOptionsParser (Revision 1243758) Result = FAILURE jdcryans : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/mapreduce/CopyTable.java > CopyTable needs to use GenericOptionsParser > --- > > Key: HBASE-5395 > URL: https://issues.apache.org/jira/browse/HBASE-5395 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.90.5 >Reporter: Jean-Daniel Cryans >Assignee: Jean-Daniel Cryans > Fix For: 0.94.0, 0.90.6, 0.92.1 > > Attachments: HBASE-5395.patch > > > CopyTable needs to use GenericOptionsParser so that we can pass other options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5363) Automatically run rat check on mvn release builds
[ https://issues.apache.org/jira/browse/HBASE-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212147#comment-13212147 ] Hudson commented on HBASE-5363: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5363 Automatically run rat check on mvn release builds (Revision 1243163) Result = FAILURE stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/pom.xml > Automatically run rat check on mvn release builds > - > > Key: HBASE-5363 > URL: https://issues.apache.org/jira/browse/HBASE-5363 > Project: HBase > Issue Type: Improvement > Components: build >Affects Versions: 0.90.5, 0.92.0 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > Fix For: 0.94.0, 0.90.6, 0.92.1 > > Attachments: hbase-5363-0.90.patch, hbase-5363.2.patch, > hbase-5363.patch > > > Some of the recent hbase release failed rat checks (mvn rat:check). We > should add checks likely in the mvn package phase so that this becomes a > non-issue in the future. > Here's an example from Whirr: > https://github.com/apache/whirr/blob/trunk/pom.xml line 388 for an example. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5393) Consider splitting after flushing
[ https://issues.apache.org/jira/browse/HBASE-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212143#comment-13212143 ] Hudson commented on HBASE-5393: --- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5393 Consider splitting after flushing (Revision 1245726) Result = FAILURE jdcryans : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreFlusher.java > Consider splitting after flushing > - > > Key: HBASE-5393 > URL: https://issues.apache.org/jira/browse/HBASE-5393 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.90.5 >Reporter: Jean-Daniel Cryans >Assignee: Jean-Daniel Cryans > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-2375-flush-split.patch > > > Spawning this from HBASE-2375, I saw that it was much more efficient > compaction-wise to check if we can split right after flushing. Much like the > ideas that Jon spelled out in the description of that jira, the window is > smaller because you don't have to compact and then split right away to only > compact again when the daughters open. > Another thing it improves is while we're normally waiting for the compaction > to happen, data that's still coming in will make us go way past the > MAX_FILESIZE to a point where for the first region I was seeing a store size > 3-4x bigger before it was able to split. > I targeted this for 0.94, but I'd like to get this into 0.92.1 or .2 too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5431) Improve delete marker handling in Import M/R jobs
[ https://issues.apache.org/jira/browse/HBASE-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211681#comment-13211681 ] Hudson commented on HBASE-5431: --- Integrated in HBase-TRUNK-security #117 (See [https://builds.apache.org/job/HBase-TRUNK-security/117/]) HBASE-5431 Improve delete marker handling in Import M/R jobs (Revision 1290955) Result = FAILURE larsh : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/Delete.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/mapreduce/Import.java > Improve delete marker handling in Import M/R jobs > - > > Key: HBASE-5431 > URL: https://issues.apache.org/jira/browse/HBASE-5431 > Project: HBase > Issue Type: Sub-task > Components: mapreduce >Affects Versions: 0.94.0 >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl >Priority: Minor > Fix For: 0.94.0 > > Attachments: 5431.txt > > > Import currently create a new Delete object for each delete KV found in a > result object. > This can be improved with the new Delete API that allows adding a delete KV > to a Delete object. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5003) If the master is started with a wrong root dir, it gets stuck and can't be killed
[
https://issues.apache.org/jira/browse/HBASE-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211213#comment-13211213
]
Hudson commented on HBASE-5003:
---
Integrated in HBase-TRUNK-security #116 (See
[https://builds.apache.org/job/HBase-TRUNK-security/116/])
HBASE-5003 If the master is started with a wrong root dir, it gets stuck
and can't be killed (Revision 1290882)
Result = FAILURE
stack :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/HConstants.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/MasterFileSystem.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
* /hbase/trunk/src/main/resources/hbase-default.xml
> If the master is started with a wrong root dir, it gets stuck and can't be
> killed
> -
>
> Key: HBASE-5003
> URL: https://issues.apache.org/jira/browse/HBASE-5003
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.90.4
>Reporter: Jean-Daniel Cryans
>Assignee: Shaneal Manek
>Priority: Critical
> Labels: noob
> Fix For: 0.94.0, 0.92.1
>
> Attachments: hbase-5003-v2.patch, hbase-5003.patch
>
>
> Reported by a new user on IRC who tried to set hbase.rootdir to
> file:///~/hbase, the master gets stuck and cannot be killed. I tried
> something similar on my machine and it spins while logging:
> {quote}
> 2011-12-09 16:11:17,002 WARN org.apache.hadoop.hbase.util.FSUtils: Unable to
> create version file at file:/bin/hbase, retrying: Mkdirs failed to create
> file:/bin/hbase
> 2011-12-09 16:11:27,002 WARN org.apache.hadoop.hbase.util.FSUtils: Unable to
> create version file at file:/bin/hbase, retrying: Mkdirs failed to create
> file:/bin/hbase
> 2011-12-09 16:11:37,003 WARN org.apache.hadoop.hbase.util.FSUtils: Unable to
> create version file at file:/bin/hbase, retrying: Mkdirs failed to create
> file:/bin/hbase
> {quote}
> The reason it cannot be stopped is that the master's main thread is stuck in
> there and will never be notified:
> {quote}
> "Master:0;su-jdcryans-01.local,51116,1323475535684" prio=5 tid=7f92b7a3c000
> nid=0x1137ba000 waiting on condition [1137b9000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at org.apache.hadoop.hbase.util.FSUtils.setVersion(FSUtils.java:297)
> at org.apache.hadoop.hbase.util.FSUtils.setVersion(FSUtils.java:268)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.checkRootDir(MasterFileSystem.java:339)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.createInitialFileSystemLayout(MasterFileSystem.java:128)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.(MasterFileSystem.java:113)
> at
> org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:435)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:314)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster.run(HMasterCommandLine.java:218)
> at java.lang.Thread.run(Thread.java:680)
> {quote}
> It seems we should do a better handling of the exceptions we get in there,
> and die if we need to. It would make a better user experience.
> Maybe also do a check on hbase.rootdir before even starting the master.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5209) HConnection/HMasterInterface should allow for way to get hostname of currently active master in multi-master HBase setup
[ https://issues.apache.org/jira/browse/HBASE-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211214#comment-13211214 ] Hudson commented on HBASE-5209: --- Integrated in HBase-TRUNK-security #116 (See [https://builds.apache.org/job/HBase-TRUNK-security/116/]) HBASE-5209 HConnection/HMasterInterface should allow for way to get hostname of currently active master in multi-master HBase setup (Revision 1290942) Result = FAILURE stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/ClusterStatus.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/ActiveMasterManager.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/zookeeper/ZKUtil.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperWatcher.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/master/TestActiveMasterManager.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/master/TestMasterFailover.java > HConnection/HMasterInterface should allow for way to get hostname of > currently active master in multi-master HBase setup > > > Key: HBASE-5209 > URL: https://issues.apache.org/jira/browse/HBASE-5209 > Project: HBase > Issue Type: Improvement > Components: master >Affects Versions: 0.94.0, 0.90.5, 0.92.0 >Reporter: Aditya Acharya >Assignee: David S. Wang > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE_5209_v5.diff > > > I have a multi-master HBase set up, and I'm trying to programmatically > determine which of the masters is currently active. But the API does not > allow me to do this. There is a getMaster() method in the HConnection class, > but it returns an HMasterInterface, whose methods do not allow me to find out > which master won the last race. The API should have a > getActiveMasterHostname() or something to that effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5209) HConnection/HMasterInterface should allow for way to get hostname of currently active master in multi-master HBase setup
[ https://issues.apache.org/jira/browse/HBASE-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211210#comment-13211210 ] Hudson commented on HBASE-5209: --- Integrated in HBase-0.92 #293 (See [https://builds.apache.org/job/HBase-0.92/293/]) HBASE-5209 HConnection/HMasterInterface should allow for way to get hostname of currently active master in multi-master HBase setup (Revision 1290943) Result = FAILURE stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/ClusterStatus.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/ActiveMasterManager.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/zookeeper/ZKUtil.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperWatcher.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/master/TestActiveMasterManager.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/master/TestMasterFailover.java > HConnection/HMasterInterface should allow for way to get hostname of > currently active master in multi-master HBase setup > > > Key: HBASE-5209 > URL: https://issues.apache.org/jira/browse/HBASE-5209 > Project: HBase > Issue Type: Improvement > Components: master >Affects Versions: 0.94.0, 0.90.5, 0.92.0 >Reporter: Aditya Acharya >Assignee: David S. Wang > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE_5209_v5.diff > > > I have a multi-master HBase set up, and I'm trying to programmatically > determine which of the masters is currently active. But the API does not > allow me to do this. There is a getMaster() method in the HConnection class, > but it returns an HMasterInterface, whose methods do not allow me to find out > which master won the last race. The API should have a > getActiveMasterHostname() or something to that effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5003) If the master is started with a wrong root dir, it gets stuck and can't be killed
[
https://issues.apache.org/jira/browse/HBASE-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211181#comment-13211181
]
Hudson commented on HBASE-5003:
---
Integrated in HBase-0.92 #292 (See
[https://builds.apache.org/job/HBase-0.92/292/])
HBASE-5003 If the master is started with a wrong root dir, it gets stuck
and can't be killed (Revision 1290884)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/HConstants.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/MasterFileSystem.java
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
* /hbase/branches/0.92/src/main/resources/hbase-default.xml
> If the master is started with a wrong root dir, it gets stuck and can't be
> killed
> -
>
> Key: HBASE-5003
> URL: https://issues.apache.org/jira/browse/HBASE-5003
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.90.4
>Reporter: Jean-Daniel Cryans
>Assignee: Shaneal Manek
>Priority: Critical
> Labels: noob
> Fix For: 0.94.0, 0.92.1
>
> Attachments: hbase-5003-v2.patch, hbase-5003.patch
>
>
> Reported by a new user on IRC who tried to set hbase.rootdir to
> file:///~/hbase, the master gets stuck and cannot be killed. I tried
> something similar on my machine and it spins while logging:
> {quote}
> 2011-12-09 16:11:17,002 WARN org.apache.hadoop.hbase.util.FSUtils: Unable to
> create version file at file:/bin/hbase, retrying: Mkdirs failed to create
> file:/bin/hbase
> 2011-12-09 16:11:27,002 WARN org.apache.hadoop.hbase.util.FSUtils: Unable to
> create version file at file:/bin/hbase, retrying: Mkdirs failed to create
> file:/bin/hbase
> 2011-12-09 16:11:37,003 WARN org.apache.hadoop.hbase.util.FSUtils: Unable to
> create version file at file:/bin/hbase, retrying: Mkdirs failed to create
> file:/bin/hbase
> {quote}
> The reason it cannot be stopped is that the master's main thread is stuck in
> there and will never be notified:
> {quote}
> "Master:0;su-jdcryans-01.local,51116,1323475535684" prio=5 tid=7f92b7a3c000
> nid=0x1137ba000 waiting on condition [1137b9000]
>java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at org.apache.hadoop.hbase.util.FSUtils.setVersion(FSUtils.java:297)
> at org.apache.hadoop.hbase.util.FSUtils.setVersion(FSUtils.java:268)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.checkRootDir(MasterFileSystem.java:339)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.createInitialFileSystemLayout(MasterFileSystem.java:128)
> at
> org.apache.hadoop.hbase.master.MasterFileSystem.(MasterFileSystem.java:113)
> at
> org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:435)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:314)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster.run(HMasterCommandLine.java:218)
> at java.lang.Thread.run(Thread.java:680)
> {quote}
> It seems we should do a better handling of the exceptions we get in there,
> and die if we need to. It would make a better user experience.
> Maybe also do a check on hbase.rootdir before even starting the master.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5255) Use singletons for OperationStatus to save memory
[
https://issues.apache.org/jira/browse/HBASE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211159#comment-13211159
]
Hudson commented on HBASE-5255:
---
Integrated in HBase-0.92 #291 (See
[https://builds.apache.org/job/HBase-0.92/291/])
HBASE-5432 Hunk missed applying 'hbase-5255 Use singletons for
OperationStatus to save memory' (Revision 1290862)
Result = SUCCESS
> Use singletons for OperationStatus to save memory
> -
>
> Key: HBASE-5255
> URL: https://issues.apache.org/jira/browse/HBASE-5255
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
>Affects Versions: 0.90.5, 0.92.0
>Reporter: Benoit Sigoure
>Assignee: Benoit Sigoure
>Priority: Minor
> Labels: performance
> Fix For: 0.94.0, 0.92.1
>
> Attachments: 5255-92.txt, 5255-v2.txt,
> HBASE-5255-0.92-Use-singletons-to-remove-unnecessary-memory-allocati.patch,
> HBASE-5255-trunk-Use-singletons-to-remove-unnecessary-memory-allocati.patch
>
>
> Every single {{Put}} causes the allocation of at least one
> {{OperationStatus}}, yet {{OperationStatus}} is almost always stateless, so
> these allocations are unnecessary and could be avoided. Attached patch adds
> a few singletons and uses them, with no public API change. I didn't test the
> patches, but you get the idea.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5200) AM.ProcessRegionInTransition() and AM.handleRegion() race thus leaving the region assignment inconsistent
[
https://issues.apache.org/jira/browse/HBASE-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211160#comment-13211160
]
Hudson commented on HBASE-5200:
---
Integrated in HBase-0.92 #291 (See
[https://builds.apache.org/job/HBase-0.92/291/])
HBASE-5200 AM.ProcessRegionInTransition() and AM.handleRegion() race thus
leaving the region assignment inconsistent (Revision 1290855)
Result = SUCCESS
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
> AM.ProcessRegionInTransition() and AM.handleRegion() race thus leaving the
> region assignment inconsistent
> -
>
> Key: HBASE-5200
> URL: https://issues.apache.org/jira/browse/HBASE-5200
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.90.5
>Reporter: ramkrishna.s.vasudevan
>Assignee: ramkrishna.s.vasudevan
> Fix For: 0.94.0, 0.92.1
>
> Attachments: 5200-test.txt, 5200-v2.txt, 5200-v3.txt,
> 5200-v4-092.txt, 5200-v4.txt, 5200-v4no-prefix.txt, HBASE-5200.patch,
> HBASE-5200_1.patch, HBASE-5200_trunk_latest_with_test_2.patch,
> TEST-org.apache.hadoop.hbase.master.TestRestartCluster.xml,
> hbase-5200_90_latest.patch, hbase-5200_90_latest_new.patch
>
>
> This is the scenario
> Consider a case where the balancer is going on thus trying to close regions
> in a RS.
> Before we could close a master switch happens.
> On Master switch the set of nodes that are in RIT is collected and we first
> get Data and start watching the node
> After that the node data is added into RIT.
> Now by this time (before adding to RIT) if the RS to which close was called
> does a transition in AM.handleRegion() we miss the handling saying RIT state
> was null.
> {code}
> 2012-01-13 10:50:46,358 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> a66d281d231dfcaea97c270698b26b6f from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,358 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> c12e53bfd48ddc5eec507d66821c4d23 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,358 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> 59ae13de8c1eb325a0dd51f4902d2052 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> f45bc9614d7575f35244849af85aa078 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> cc3ecd7054fe6cd4a1159ed92fd62641 from server
> HOST-192-168-47-204,20020,1326342744518 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> 3af40478a17fee96b4a192b22c90d5a2 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> e6096a8466e730463e10d3d61f809b92 from server
> HOST-192-168-47-204,20020,1326342744518 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> 4806781a1a23066f7baed22b4d237e24 from server
> HOST-192-168-47-204,20020,1326342744518 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> d69e104131accaefe21dcc01fddc7629 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> {code}
> In branch the CLOSING node is created by RS thus leading to more
> inconsistency.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://w
[jira] [Commented] (HBASE-5432) Hunk missed applying 'hbase-5255 Use singletons for OperationStatus to save memory'
[ https://issues.apache.org/jira/browse/HBASE-5432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211161#comment-13211161 ] Hudson commented on HBASE-5432: --- Integrated in HBase-0.92 #291 (See [https://builds.apache.org/job/HBase-0.92/291/]) HBASE-5432 Hunk missed applying 'hbase-5255 Use singletons for OperationStatus to save memory' (Revision 1290862) Result = SUCCESS stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java > Hunk missed applying 'hbase-5255 Use singletons for OperationStatus to save > memory' > --- > > Key: HBASE-5432 > URL: https://issues.apache.org/jira/browse/HBASE-5432 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack > Fix For: 0.92.1 > > Attachments: 5432.txt > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5195) [Coprocessors] preGet hook does not allow overriding or wrapping filter on incoming Get
[ https://issues.apache.org/jira/browse/HBASE-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211142#comment-13211142 ] Hudson commented on HBASE-5195: --- Integrated in HBase-TRUNK #2665 (See [https://builds.apache.org/job/HBase-TRUNK/2665/]) HBASE-5195 [Coprocessors] preGet hook does not allow overriding or wrapping filter on incoming Get -- SECOND HALF OF THIS COMMIT (Revision 1245773) Result = FAILURE stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java > [Coprocessors] preGet hook does not allow overriding or wrapping filter on > incoming Get > --- > > Key: HBASE-5195 > URL: https://issues.apache.org/jira/browse/HBASE-5195 > Project: HBase > Issue Type: Bug >Affects Versions: 0.94.0, 0.92.0 >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-5195.patch > > > Without the ability to wrap the internal Scan on the Get, we can't override > (or protect, in the case of access control) Gets as we can Scans. The result > is inconsistent behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4640) Catch ClosedChannelException and document it
[ https://issues.apache.org/jira/browse/HBASE-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211134#comment-13211134 ] Hudson commented on HBASE-4640: --- Integrated in HBase-TRUNK #2665 (See [https://builds.apache.org/job/HBase-TRUNK/2665/]) HBASE-4640 Catch ClosedChannelException and document it (Revision 1245730) Result = FAILURE jdcryans : Files : * /hbase/trunk/src/docbkx/troubleshooting.xml * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/ipc/HBaseServer.java > Catch ClosedChannelException and document it > > > Key: HBASE-4640 > URL: https://issues.apache.org/jira/browse/HBASE-4640 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.90.4 >Reporter: Jean-Daniel Cryans >Assignee: Jean-Daniel Cryans >Priority: Minor > Fix For: 0.94.0 > > Attachments: HBASE-4640.patch > > > ClosedChannelException is a pretty obscure exception for the non-expert and > doesn't tell you why you get it. We should instead catch it, print a WARN, > don't print a stack trace, and add a line in the book about this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5346) Fix testColumnFamilyCompression and test_TIMERANGE in TestHFileOutputFormat
[ https://issues.apache.org/jira/browse/HBASE-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211136#comment-13211136 ] Hudson commented on HBASE-5346: --- Integrated in HBase-TRUNK #2665 (See [https://builds.apache.org/job/HBase-TRUNK/2665/]) HBASE-5346 Fix testColumnFamilyCompression and test_TIMERANGE in TestHFileOutputFormat (Revision 1245280) Result = FAILURE stack : Files : * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/mapreduce/TestHFileOutputFormat.java > Fix testColumnFamilyCompression and test_TIMERANGE in TestHFileOutputFormat > > > Key: HBASE-5346 > URL: https://issues.apache.org/jira/browse/HBASE-5346 > Project: HBase > Issue Type: Sub-task > Components: mapreduce, test >Affects Versions: 0.94.0, 0.92.0 >Reporter: Gregory Chanan >Assignee: Gregory Chanan > Fix For: 0.94.0, 0.92.0 > > Attachments: HBASE-5346-v0.patch > > > Running > mvn -Dhadoop.profile=23 test -P localTests > -Dtest=org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat > yields this on 0.92 (for testColumnFamilyCompression and test_TIMERANGE): > Failed tests: > testColumnFamilyCompression(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat): > HFile for column family info-A not found > Tests in error: > test_TIMERANGE(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat): > /home/gchanan/workspace/apache92/target/test-data/276cbd0c-c771-4f81-9ba8-c464c9dd7486/test_TIMERANGE_present/_temporary/0/_temporary/_attempt_200707121733_0001_m_00_0 > (Is a directory) > The problem is that these tests make incorrect assumptions about the output > of mapreduce jobs. Prior to 0.23, temporary data was in, for example: > ./_temporary/_attempt___r_00_0/b/1979617994050536795 > Now that has changed. The correct way to get that path is based on > getDefaultWorkFile. > Also, the data is not moved into the outputPath until both the Task and Job > are committed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-3584) Allow atomic put/delete in one call
[ https://issues.apache.org/jira/browse/HBASE-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211141#comment-13211141 ] Hudson commented on HBASE-3584: --- Integrated in HBase-TRUNK #2665 (See [https://builds.apache.org/job/HBase-TRUNK/2665/]) HBASE-3584 Addendum, remove RowMutation (Revision 1245876) HBASE-3584 Rename RowMutation to RowMutations (Revision 1245792) Result = FAILURE larsh : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/RowMutation.java stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/HTable.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/HTableInterface.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/RowMutation.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/RowMutations.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/coprocessor/CoprocessorHost.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/io/HbaseObjectWritable.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/ipc/HRegionInterface.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/coprocessor/TestRegionObserverInterface.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestAtomicOperation.java > Allow atomic put/delete in one call > --- > > Key: HBASE-3584 > URL: https://issues.apache.org/jira/browse/HBASE-3584 > Project: HBase > Issue Type: New Feature > Components: client, coprocessors, regionserver >Reporter: ryan rawson >Assignee: Lars Hofhansl > Fix For: 0.94.0 > > Attachments: 3584-final.txt, 3584-v1.txt, 3584-v3.txt > > > Right now we have the following calls: > put(Put) > delete(Delete) > increment(Increments) > But we cannot combine all of the above in a single call, complete with a > single row lock. It would be nice to do that. > It would also allow us to do a CAS where we could do a put/increment if the > check succeeded. > - > Amendment: > Since Increment does not currently support MVCC it cannot be included in an > atomic operation. > So this for Put and Delete only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5120) Timeout monitor races with table disable handler
[
https://issues.apache.org/jira/browse/HBASE-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211138#comment-13211138
]
Hudson commented on HBASE-5120:
---
Integrated in HBase-TRUNK #2665 (See
[https://builds.apache.org/job/HBase-TRUNK/2665/])
HBASE-5120 Timeout monitor races with table disable handler (Revision
1245731)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
> Timeout monitor races with table disable handler
>
>
> Key: HBASE-5120
> URL: https://issues.apache.org/jira/browse/HBASE-5120
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.92.0
>Reporter: Zhihong Yu
>Assignee: ramkrishna.s.vasudevan
>Priority: Blocker
> Fix For: 0.94.0
>
> Attachments: HBASE-5120.patch, HBASE-5120_1.patch,
> HBASE-5120_2.patch, HBASE-5120_3.patch, HBASE-5120_4.patch,
> HBASE-5120_5.patch, HBASE-5120_5.patch
>
>
> Here is what J-D described here:
> https://issues.apache.org/jira/browse/HBASE-5119?focusedCommentId=13179176&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13179176
> I think I will retract from my statement that it "used to be extremely racy
> and caused more troubles than it fixed", on my first test I got a stuck
> region in transition instead of being able to recover. The timeout was set to
> 2 minutes to be sure I hit it.
> First the region gets closed
> {quote}
> 2012-01-04 00:16:25,811 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Sent CLOSE to
> sv4r5s38,62023,1325635980913 for region
> test1,089cd0c9,1325635015491.1a4b111bcc228043e89f59c4c3f6a791.
> {quote}
> 2 minutes later it times out:
> {quote}
> 2012-01-04 00:18:30,026 INFO
> org.apache.hadoop.hbase.master.AssignmentManager: Regions in transition timed
> out: test1,089cd0c9,1325635015491.1a4b111bcc228043e89f59c4c3f6a791.
> state=PENDING_CLOSE, ts=1325636185810, server=null
> 2012-01-04 00:18:30,026 INFO
> org.apache.hadoop.hbase.master.AssignmentManager: Region has been
> PENDING_CLOSE for too long, running forced unassign again on
> region=test1,089cd0c9,1325635015491.1a4b111bcc228043e89f59c4c3f6a791.
> 2012-01-04 00:18:30,027 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Starting unassignment of
> region test1,089cd0c9,1325635015491.1a4b111bcc228043e89f59c4c3f6a791.
> (offlining)
> {quote}
> 100ms later the master finally gets the event:
> {quote}
> 2012-01-04 00:18:30,129 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Handling
> transition=RS_ZK_REGION_CLOSED, server=sv4r5s38,62023,1325635980913,
> region=1a4b111bcc228043e89f59c4c3f6a791, which is more than 15 seconds late
> 2012-01-04 00:18:30,129 DEBUG
> org.apache.hadoop.hbase.master.handler.ClosedRegionHandler: Handling CLOSED
> event for 1a4b111bcc228043e89f59c4c3f6a791
> 2012-01-04 00:18:30,129 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Table being disabled so
> deleting ZK node and removing from regions in transition, skipping assignment
> of region test1,089cd0c9,1325635015491.1a4b111bcc228043e89f59c4c3f6a791.
> 2012-01-04 00:18:30,129 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign:
> master:62003-0x134589d3db03587 Deleting existing unassigned node for
> 1a4b111bcc228043e89f59c4c3f6a791 that is in expected state RS_ZK_REGION_CLOSED
> 2012-01-04 00:18:30,166 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign:
> master:62003-0x134589d3db03587 Successfully deleted unassigned node for
> region 1a4b111bcc228043e89f59c4c3f6a791 in expected state RS_ZK_REGION_CLOSED
> {quote}
> At this point everything is fine, the region was processed as closed. But
> wait, remember that line where it said it was going to force an unassign?
> {quote}
> 2012-01-04 00:18:30,322 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign:
> master:62003-0x134589d3db03587 Creating unassigned node for
> 1a4b111bcc228043e89f59c4c3f6a791 in a CLOSING state
> 2012-01-04 00:18:30,328 INFO
> org.apache.hadoop.hbase.master.AssignmentManager: Server null returned
> java.lang.NullPointerException: Passed server is null for
> 1a4b111bcc228043e89f59c4c3f6a791
> {quote}
> Now the master is confused, it recreated the RIT znode but the region doesn't
> even exist anymore. It even tries to shut it down but is blocked by NPEs. Now
> this is what's going on.
> The late ZK notification that the znode was deleted (but it got recreated
> after):
> {quote}
> 2012-01-04 00:19:33,285 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: The znode of region
> test1,089cd0c9,1325635015491.1a4b111bcc228043e89f59c4c3f6a791. has been
> deleted.
> {quote}
> Then it prints this, and much later tries to unassign it again:
> {quote}
> 2012-01-04 00:19:46,607 DEBUG
> org.apache.hadoo
[jira] [Commented] (HBASE-5200) AM.ProcessRegionInTransition() and AM.handleRegion() race thus leaving the region assignment inconsistent
[
https://issues.apache.org/jira/browse/HBASE-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211139#comment-13211139
]
Hudson commented on HBASE-5200:
---
Integrated in HBase-TRUNK #2665 (See
[https://builds.apache.org/job/HBase-TRUNK/2665/])
HBASE-5200 AM.ProcessRegionInTransition() and AM.handleRegion() race thus
leaving the region assignment inconsistent (Revision 1290854)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java
> AM.ProcessRegionInTransition() and AM.handleRegion() race thus leaving the
> region assignment inconsistent
> -
>
> Key: HBASE-5200
> URL: https://issues.apache.org/jira/browse/HBASE-5200
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.90.5
>Reporter: ramkrishna.s.vasudevan
>Assignee: ramkrishna.s.vasudevan
> Fix For: 0.94.0, 0.92.1
>
> Attachments: 5200-test.txt, 5200-v2.txt, 5200-v3.txt,
> 5200-v4-092.txt, 5200-v4.txt, 5200-v4no-prefix.txt, HBASE-5200.patch,
> HBASE-5200_1.patch, HBASE-5200_trunk_latest_with_test_2.patch,
> TEST-org.apache.hadoop.hbase.master.TestRestartCluster.xml,
> hbase-5200_90_latest.patch, hbase-5200_90_latest_new.patch
>
>
> This is the scenario
> Consider a case where the balancer is going on thus trying to close regions
> in a RS.
> Before we could close a master switch happens.
> On Master switch the set of nodes that are in RIT is collected and we first
> get Data and start watching the node
> After that the node data is added into RIT.
> Now by this time (before adding to RIT) if the RS to which close was called
> does a transition in AM.handleRegion() we miss the handling saying RIT state
> was null.
> {code}
> 2012-01-13 10:50:46,358 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> a66d281d231dfcaea97c270698b26b6f from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,358 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> c12e53bfd48ddc5eec507d66821c4d23 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,358 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> 59ae13de8c1eb325a0dd51f4902d2052 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> f45bc9614d7575f35244849af85aa078 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> cc3ecd7054fe6cd4a1159ed92fd62641 from server
> HOST-192-168-47-204,20020,1326342744518 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> 3af40478a17fee96b4a192b22c90d5a2 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> e6096a8466e730463e10d3d61f809b92 from server
> HOST-192-168-47-204,20020,1326342744518 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> 4806781a1a23066f7baed22b4d237e24 from server
> HOST-192-168-47-204,20020,1326342744518 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> d69e104131accaefe21dcc01fddc7629 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> {code}
> In branch the CLOSING node is created by RS thus leading to more
> inconsistency.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default
[jira] [Commented] (HBASE-5279) NPE in Master after upgrading to 0.92.0
[
https://issues.apache.org/jira/browse/HBASE-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211140#comment-13211140
]
Hudson commented on HBASE-5279:
---
Integrated in HBase-TRUNK #2665 (See
[https://builds.apache.org/job/HBase-TRUNK/2665/])
HBASE-5279 NPE in Master after upgrading to 0.92.0 -- REVERT OVERCOMMIT TO
HREGION (Revision 1245768)
HBASE-5279 NPE in Master after upgrading to 0.92.0 (Revision 1245767)
Result = FAILURE
stack :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
stack :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/catalog/MetaReader.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
> NPE in Master after upgrading to 0.92.0
> ---
>
> Key: HBASE-5279
> URL: https://issues.apache.org/jira/browse/HBASE-5279
> Project: HBase
> Issue Type: Bug
> Components: master
>Affects Versions: 0.92.0
>Reporter: Tobias Herbert
>Priority: Critical
> Fix For: 0.92.1
>
> Attachments: HBASE-5279-v2.patch, HBASE-5279.patch
>
>
> I have upgraded my environment from 0.90.4 to 0.92.0
> after the table migration I get the following error in the master (permanent)
> {noformat}
> 2012-01-25 18:23:48,648 FATAL master-namenode,6,1327512209588
> org.apache.hadoop.hbase.master.HMaster - Unhandled exception. Starting
> shutdown.
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.AssignmentManager.rebuildUserRegions(AssignmentManager.java:2190)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.joinCluster(AssignmentManager.java:323)
> at
> org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:501)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:326)
> at java.lang.Thread.run(Thread.java:662)
> 2012-01-25 18:23:48,650 INFO namenode,6,1327512209588
> org.apache.hadoop.hbase.master.HMaster - Aborting
> {noformat}
> I think that's because I had a hard crash in the cluster a while ago - and
> the following WARN since then
> {noformat}
> 2012-01-25 21:20:47,121 WARN namenode,6,1327513078123-CatalogJanitor
> org.apache.hadoop.hbase.master.CatalogJanitor - REGIONINFO_QUALIFIER is empty
> in keyvalues={emails,,xxx./info:server/1314336400471/Put/vlen=38,
> emails,,1314189353300.xxx./info:serverstartcode/1314336400471/Put/vlen=8}
> {noformat}
> my patch was simple to go around the NPE (as the other code around the lines)
> but I don't know if that's correct
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5397) [book] zookeeper quorum mistake
[ https://issues.apache.org/jira/browse/HBASE-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211143#comment-13211143 ] Hudson commented on HBASE-5397: --- Integrated in HBase-TRUNK #2665 (See [https://builds.apache.org/job/HBase-TRUNK/2665/]) hbase-5397. performance.xml, configuration.xml - correction to ZK config. (Revision 1245199) Result = FAILURE > [book] zookeeper quorum mistake > --- > > Key: HBASE-5397 > URL: https://issues.apache.org/jira/browse/HBASE-5397 > Project: HBase > Issue Type: Bug >Reporter: Andre Medeiros >Assignee: Doug Meil >Priority: Minor > Attachments: docbkx_hbase_5397.patch > > > In Chapter 2, section 2.5 "ZooKeeper" under "How many ZooKeepers should I > run?" there is the sentence > *There can be no quorum if the number of members is an even number.* > This is not true. In ZooKeeper, an even number of peers is supported, but it > is normally not used because an even sized ensemble requires, proportionally, > more peers to form a quorum than an odd sized ensemble requires. For example, > an ensemble with 4 peers requires 3 to form a quorum, while an ensemble with > 5 also requires 3 to form a quorum. Thus, an ensemble of 5 allows 2 peers to > fail, and thus is more fault tolerant than the ensemble of 4, which allows > only 1 down peer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5421) use hadoop-client/hadoop-minicluster artifacts for Hadoop 0.23 build
[ https://issues.apache.org/jira/browse/HBASE-5421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211135#comment-13211135 ] Hudson commented on HBASE-5421: --- Integrated in HBase-TRUNK #2665 (See [https://builds.apache.org/job/HBase-TRUNK/2665/]) HBASE-5421 use hadoop-client/hadoop-minicluster artifacts for Hadoop 0.23 build (Revision 1245743) Result = FAILURE stack : Files : * /hbase/trunk/pom.xml > use hadoop-client/hadoop-minicluster artifacts for Hadoop 0.23 build > > > Key: HBASE-5421 > URL: https://issues.apache.org/jira/browse/HBASE-5421 > Project: HBase > Issue Type: Improvement > Components: build >Affects Versions: 0.92.0 >Reporter: Shaneal Manek >Assignee: Shaneal Manek >Priority: Minor > Labels: build > Fix For: 0.94.0, 0.92.1 > > Attachments: hbase-5421.patch > > > Hadoop recently added hadoop-client and hadoop-minicluster artifacts for > Hadoop 0.23+ that don't export all the internal dependencies (HADOOP-8009). > Let's use them instead of manually specifying transitive dependency exclusion > lists (which is error prone and annoying). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5425) Punt on the timeout doesn't work in BulkEnabler#waitUntilDone (master's EnableTableHandler)
[
https://issues.apache.org/jira/browse/HBASE-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211137#comment-13211137
]
Hudson commented on HBASE-5425:
---
Integrated in HBase-TRUNK #2665 (See
[https://builds.apache.org/job/HBase-TRUNK/2665/])
HBASE-5425 Punt on the timeout doesn't work in BulkEnabler#waitUntilDone
(master's EnableTableHandler) (Revision 1245674)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/handler/EnableTableHandler.java
> Punt on the timeout doesn't work in BulkEnabler#waitUntilDone (master's
> EnableTableHandler)
>
>
> Key: HBASE-5425
> URL: https://issues.apache.org/jira/browse/HBASE-5425
> Project: HBase
> Issue Type: Bug
> Components: master
>Affects Versions: 0.90.5, 0.92.0
>Reporter: terry zhang
> Fix For: 0.94.0
>
> Attachments: HBASE-5425.patch
>
>
> please take a look at the code below in EnableTableHandler(hbase master):
> {code:title=EnableTableHandler.java|borderStyle=solid}
> protected boolean waitUntilDone(long timeout)
> throws InterruptedException {
>
> .
> int lastNumberOfRegions = this.countOfRegionsInTable;
> while (!server.isStopped() && remaining > 0) {
> Thread.sleep(waitingTimeForEvents);
> regions = assignmentManager.getRegionsOfTable(tableName);
> if (isDone(regions)) break;
> // Punt on the timeout as long we make progress
> if (regions.size() > lastNumberOfRegions) {
> lastNumberOfRegions = regions.size();
> timeout += waitingTimeForEvents;
> }
> remaining = timeout - (System.currentTimeMillis() - startTime);
>
> }
> private boolean isDone(final List regions) {
> return regions != null && regions.size() >= this.countOfRegionsInTable;
> }
> {code}
> We can easily find out if we let lastNumberOfRegions =
> this.countOfRegionsInTable , the function of punt on timeout code will never
> be executed. I think initlize lastNumberOfRegions = 0 can make it work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5294) Make sure javadoc is included in tarball bundle when we release
[ https://issues.apache.org/jira/browse/HBASE-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211132#comment-13211132 ] Hudson commented on HBASE-5294: --- Integrated in HBase-TRUNK #2665 (See [https://builds.apache.org/job/HBase-TRUNK/2665/]) HBASE-5294 Make sure javadoc is included in tarball bundle when we release (Revision 1245827) Result = FAILURE stack : Files : * /hbase/trunk/pom.xml * /hbase/trunk/src/docbkx/developer.xml > Make sure javadoc is included in tarball bundle when we release > --- > > Key: HBASE-5294 > URL: https://issues.apache.org/jira/browse/HBASE-5294 > Project: HBase > Issue Type: Task >Affects Versions: 0.92.0 >Reporter: stack >Assignee: Shaneal Manek >Priority: Critical > Fix For: 0.94.0, 0.92.1 > > Attachments: hbase-5294.patch > > > 0.92.0 doesn't have javadoc in the tarball. Fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5420) TestImportTsv does not shut down MR Cluster correctly (fails against 0.23 hadoop)
[ https://issues.apache.org/jira/browse/HBASE-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211133#comment-13211133 ] Hudson commented on HBASE-5420: --- Integrated in HBase-TRUNK #2665 (See [https://builds.apache.org/job/HBase-TRUNK/2665/]) HBASE-5420 TestImportTsv does not shut down MR Cluster correctly (fails against 0.23 hadoop) (Revision 1245795) Result = FAILURE stack : Files : * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java > TestImportTsv does not shut down MR Cluster correctly (fails against 0.23 > hadoop) > - > > Key: HBASE-5420 > URL: https://issues.apache.org/jira/browse/HBASE-5420 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 0.94.0, 0.92.0 >Reporter: Gregory Chanan >Assignee: Gregory Chanan > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-5420-v1.patch, HBASE-5420.patch > > > Test calls startMiniMapReduceCluster() but never calls > shutdownMiniMapReduceCluster(). > This causes failures with -Dhadoop.profile=23 when both testMROnTable and > testMROnTableWithCustomMapper are run, because the cluster cannot start up > properly for the second test. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5428) Allow for custom filters to be registered within the Thrift interface
[ https://issues.apache.org/jira/browse/HBASE-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211129#comment-13211129 ] Hudson commented on HBASE-5428: --- Integrated in HBase-TRUNK #2665 (See [https://builds.apache.org/job/HBase-TRUNK/2665/]) HBASE-5428 Allow for custom filters to be registered within the Thrift interface (Revision 1245774) Result = FAILURE stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/filter/ParseFilter.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServerRunner.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/filter/TestParseFilter.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/thrift/TestThriftServer.java > Allow for custom filters to be registered within the Thrift interface > - > > Key: HBASE-5428 > URL: https://issues.apache.org/jira/browse/HBASE-5428 > Project: HBase > Issue Type: Improvement > Components: thrift >Affects Versions: 0.92.0 >Reporter: Robert Roland > Labels: patch > Fix For: 0.94.0 > > Attachments: ThriftCustomFilters.patch > > > Custom filters work within the Java client API, but are not accessible within > the Thrift API. Attempting to use one will generate a "Filter Name x not > supported" > Attached patch allows a user to specify a list of custom filters that are > registered at Thrift server startup time within the HBase configuration files: > > hbase.thrift.filters > MyFilter:com.foo.Filter,OtherFilter:com.foo.OtherFilter > > Patch created off SVN r1245727 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5393) Consider splitting after flushing
[ https://issues.apache.org/jira/browse/HBASE-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211130#comment-13211130 ] Hudson commented on HBASE-5393: --- Integrated in HBase-TRUNK #2665 (See [https://builds.apache.org/job/HBase-TRUNK/2665/]) HBASE-5393 Consider splitting after flushing (Revision 1245727) Result = FAILURE jdcryans : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreFlusher.java > Consider splitting after flushing > - > > Key: HBASE-5393 > URL: https://issues.apache.org/jira/browse/HBASE-5393 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.90.5 >Reporter: Jean-Daniel Cryans >Assignee: Jean-Daniel Cryans > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-2375-flush-split.patch > > > Spawning this from HBASE-2375, I saw that it was much more efficient > compaction-wise to check if we can split right after flushing. Much like the > ideas that Jon spelled out in the description of that jira, the window is > smaller because you don't have to compact and then split right away to only > compact again when the daughters open. > Another thing it improves is while we're normally waiting for the compaction > to happen, data that's still coming in will make us go way past the > MAX_FILESIZE to a point where for the first region I was seeing a store size > 3-4x bigger before it was able to split. > I targeted this for 0.94, but I'd like to get this into 0.92.1 or .2 too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5427) Upgrade our zk to 3.4.3
[ https://issues.apache.org/jira/browse/HBASE-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211131#comment-13211131 ] Hudson commented on HBASE-5427: --- Integrated in HBase-TRUNK #2665 (See [https://builds.apache.org/job/HBase-TRUNK/2665/]) HBASE-5427 Upgrade our zk to 3.4.3 (Revision 1245759) Result = FAILURE stack : Files : * /hbase/trunk/pom.xml > Upgrade our zk to 3.4.3 > --- > > Key: HBASE-5427 > URL: https://issues.apache.org/jira/browse/HBASE-5427 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack > Fix For: 0.94.0, 0.92.1 > > Attachments: 5427.txt > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5200) AM.ProcessRegionInTransition() and AM.handleRegion() race thus leaving the region assignment inconsistent
[
https://issues.apache.org/jira/browse/HBASE-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211126#comment-13211126
]
Hudson commented on HBASE-5200:
---
Integrated in HBase-TRUNK-security #115 (See
[https://builds.apache.org/job/HBase-TRUNK-security/115/])
HBASE-5200 AM.ProcessRegionInTransition() and AM.handleRegion() race thus
leaving the region assignment inconsistent (Revision 1290854)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java
> AM.ProcessRegionInTransition() and AM.handleRegion() race thus leaving the
> region assignment inconsistent
> -
>
> Key: HBASE-5200
> URL: https://issues.apache.org/jira/browse/HBASE-5200
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.90.5
>Reporter: ramkrishna.s.vasudevan
>Assignee: ramkrishna.s.vasudevan
> Fix For: 0.94.0, 0.92.1
>
> Attachments: 5200-test.txt, 5200-v2.txt, 5200-v3.txt,
> 5200-v4-092.txt, 5200-v4.txt, 5200-v4no-prefix.txt, HBASE-5200.patch,
> HBASE-5200_1.patch, HBASE-5200_trunk_latest_with_test_2.patch,
> TEST-org.apache.hadoop.hbase.master.TestRestartCluster.xml,
> hbase-5200_90_latest.patch, hbase-5200_90_latest_new.patch
>
>
> This is the scenario
> Consider a case where the balancer is going on thus trying to close regions
> in a RS.
> Before we could close a master switch happens.
> On Master switch the set of nodes that are in RIT is collected and we first
> get Data and start watching the node
> After that the node data is added into RIT.
> Now by this time (before adding to RIT) if the RS to which close was called
> does a transition in AM.handleRegion() we miss the handling saying RIT state
> was null.
> {code}
> 2012-01-13 10:50:46,358 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> a66d281d231dfcaea97c270698b26b6f from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,358 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> c12e53bfd48ddc5eec507d66821c4d23 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,358 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> 59ae13de8c1eb325a0dd51f4902d2052 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> f45bc9614d7575f35244849af85aa078 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> cc3ecd7054fe6cd4a1159ed92fd62641 from server
> HOST-192-168-47-204,20020,1326342744518 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> 3af40478a17fee96b4a192b22c90d5a2 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> e6096a8466e730463e10d3d61f809b92 from server
> HOST-192-168-47-204,20020,1326342744518 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> 4806781a1a23066f7baed22b4d237e24 from server
> HOST-192-168-47-204,20020,1326342744518 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> 2012-01-13 10:50:46,359 WARN
> org.apache.hadoop.hbase.master.AssignmentManager: Received CLOSED for region
> d69e104131accaefe21dcc01fddc7629 from server
> HOST-192-168-47-205,20020,1326363111288 but region was in the state null and
> not in expected PENDING_CLOSE or CLOSING states
> {code}
> In branch the CLOSING node is created by RS thus leading to more
> inconsistency.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdmini
[jira] [Commented] (HBASE-3584) Allow atomic put/delete in one call
[ https://issues.apache.org/jira/browse/HBASE-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211127#comment-13211127 ] Hudson commented on HBASE-3584: --- Integrated in HBase-TRUNK-security #115 (See [https://builds.apache.org/job/HBase-TRUNK-security/115/]) HBASE-3584 Addendum, remove RowMutation (Revision 1245876) Result = FAILURE larsh : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/RowMutation.java > Allow atomic put/delete in one call > --- > > Key: HBASE-3584 > URL: https://issues.apache.org/jira/browse/HBASE-3584 > Project: HBase > Issue Type: New Feature > Components: client, coprocessors, regionserver >Reporter: ryan rawson >Assignee: Lars Hofhansl > Fix For: 0.94.0 > > Attachments: 3584-final.txt, 3584-v1.txt, 3584-v3.txt > > > Right now we have the following calls: > put(Put) > delete(Delete) > increment(Increments) > But we cannot combine all of the above in a single call, complete with a > single row lock. It would be nice to do that. > It would also allow us to do a CAS where we could do a put/increment if the > check succeeded. > - > Amendment: > Since Increment does not currently support MVCC it cannot be included in an > atomic operation. > So this for Put and Delete only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5279) NPE in Master after upgrading to 0.92.0
[
https://issues.apache.org/jira/browse/HBASE-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210824#comment-13210824
]
Hudson commented on HBASE-5279:
---
Integrated in HBase-TRUNK-security #114 (See
[https://builds.apache.org/job/HBase-TRUNK-security/114/])
HBASE-5279 NPE in Master after upgrading to 0.92.0 -- REVERT OVERCOMMIT TO
HREGION (Revision 1245768)
HBASE-5279 NPE in Master after upgrading to 0.92.0 (Revision 1245767)
Result = FAILURE
stack :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
stack :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/catalog/MetaReader.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
> NPE in Master after upgrading to 0.92.0
> ---
>
> Key: HBASE-5279
> URL: https://issues.apache.org/jira/browse/HBASE-5279
> Project: HBase
> Issue Type: Bug
> Components: master
>Affects Versions: 0.92.0
>Reporter: Tobias Herbert
>Priority: Critical
> Fix For: 0.92.1
>
> Attachments: HBASE-5279-v2.patch, HBASE-5279.patch
>
>
> I have upgraded my environment from 0.90.4 to 0.92.0
> after the table migration I get the following error in the master (permanent)
> {noformat}
> 2012-01-25 18:23:48,648 FATAL master-namenode,6,1327512209588
> org.apache.hadoop.hbase.master.HMaster - Unhandled exception. Starting
> shutdown.
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.AssignmentManager.rebuildUserRegions(AssignmentManager.java:2190)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.joinCluster(AssignmentManager.java:323)
> at
> org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:501)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:326)
> at java.lang.Thread.run(Thread.java:662)
> 2012-01-25 18:23:48,650 INFO namenode,6,1327512209588
> org.apache.hadoop.hbase.master.HMaster - Aborting
> {noformat}
> I think that's because I had a hard crash in the cluster a while ago - and
> the following WARN since then
> {noformat}
> 2012-01-25 21:20:47,121 WARN namenode,6,1327513078123-CatalogJanitor
> org.apache.hadoop.hbase.master.CatalogJanitor - REGIONINFO_QUALIFIER is empty
> in keyvalues={emails,,xxx./info:server/1314336400471/Put/vlen=38,
> emails,,1314189353300.xxx./info:serverstartcode/1314336400471/Put/vlen=8}
> {noformat}
> my patch was simple to go around the NPE (as the other code around the lines)
> but I don't know if that's correct
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-3584) Allow atomic put/delete in one call
[ https://issues.apache.org/jira/browse/HBASE-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210826#comment-13210826 ] Hudson commented on HBASE-3584: --- Integrated in HBase-TRUNK-security #114 (See [https://builds.apache.org/job/HBase-TRUNK-security/114/]) HBASE-3584 Rename RowMutation to RowMutations (Revision 1245792) Result = FAILURE stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/HTable.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/HTableInterface.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/RowMutation.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/RowMutations.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/coprocessor/CoprocessorHost.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/io/HbaseObjectWritable.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/ipc/HRegionInterface.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/coprocessor/TestRegionObserverInterface.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestAtomicOperation.java > Allow atomic put/delete in one call > --- > > Key: HBASE-3584 > URL: https://issues.apache.org/jira/browse/HBASE-3584 > Project: HBase > Issue Type: New Feature > Components: client, coprocessors, regionserver >Reporter: ryan rawson >Assignee: Lars Hofhansl > Fix For: 0.94.0 > > Attachments: 3584-final.txt, 3584-v1.txt, 3584-v3.txt > > > Right now we have the following calls: > put(Put) > delete(Delete) > increment(Increments) > But we cannot combine all of the above in a single call, complete with a > single row lock. It would be nice to do that. > It would also allow us to do a CAS where we could do a put/increment if the > check succeeded. > - > Amendment: > Since Increment does not currently support MVCC it cannot be included in an > atomic operation. > So this for Put and Delete only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5420) TestImportTsv does not shut down MR Cluster correctly (fails against 0.23 hadoop)
[ https://issues.apache.org/jira/browse/HBASE-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210827#comment-13210827 ] Hudson commented on HBASE-5420: --- Integrated in HBase-TRUNK-security #114 (See [https://builds.apache.org/job/HBase-TRUNK-security/114/]) HBASE-5420 TestImportTsv does not shut down MR Cluster correctly (fails against 0.23 hadoop) (Revision 1245795) Result = FAILURE stack : Files : * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java > TestImportTsv does not shut down MR Cluster correctly (fails against 0.23 > hadoop) > - > > Key: HBASE-5420 > URL: https://issues.apache.org/jira/browse/HBASE-5420 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 0.94.0, 0.92.0 >Reporter: Gregory Chanan >Assignee: Gregory Chanan > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-5420-v1.patch, HBASE-5420.patch > > > Test calls startMiniMapReduceCluster() but never calls > shutdownMiniMapReduceCluster(). > This causes failures with -Dhadoop.profile=23 when both testMROnTable and > testMROnTableWithCustomMapper are run, because the cluster cannot start up > properly for the second test. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5425) Punt on the timeout doesn't work in BulkEnabler#waitUntilDone (master's EnableTableHandler)
[
https://issues.apache.org/jira/browse/HBASE-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210830#comment-13210830
]
Hudson commented on HBASE-5425:
---
Integrated in HBase-TRUNK-security #114 (See
[https://builds.apache.org/job/HBase-TRUNK-security/114/])
HBASE-5425 Punt on the timeout doesn't work in BulkEnabler#waitUntilDone
(master's EnableTableHandler) (Revision 1245674)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/handler/EnableTableHandler.java
> Punt on the timeout doesn't work in BulkEnabler#waitUntilDone (master's
> EnableTableHandler)
>
>
> Key: HBASE-5425
> URL: https://issues.apache.org/jira/browse/HBASE-5425
> Project: HBase
> Issue Type: Bug
> Components: master
>Affects Versions: 0.90.5, 0.92.0
>Reporter: terry zhang
> Fix For: 0.94.0
>
> Attachments: HBASE-5425.patch
>
>
> please take a look at the code below in EnableTableHandler(hbase master):
> {code:title=EnableTableHandler.java|borderStyle=solid}
> protected boolean waitUntilDone(long timeout)
> throws InterruptedException {
>
> .
> int lastNumberOfRegions = this.countOfRegionsInTable;
> while (!server.isStopped() && remaining > 0) {
> Thread.sleep(waitingTimeForEvents);
> regions = assignmentManager.getRegionsOfTable(tableName);
> if (isDone(regions)) break;
> // Punt on the timeout as long we make progress
> if (regions.size() > lastNumberOfRegions) {
> lastNumberOfRegions = regions.size();
> timeout += waitingTimeForEvents;
> }
> remaining = timeout - (System.currentTimeMillis() - startTime);
>
> }
> private boolean isDone(final List regions) {
> return regions != null && regions.size() >= this.countOfRegionsInTable;
> }
> {code}
> We can easily find out if we let lastNumberOfRegions =
> this.countOfRegionsInTable , the function of punt on timeout code will never
> be executed. I think initlize lastNumberOfRegions = 0 can make it work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5421) use hadoop-client/hadoop-minicluster artifacts for Hadoop 0.23 build
[ https://issues.apache.org/jira/browse/HBASE-5421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210829#comment-13210829 ] Hudson commented on HBASE-5421: --- Integrated in HBase-TRUNK-security #114 (See [https://builds.apache.org/job/HBase-TRUNK-security/114/]) HBASE-5421 use hadoop-client/hadoop-minicluster artifacts for Hadoop 0.23 build (Revision 1245743) Result = FAILURE stack : Files : * /hbase/trunk/pom.xml > use hadoop-client/hadoop-minicluster artifacts for Hadoop 0.23 build > > > Key: HBASE-5421 > URL: https://issues.apache.org/jira/browse/HBASE-5421 > Project: HBase > Issue Type: Improvement > Components: build >Affects Versions: 0.92.0 >Reporter: Shaneal Manek >Assignee: Shaneal Manek >Priority: Minor > Labels: build > Fix For: 0.94.0, 0.92.1 > > Attachments: hbase-5421.patch > > > Hadoop recently added hadoop-client and hadoop-minicluster artifacts for > Hadoop 0.23+ that don't export all the internal dependencies (HADOOP-8009). > Let's use them instead of manually specifying transitive dependency exclusion > lists (which is error prone and annoying). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5195) [Coprocessors] preGet hook does not allow overriding or wrapping filter on incoming Get
[ https://issues.apache.org/jira/browse/HBASE-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210828#comment-13210828 ] Hudson commented on HBASE-5195: --- Integrated in HBase-TRUNK-security #114 (See [https://builds.apache.org/job/HBase-TRUNK-security/114/]) HBASE-5195 [Coprocessors] preGet hook does not allow overriding or wrapping filter on incoming Get -- SECOND HALF OF THIS COMMIT (Revision 1245773) Result = FAILURE stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java > [Coprocessors] preGet hook does not allow overriding or wrapping filter on > incoming Get > --- > > Key: HBASE-5195 > URL: https://issues.apache.org/jira/browse/HBASE-5195 > Project: HBase > Issue Type: Bug >Affects Versions: 0.94.0, 0.92.0 >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-5195.patch > > > Without the ability to wrap the internal Scan on the Get, we can't override > (or protect, in the case of access control) Gets as we can Scans. The result > is inconsistent behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4640) Catch ClosedChannelException and document it
[ https://issues.apache.org/jira/browse/HBASE-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210825#comment-13210825 ] Hudson commented on HBASE-4640: --- Integrated in HBase-TRUNK-security #114 (See [https://builds.apache.org/job/HBase-TRUNK-security/114/]) HBASE-4640 Catch ClosedChannelException and document it (Revision 1245730) Result = FAILURE jdcryans : Files : * /hbase/trunk/src/docbkx/troubleshooting.xml * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/ipc/HBaseServer.java > Catch ClosedChannelException and document it > > > Key: HBASE-4640 > URL: https://issues.apache.org/jira/browse/HBASE-4640 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.90.4 >Reporter: Jean-Daniel Cryans >Assignee: Jean-Daniel Cryans >Priority: Minor > Fix For: 0.94.0 > > Attachments: HBASE-4640.patch > > > ClosedChannelException is a pretty obscure exception for the non-expert and > doesn't tell you why you get it. We should instead catch it, print a WARN, > don't print a stack trace, and add a line in the book about this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5393) Consider splitting after flushing
[ https://issues.apache.org/jira/browse/HBASE-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210819#comment-13210819 ] Hudson commented on HBASE-5393: --- Integrated in HBase-TRUNK-security #114 (See [https://builds.apache.org/job/HBase-TRUNK-security/114/]) HBASE-5393 Consider splitting after flushing (Revision 1245727) Result = FAILURE jdcryans : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreFlusher.java > Consider splitting after flushing > - > > Key: HBASE-5393 > URL: https://issues.apache.org/jira/browse/HBASE-5393 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.90.5 >Reporter: Jean-Daniel Cryans >Assignee: Jean-Daniel Cryans > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-2375-flush-split.patch > > > Spawning this from HBASE-2375, I saw that it was much more efficient > compaction-wise to check if we can split right after flushing. Much like the > ideas that Jon spelled out in the description of that jira, the window is > smaller because you don't have to compact and then split right away to only > compact again when the daughters open. > Another thing it improves is while we're normally waiting for the compaction > to happen, data that's still coming in will make us go way past the > MAX_FILESIZE to a point where for the first region I was seeing a store size > 3-4x bigger before it was able to split. > I targeted this for 0.94, but I'd like to get this into 0.92.1 or .2 too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5427) Upgrade our zk to 3.4.3
[ https://issues.apache.org/jira/browse/HBASE-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210821#comment-13210821 ] Hudson commented on HBASE-5427: --- Integrated in HBase-TRUNK-security #114 (See [https://builds.apache.org/job/HBase-TRUNK-security/114/]) HBASE-5427 Upgrade our zk to 3.4.3 (Revision 1245759) Result = FAILURE stack : Files : * /hbase/trunk/pom.xml > Upgrade our zk to 3.4.3 > --- > > Key: HBASE-5427 > URL: https://issues.apache.org/jira/browse/HBASE-5427 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack > Fix For: 0.94.0, 0.92.1 > > Attachments: 5427.txt > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5294) Make sure javadoc is included in tarball bundle when we release
[ https://issues.apache.org/jira/browse/HBASE-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210823#comment-13210823 ] Hudson commented on HBASE-5294: --- Integrated in HBase-TRUNK-security #114 (See [https://builds.apache.org/job/HBase-TRUNK-security/114/]) HBASE-5294 Make sure javadoc is included in tarball bundle when we release (Revision 1245827) Result = FAILURE stack : Files : * /hbase/trunk/pom.xml * /hbase/trunk/src/docbkx/developer.xml > Make sure javadoc is included in tarball bundle when we release > --- > > Key: HBASE-5294 > URL: https://issues.apache.org/jira/browse/HBASE-5294 > Project: HBase > Issue Type: Task >Affects Versions: 0.92.0 >Reporter: stack >Assignee: Shaneal Manek >Priority: Critical > Fix For: 0.94.0, 0.92.1 > > Attachments: hbase-5294.patch > > > 0.92.0 doesn't have javadoc in the tarball. Fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5120) Timeout monitor races with table disable handler
[
https://issues.apache.org/jira/browse/HBASE-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210822#comment-13210822
]
Hudson commented on HBASE-5120:
---
Integrated in HBase-TRUNK-security #114 (See
[https://builds.apache.org/job/HBase-TRUNK-security/114/])
HBASE-5120 Timeout monitor races with table disable handler (Revision
1245731)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
> Timeout monitor races with table disable handler
>
>
> Key: HBASE-5120
> URL: https://issues.apache.org/jira/browse/HBASE-5120
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.92.0
>Reporter: Zhihong Yu
>Assignee: ramkrishna.s.vasudevan
>Priority: Blocker
> Fix For: 0.94.0
>
> Attachments: HBASE-5120.patch, HBASE-5120_1.patch,
> HBASE-5120_2.patch, HBASE-5120_3.patch, HBASE-5120_4.patch,
> HBASE-5120_5.patch, HBASE-5120_5.patch
>
>
> Here is what J-D described here:
> https://issues.apache.org/jira/browse/HBASE-5119?focusedCommentId=13179176&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13179176
> I think I will retract from my statement that it "used to be extremely racy
> and caused more troubles than it fixed", on my first test I got a stuck
> region in transition instead of being able to recover. The timeout was set to
> 2 minutes to be sure I hit it.
> First the region gets closed
> {quote}
> 2012-01-04 00:16:25,811 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Sent CLOSE to
> sv4r5s38,62023,1325635980913 for region
> test1,089cd0c9,1325635015491.1a4b111bcc228043e89f59c4c3f6a791.
> {quote}
> 2 minutes later it times out:
> {quote}
> 2012-01-04 00:18:30,026 INFO
> org.apache.hadoop.hbase.master.AssignmentManager: Regions in transition timed
> out: test1,089cd0c9,1325635015491.1a4b111bcc228043e89f59c4c3f6a791.
> state=PENDING_CLOSE, ts=1325636185810, server=null
> 2012-01-04 00:18:30,026 INFO
> org.apache.hadoop.hbase.master.AssignmentManager: Region has been
> PENDING_CLOSE for too long, running forced unassign again on
> region=test1,089cd0c9,1325635015491.1a4b111bcc228043e89f59c4c3f6a791.
> 2012-01-04 00:18:30,027 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Starting unassignment of
> region test1,089cd0c9,1325635015491.1a4b111bcc228043e89f59c4c3f6a791.
> (offlining)
> {quote}
> 100ms later the master finally gets the event:
> {quote}
> 2012-01-04 00:18:30,129 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Handling
> transition=RS_ZK_REGION_CLOSED, server=sv4r5s38,62023,1325635980913,
> region=1a4b111bcc228043e89f59c4c3f6a791, which is more than 15 seconds late
> 2012-01-04 00:18:30,129 DEBUG
> org.apache.hadoop.hbase.master.handler.ClosedRegionHandler: Handling CLOSED
> event for 1a4b111bcc228043e89f59c4c3f6a791
> 2012-01-04 00:18:30,129 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: Table being disabled so
> deleting ZK node and removing from regions in transition, skipping assignment
> of region test1,089cd0c9,1325635015491.1a4b111bcc228043e89f59c4c3f6a791.
> 2012-01-04 00:18:30,129 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign:
> master:62003-0x134589d3db03587 Deleting existing unassigned node for
> 1a4b111bcc228043e89f59c4c3f6a791 that is in expected state RS_ZK_REGION_CLOSED
> 2012-01-04 00:18:30,166 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign:
> master:62003-0x134589d3db03587 Successfully deleted unassigned node for
> region 1a4b111bcc228043e89f59c4c3f6a791 in expected state RS_ZK_REGION_CLOSED
> {quote}
> At this point everything is fine, the region was processed as closed. But
> wait, remember that line where it said it was going to force an unassign?
> {quote}
> 2012-01-04 00:18:30,322 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign:
> master:62003-0x134589d3db03587 Creating unassigned node for
> 1a4b111bcc228043e89f59c4c3f6a791 in a CLOSING state
> 2012-01-04 00:18:30,328 INFO
> org.apache.hadoop.hbase.master.AssignmentManager: Server null returned
> java.lang.NullPointerException: Passed server is null for
> 1a4b111bcc228043e89f59c4c3f6a791
> {quote}
> Now the master is confused, it recreated the RIT znode but the region doesn't
> even exist anymore. It even tries to shut it down but is blocked by NPEs. Now
> this is what's going on.
> The late ZK notification that the znode was deleted (but it got recreated
> after):
> {quote}
> 2012-01-04 00:19:33,285 DEBUG
> org.apache.hadoop.hbase.master.AssignmentManager: The znode of region
> test1,089cd0c9,1325635015491.1a4b111bcc228043e89f59c4c3f6a791. has been
> deleted.
> {quote}
> Then it prints this, and much later tries to unassign it again:
> {quote}
> 2012-01-04 00:19:46,607 DEBUG
>
[jira] [Commented] (HBASE-5428) Allow for custom filters to be registered within the Thrift interface
[ https://issues.apache.org/jira/browse/HBASE-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210820#comment-13210820 ] Hudson commented on HBASE-5428: --- Integrated in HBase-TRUNK-security #114 (See [https://builds.apache.org/job/HBase-TRUNK-security/114/]) HBASE-5428 Allow for custom filters to be registered within the Thrift interface (Revision 1245774) Result = FAILURE stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/filter/ParseFilter.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServerRunner.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/filter/TestParseFilter.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/thrift/TestThriftServer.java > Allow for custom filters to be registered within the Thrift interface > - > > Key: HBASE-5428 > URL: https://issues.apache.org/jira/browse/HBASE-5428 > Project: HBase > Issue Type: Improvement > Components: thrift >Affects Versions: 0.92.0 >Reporter: Robert Roland > Labels: patch > Fix For: 0.94.0 > > Attachments: ThriftCustomFilters.patch > > > Custom filters work within the Java client API, but are not accessible within > the Thrift API. Attempting to use one will generate a "Filter Name x not > supported" > Attached patch allows a user to specify a list of custom filters that are > registered at Thrift server startup time within the HBase configuration files: > > hbase.thrift.filters > MyFilter:com.foo.Filter,OtherFilter:com.foo.OtherFilter > > Patch created off SVN r1245727 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5294) Make sure javadoc is included in tarball bundle when we release
[ https://issues.apache.org/jira/browse/HBASE-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210803#comment-13210803 ] Hudson commented on HBASE-5294: --- Integrated in HBase-0.92 #290 (See [https://builds.apache.org/job/HBase-0.92/290/]) HBASE-5294 Make sure javadoc is included in tarball bundle when we release (Revision 1245826) Result = SUCCESS stack : Files : * /hbase/branches/0.92/pom.xml > Make sure javadoc is included in tarball bundle when we release > --- > > Key: HBASE-5294 > URL: https://issues.apache.org/jira/browse/HBASE-5294 > Project: HBase > Issue Type: Task >Affects Versions: 0.92.0 >Reporter: stack >Assignee: Shaneal Manek >Priority: Critical > Fix For: 0.94.0, 0.92.1 > > Attachments: hbase-5294.patch > > > 0.92.0 doesn't have javadoc in the tarball. Fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5420) TestImportTsv does not shut down MR Cluster correctly (fails against 0.23 hadoop)
[ https://issues.apache.org/jira/browse/HBASE-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210773#comment-13210773 ] Hudson commented on HBASE-5420: --- Integrated in HBase-0.92 #289 (See [https://builds.apache.org/job/HBase-0.92/289/]) HBASE-5420 TestImportTsv does not shut down MR Cluster correctly (fails against 0.23 hadoop) (Revision 1245796) Result = SUCCESS stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/mapreduce/TestImportTsv.java > TestImportTsv does not shut down MR Cluster correctly (fails against 0.23 > hadoop) > - > > Key: HBASE-5420 > URL: https://issues.apache.org/jira/browse/HBASE-5420 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 0.94.0, 0.92.0 >Reporter: Gregory Chanan >Assignee: Gregory Chanan > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-5420-v1.patch, HBASE-5420.patch > > > Test calls startMiniMapReduceCluster() but never calls > shutdownMiniMapReduceCluster(). > This causes failures with -Dhadoop.profile=23 when both testMROnTable and > testMROnTableWithCustomMapper are run, because the cluster cannot start up > properly for the second test. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5195) [Coprocessors] preGet hook does not allow overriding or wrapping filter on incoming Get
[ https://issues.apache.org/jira/browse/HBASE-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210706#comment-13210706 ] Hudson commented on HBASE-5195: --- Integrated in HBase-0.92 #288 (See [https://builds.apache.org/job/HBase-0.92/288/]) HBASE-5195 [Coprocessors] preGet hook does not allow overriding or wrapping filter on incoming Get (Revision 1245765) Result = SUCCESS stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java > [Coprocessors] preGet hook does not allow overriding or wrapping filter on > incoming Get > --- > > Key: HBASE-5195 > URL: https://issues.apache.org/jira/browse/HBASE-5195 > Project: HBase > Issue Type: Bug >Affects Versions: 0.94.0, 0.92.0 >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-5195.patch > > > Without the ability to wrap the internal Scan on the Get, we can't override > (or protect, in the case of access control) Gets as we can Scans. The result > is inconsistent behavior. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5279) NPE in Master after upgrading to 0.92.0
[
https://issues.apache.org/jira/browse/HBASE-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210705#comment-13210705
]
Hudson commented on HBASE-5279:
---
Integrated in HBase-0.92 #288 (See
[https://builds.apache.org/job/HBase-0.92/288/])
HBASE-5279 NPE in Master after upgrading to 0.92.0 (Revision 1245769)
Result = SUCCESS
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/catalog/MetaReader.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
> NPE in Master after upgrading to 0.92.0
> ---
>
> Key: HBASE-5279
> URL: https://issues.apache.org/jira/browse/HBASE-5279
> Project: HBase
> Issue Type: Bug
> Components: master
>Affects Versions: 0.92.0
>Reporter: Tobias Herbert
>Priority: Critical
> Fix For: 0.92.1
>
> Attachments: HBASE-5279-v2.patch, HBASE-5279.patch
>
>
> I have upgraded my environment from 0.90.4 to 0.92.0
> after the table migration I get the following error in the master (permanent)
> {noformat}
> 2012-01-25 18:23:48,648 FATAL master-namenode,6,1327512209588
> org.apache.hadoop.hbase.master.HMaster - Unhandled exception. Starting
> shutdown.
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.AssignmentManager.rebuildUserRegions(AssignmentManager.java:2190)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.joinCluster(AssignmentManager.java:323)
> at
> org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:501)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:326)
> at java.lang.Thread.run(Thread.java:662)
> 2012-01-25 18:23:48,650 INFO namenode,6,1327512209588
> org.apache.hadoop.hbase.master.HMaster - Aborting
> {noformat}
> I think that's because I had a hard crash in the cluster a while ago - and
> the following WARN since then
> {noformat}
> 2012-01-25 21:20:47,121 WARN namenode,6,1327513078123-CatalogJanitor
> org.apache.hadoop.hbase.master.CatalogJanitor - REGIONINFO_QUALIFIER is empty
> in keyvalues={emails,,xxx./info:server/1314336400471/Put/vlen=38,
> emails,,1314189353300.xxx./info:serverstartcode/1314336400471/Put/vlen=8}
> {noformat}
> my patch was simple to go around the NPE (as the other code around the lines)
> but I don't know if that's correct
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5421) use hadoop-client/hadoop-minicluster artifacts for Hadoop 0.23 build
[ https://issues.apache.org/jira/browse/HBASE-5421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210640#comment-13210640 ] Hudson commented on HBASE-5421: --- Integrated in HBase-0.92 #287 (See [https://builds.apache.org/job/HBase-0.92/287/]) HBASE-5421 use hadoop-client/hadoop-minicluster artifacts for Hadoop 0.23 build (Revision 1245742) Result = SUCCESS stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/pom.xml > use hadoop-client/hadoop-minicluster artifacts for Hadoop 0.23 build > > > Key: HBASE-5421 > URL: https://issues.apache.org/jira/browse/HBASE-5421 > Project: HBase > Issue Type: Improvement > Components: build >Affects Versions: 0.92.0 >Reporter: Shaneal Manek >Assignee: Shaneal Manek >Priority: Minor > Labels: build > Fix For: 0.94.0, 0.92.1 > > Attachments: hbase-5421.patch > > > Hadoop recently added hadoop-client and hadoop-minicluster artifacts for > Hadoop 0.23+ that don't export all the internal dependencies (HADOOP-8009). > Let's use them instead of manually specifying transitive dependency exclusion > lists (which is error prone and annoying). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5317) Fix TestHFileOutputFormat to work against hadoop 0.23
[ https://issues.apache.org/jira/browse/HBASE-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210639#comment-13210639 ] Hudson commented on HBASE-5317: --- Integrated in HBase-0.92 #287 (See [https://builds.apache.org/job/HBase-0.92/287/]) HBASE-5317 Fix testColumnFamilyCompression and test_TIMERANGE in TestHFileOutputFormat (Revision 1245724) Result = SUCCESS stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/mapreduce/TestHFileOutputFormat.java > Fix TestHFileOutputFormat to work against hadoop 0.23 > - > > Key: HBASE-5317 > URL: https://issues.apache.org/jira/browse/HBASE-5317 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 0.94.0, 0.92.0 >Reporter: Gregory Chanan >Assignee: Gregory Chanan > Attachments: HBASE-5317-v0.patch, HBASE-5317-v1.patch > > > Running > mvn -Dhadoop.profile=23 test -P localTests > -Dtest=org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat > yields this on 0.92: > Failed tests: > testColumnFamilyCompression(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat): > HFile for column family info-A not found > Tests in error: > test_TIMERANGE(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat): > /home/gchanan/workspace/apache92/target/test-data/276cbd0c-c771-4f81-9ba8-c464c9dd7486/test_TIMERANGE_present/_temporary/0/_temporary/_attempt_200707121733_0001_m_00_0 > (Is a directory) > > testMRIncrementalLoad(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat): > TestTable > > testMRIncrementalLoadWithSplit(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat): > TestTable > It looks like on trunk, this also results in an error: > > testExcludeMinorCompaction(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat): > TestTable > I have a patch that fixes testColumnFamilyCompression and test_TIMERANGE, but > haven't fixed the other 3 yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5393) Consider splitting after flushing
[ https://issues.apache.org/jira/browse/HBASE-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210637#comment-13210637 ] Hudson commented on HBASE-5393: --- Integrated in HBase-0.92 #287 (See [https://builds.apache.org/job/HBase-0.92/287/]) HBASE-5393 Consider splitting after flushing (Revision 1245726) Result = SUCCESS jdcryans : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreFlusher.java > Consider splitting after flushing > - > > Key: HBASE-5393 > URL: https://issues.apache.org/jira/browse/HBASE-5393 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.90.5 >Reporter: Jean-Daniel Cryans >Assignee: Jean-Daniel Cryans > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-2375-flush-split.patch > > > Spawning this from HBASE-2375, I saw that it was much more efficient > compaction-wise to check if we can split right after flushing. Much like the > ideas that Jon spelled out in the description of that jira, the window is > smaller because you don't have to compact and then split right away to only > compact again when the daughters open. > Another thing it improves is while we're normally waiting for the compaction > to happen, data that's still coming in will make us go way past the > MAX_FILESIZE to a point where for the first region I was seeing a store size > 3-4x bigger before it was able to split. > I targeted this for 0.94, but I'd like to get this into 0.92.1 or .2 too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5427) Upgrade our zk to 3.4.3
[ https://issues.apache.org/jira/browse/HBASE-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210638#comment-13210638 ] Hudson commented on HBASE-5427: --- Integrated in HBase-0.92 #287 (See [https://builds.apache.org/job/HBase-0.92/287/]) HBASE-5427 Upgrade our zk to 3.4.3 (Revision 1245760) Result = SUCCESS stack : Files : * /hbase/branches/0.92/pom.xml > Upgrade our zk to 3.4.3 > --- > > Key: HBASE-5427 > URL: https://issues.apache.org/jira/browse/HBASE-5427 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack > Fix For: 0.94.0, 0.92.1 > > Attachments: 5427.txt > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5425) Punt on the timeout doesn't work in BulkEnabler#waitUntilDone (master's EnableTableHandler)
[
https://issues.apache.org/jira/browse/HBASE-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210562#comment-13210562
]
Hudson commented on HBASE-5425:
---
Integrated in HBase-0.92 #286 (See
[https://builds.apache.org/job/HBase-0.92/286/])
HBASE-5425 Punt on the timeout doesn't work in BulkEnabler#waitUntilDone
(master's EnableTableHandler) (Revision 1245676)
Result = SUCCESS
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/handler/EnableTableHandler.java
> Punt on the timeout doesn't work in BulkEnabler#waitUntilDone (master's
> EnableTableHandler)
>
>
> Key: HBASE-5425
> URL: https://issues.apache.org/jira/browse/HBASE-5425
> Project: HBase
> Issue Type: Bug
> Components: master
>Affects Versions: 0.90.5, 0.92.0
>Reporter: terry zhang
> Fix For: 0.94.0
>
> Attachments: HBASE-5425.patch
>
>
> please take a look at the code below in EnableTableHandler(hbase master):
> {code:title=EnableTableHandler.java|borderStyle=solid}
> protected boolean waitUntilDone(long timeout)
> throws InterruptedException {
>
> .
> int lastNumberOfRegions = this.countOfRegionsInTable;
> while (!server.isStopped() && remaining > 0) {
> Thread.sleep(waitingTimeForEvents);
> regions = assignmentManager.getRegionsOfTable(tableName);
> if (isDone(regions)) break;
> // Punt on the timeout as long we make progress
> if (regions.size() > lastNumberOfRegions) {
> lastNumberOfRegions = regions.size();
> timeout += waitingTimeForEvents;
> }
> remaining = timeout - (System.currentTimeMillis() - startTime);
>
> }
> private boolean isDone(final List regions) {
> return regions != null && regions.size() >= this.countOfRegionsInTable;
> }
> {code}
> We can easily find out if we let lastNumberOfRegions =
> this.countOfRegionsInTable , the function of punt on timeout code will never
> be executed. I think initlize lastNumberOfRegions = 0 can make it work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5411) Add more metrics for ThriftMetrics
[ https://issues.apache.org/jira/browse/HBASE-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210073#comment-13210073 ] Hudson commented on HBASE-5411: --- Integrated in HBase-TRUNK-security #113 (See [https://builds.apache.org/job/HBase-TRUNK-security/113/]) HBASE-5411 Add more metrics for ThriftMetrics (Scott Chen) (Revision 1244977) Result = FAILURE tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/thrift/ThriftMetrics.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServerRunner.java > Add more metrics for ThriftMetrics > -- > > Key: HBASE-5411 > URL: https://issues.apache.org/jira/browse/HBASE-5411 > Project: HBase > Issue Type: Improvement > Components: metrics >Reporter: Scott Chen >Assignee: Scott Chen >Priority: Minor > Fix For: 0.94.0 > > Attachments: HBASE-5411.D1737.1.patch, HBASE-5411.D1737.2.patch > > > We found these numbers will be useful for the thrift metrics. > 1. connections to the thrift servers > 2. # rowkeys in batch puts > 3. # of keys in batch gets -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5346) Fix testColumnFamilyCompression and test_TIMERANGE in TestHFileOutputFormat
[ https://issues.apache.org/jira/browse/HBASE-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210074#comment-13210074 ] Hudson commented on HBASE-5346: --- Integrated in HBase-TRUNK-security #113 (See [https://builds.apache.org/job/HBase-TRUNK-security/113/]) HBASE-5346 Fix testColumnFamilyCompression and test_TIMERANGE in TestHFileOutputFormat (Revision 1245280) Result = FAILURE stack : Files : * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/mapreduce/TestHFileOutputFormat.java > Fix testColumnFamilyCompression and test_TIMERANGE in TestHFileOutputFormat > > > Key: HBASE-5346 > URL: https://issues.apache.org/jira/browse/HBASE-5346 > Project: HBase > Issue Type: Sub-task > Components: mapreduce, test >Affects Versions: 0.94.0, 0.92.0 >Reporter: Gregory Chanan >Assignee: Gregory Chanan > Fix For: 0.94.0 > > Attachments: HBASE-5346-v0.patch > > > Running > mvn -Dhadoop.profile=23 test -P localTests > -Dtest=org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat > yields this on 0.92 (for testColumnFamilyCompression and test_TIMERANGE): > Failed tests: > testColumnFamilyCompression(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat): > HFile for column family info-A not found > Tests in error: > test_TIMERANGE(org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat): > /home/gchanan/workspace/apache92/target/test-data/276cbd0c-c771-4f81-9ba8-c464c9dd7486/test_TIMERANGE_present/_temporary/0/_temporary/_attempt_200707121733_0001_m_00_0 > (Is a directory) > The problem is that these tests make incorrect assumptions about the output > of mapreduce jobs. Prior to 0.23, temporary data was in, for example: > ./_temporary/_attempt___r_00_0/b/1979617994050536795 > Now that has changed. The correct way to get that path is based on > getDefaultWorkFile. > Also, the data is not moved into the outputPath until both the Task and Job > are committed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5397) [book] zookeeper quorum mistake
[ https://issues.apache.org/jira/browse/HBASE-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210075#comment-13210075 ] Hudson commented on HBASE-5397: --- Integrated in HBase-TRUNK-security #113 (See [https://builds.apache.org/job/HBase-TRUNK-security/113/]) hbase-5397. performance.xml, configuration.xml - correction to ZK config. (Revision 1245199) Result = FAILURE > [book] zookeeper quorum mistake > --- > > Key: HBASE-5397 > URL: https://issues.apache.org/jira/browse/HBASE-5397 > Project: HBase > Issue Type: Bug >Reporter: Andre Medeiros >Assignee: Doug Meil >Priority: Minor > Attachments: docbkx_hbase_5397.patch > > > In Chapter 2, section 2.5 "ZooKeeper" under "How many ZooKeepers should I > run?" there is the sentence > *There can be no quorum if the number of members is an even number.* > This is not true. In ZooKeeper, an even number of peers is supported, but it > is normally not used because an even sized ensemble requires, proportionally, > more peers to form a quorum than an odd sized ensemble requires. For example, > an ensemble with 4 peers requires 3 to form a quorum, while an ensemble with > 5 also requires 3 to form a quorum. Thus, an ensemble of 5 allows 2 peers to > fail, and thus is more fault tolerant than the ensemble of 4, which allows > only 1 down peer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5197) [replication] Handle socket timeouts in ReplicationSource to prevent DDOS
[ https://issues.apache.org/jira/browse/HBASE-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209410#comment-13209410 ] Hudson commented on HBASE-5197: --- Integrated in HBase-TRUNK #2663 (See [https://builds.apache.org/job/HBase-TRUNK/2663/]) HBASE-5197 [replication] Handle socket timeouts in ReplicationSource to prevent DDOS (Revision 1243733) Result = FAILURE jdcryans : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java > [replication] Handle socket timeouts in ReplicationSource to prevent DDOS > - > > Key: HBASE-5197 > URL: https://issues.apache.org/jira/browse/HBASE-5197 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.90.5 >Reporter: Jean-Daniel Cryans >Assignee: Jean-Daniel Cryans > Fix For: 0.94.0, 0.90.6, 0.92.1 > > Attachments: HBASE-5197-v2.patch, HBASE-5197.patch > > > Kind of like HBASE-4462 but for replication. If while replicating you get a > socket timeout, the last thing you want to do is to retry it right away. > Since we can't fail the replication thread, the best I can think of is to > sleep a really long amount of time. > Planning to bring this to all branches. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5388) Tune HConnectionManager#getCachedLocation method
[
https://issues.apache.org/jira/browse/HBASE-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209412#comment-13209412
]
Hudson commented on HBASE-5388:
---
Integrated in HBase-TRUNK #2663 (See
[https://builds.apache.org/job/HBase-TRUNK/2663/])
HBASE-5388 Tune HConnectionManager#getCachedLocation method (Ronghai Ma)
(Revision 1243994)
Result = FAILURE
tedyu :
Files :
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/util/SoftValueSortedMap.java
> Tune HConnectionManager#getCachedLocation method
>
>
> Key: HBASE-5388
> URL: https://issues.apache.org/jira/browse/HBASE-5388
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 0.90.5
>Reporter: ronghai.ma
>Assignee: ronghai.ma
> Labels: patch
> Fix For: 0.94.0
>
> Attachments: 5388-v2.txt, 5388-v3.txt, 5388-v4.txt, 5388-v5.txt,
> 5388-v6.txt, HConnectionManager.java, SoftValueSortedMap.java,
> SoftValueSortedMap.java
>
>
> About 75% improvement in execution time.
> 1. Add the following method in SoftValueSortedMap:
> {code}
> public synchronized Entry lowerEntry(K key) {
> return ((TreeMap) this.internalMap).lowerEntry(key);
> }
> {code}
> 2. Modify getCachedLocation:
> {code}
> Map.Entry tEntry = tableLocations.lowerEntry(row);
> if (tEntry != null) {
> HRegionLocation possibleRegion = tEntry.getValue();
> //other code
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5411) Add more metrics for ThriftMetrics
[ https://issues.apache.org/jira/browse/HBASE-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209408#comment-13209408 ] Hudson commented on HBASE-5411: --- Integrated in HBase-TRUNK #2663 (See [https://builds.apache.org/job/HBase-TRUNK/2663/]) HBASE-5411 Add more metrics for ThriftMetrics (Scott Chen) (Revision 1244977) Result = FAILURE tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/thrift/ThriftMetrics.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServerRunner.java > Add more metrics for ThriftMetrics > -- > > Key: HBASE-5411 > URL: https://issues.apache.org/jira/browse/HBASE-5411 > Project: HBase > Issue Type: Improvement > Components: metrics >Reporter: Scott Chen >Assignee: Scott Chen >Priority: Minor > Fix For: 0.94.0 > > Attachments: HBASE-5411.D1737.1.patch, HBASE-5411.D1737.2.patch > > > We found these numbers will be useful for the thrift metrics. > 1. connections to the thrift servers > 2. # rowkeys in batch puts > 3. # of keys in batch gets -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5405) index.xml - correcting BigTable paper description
[ https://issues.apache.org/jira/browse/HBASE-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209405#comment-13209405 ] Hudson commented on HBASE-5405: --- Integrated in HBase-TRUNK #2663 (See [https://builds.apache.org/job/HBase-TRUNK/2663/]) hbase-5405. index.xml - correcting bigtable link description (Revision 1244659) Result = FAILURE > index.xml - correcting BigTable paper description > - > > Key: HBASE-5405 > URL: https://issues.apache.org/jira/browse/HBASE-5405 > Project: HBase > Issue Type: Bug >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Trivial > Attachments: index_hbase_5405.xml.patch > > > "Bigtable: A Distributed Storage System for Structured" should be "Bigtable: > A Distributed Storage System for Structured Data" (the "data" was missing) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5404) [book] adding performance info about compression and schema design
[ https://issues.apache.org/jira/browse/HBASE-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209407#comment-13209407 ] Hudson commented on HBASE-5404: --- Integrated in HBase-TRUNK #2663 (See [https://builds.apache.org/job/HBase-TRUNK/2663/]) hbase-5404. book.xml, performance.xml - more info on compression and schema design (Revision 1244649) Result = FAILURE > [book] adding performance info about compression and schema design > -- > > Key: HBASE-5404 > URL: https://issues.apache.org/jira/browse/HBASE-5404 > Project: HBase > Issue Type: Improvement >Reporter: Doug Meil >Assignee: Doug Meil >Priority: Minor > Attachments: docbkx_hbase_5404.patch > > > performance.xml > * added "however.." section describing that compression only affects data on > disk. If you have long keys and too-big comlumn names, you'll still pay the > price for that on the wire. > book.xml > * added a few links to arch/storefile section in the schema design chapter. > * added link to perf.schema from schema design chapter, ops section. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
