[jira] [Assigned] (HBASE-5795) hbase-3927 breaks 0.92<->0.94 compatibility
[
https://issues.apache.org/jira/browse/HBASE-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reassigned HBASE-5795:
Assignee: stack
> hbase-3927 breaks 0.92<->0.94 compatibility
> ---
>
> Key: HBASE-5795
> URL: https://issues.apache.org/jira/browse/HBASE-5795
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Assignee: stack
>
> This commit broke our 0.92/0.94 compatibility:
> {code}
>
> r1136686 | stack | 2011-06-16 14:18:08 -0700 (Thu, 16 Jun 2011) | 1 line
> HBASE-3927 display total uncompressed byte size of a region in web UI
> {code}
> I just tried the new RC for 0.94. I brought up a 0.94 master on a 0.92
> cluster and rather than just digest version 1 of the HServerLoad, I get this:
> {code}
> 2012-04-14 22:47:59,752 WARN org.apache.hadoop.ipc.HBaseServer: Unable to
> read call parameters for client 10.4.14.38
> java.io.IOException: Error in readFields
> at
> org.apache.hadoop.hbase.io.HbaseObjectWritable.readObject(HbaseObjectWritable.java:684)
> at
> org.apache.hadoop.hbase.ipc.Invocation.readFields(Invocation.java:125)
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Connection.processData(HBaseServer.java:1269)
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Connection.readAndProcess(HBaseServer.java:1184)
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Listener.doRead(HBaseServer.java:722)
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Listener$Reader.doRunLoop(HBaseServer.java:513)
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Listener$Reader.run(HBaseServer.java:488)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: A record version mismatch occured. Expecting v2, found v1
> at
> org.apache.hadoop.io.VersionedWritable.readFields(VersionedWritable.java:46)
> at
> org.apache.hadoop.hbase.HServerLoad$RegionLoad.readFields(HServerLoad.java:379)
> at
> org.apache.hadoop.hbase.HServerLoad.readFields(HServerLoad.java:686)
> at
> org.apache.hadoop.hbase.io.HbaseObjectWritable.readObject(HbaseObjectWritable.java:681)
> ... 9 more
> {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] [Assigned] (HBASE-5774) Add documentation for WALPlayer to HBase reference guide.
[ https://issues.apache.org/jira/browse/HBASE-5774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-5774: Assignee: Doug Meil (was: Lars Hofhansl) Assigning Doug to take a looksee (assign back to Lars if you all good w/ it Doug) > Add documentation for WALPlayer to HBase reference guide. > - > > Key: HBASE-5774 > URL: https://issues.apache.org/jira/browse/HBASE-5774 > Project: HBase > Issue Type: Sub-task >Reporter: Lars Hofhansl >Assignee: Doug Meil > Attachments: 5774.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] [Assigned] (HBASE-5754) data lost with gora continuous ingest test (goraci)
[ https://issues.apache.org/jira/browse/HBASE-5754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-5754: Assignee: stack > data lost with gora continuous ingest test (goraci) > --- > > Key: HBASE-5754 > URL: https://issues.apache.org/jira/browse/HBASE-5754 > Project: HBase > Issue Type: Bug >Affects Versions: 0.92.1 > Environment: 10 node test cluster >Reporter: Eric Newton >Assignee: stack > > Keith Turner re-wrote the accumulo continuous ingest test using gora, which > has both hbase and accumulo back-ends. > I put a billion entries into HBase, and ran the Verify map/reduce job. The > verification failed because about 21K entries were missing. The goraci > [README|https://github.com/keith-turner/goraci] explains the test, and how it > detects missing data. > I re-ran the test with 100 million entries, and it verified successfully. > Both of the times I tested using a billion entries, the verification failed. > If I run the verification step twice, the results are consistent, so the > problem is > probably not on the verify step. > Here's the versions of the various packages: > ||package||version|| > |hadoop|0.20.205.0| > |hbase|0.92.1| > |gora|http://svn.apache.org/repos/asf/gora/trunk r1311277| > |goraci|https://github.com/ericnewton/goraci tagged 2012-04-08| > The change I made to goraci was to configure it for hbase and to allow it to > build properly. -- 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] [Assigned] (HBASE-5706) "Dropping fs latency stats since buffer is full" spam
[
https://issues.apache.org/jira/browse/HBASE-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reassigned HBASE-5706:
Assignee: Shaneal Manek
> "Dropping fs latency stats since buffer is full" spam
> -
>
> Key: HBASE-5706
> URL: https://issues.apache.org/jira/browse/HBASE-5706
> Project: HBase
> Issue Type: Improvement
>Reporter: Jean-Daniel Cryans
>Assignee: Shaneal Manek
>Priority: Minor
> Fix For: 0.94.0, 0.96.0
>
>
> I see tons of this while running tests (note that it's a WARN):
> {noformat}
> 2012-04-03 18:54:47,172 WARN org.apache.hadoop.hbase.io.hfile.HFile: Dropping
> fs latency stats since buffer is full
> {noformat}
> While the code says this:
> {noformat}
> // we don't want to fill up the logs with this message, so only log it
> // once every 30 seconds at most
> // I also want to avoid locks on the 'critical path' (the common case will
> be
> // uncontended) - hence the CAS
> private static void logDroppedLatencyStat() {
> {noformat}
> It doesn't seem like this message is actionnable and even though it's printed
> "only" every 30 seconds it's still very spammy.
> We should get rid of it or make it more useful (I don't know which).
--
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] [Assigned] (HBASE-5610) Add GA to hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-5610: Assignee: stack > Add GA to hbase.apache.org > -- > > Key: HBASE-5610 > URL: https://issues.apache.org/jira/browse/HBASE-5610 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack > Fix For: 0.96.0 > > Attachments: ga.txt > > > Lets add the bit of script necessary tracking hbase.apache.org in google > analytics. I was going to get it going first then open it to the PMC for > viewing. -- 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] [Assigned] (HBASE-5328) Small changes to Master to make it more testable
[ https://issues.apache.org/jira/browse/HBASE-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-5328: Assignee: stack > Small changes to Master to make it more testable > > > Key: HBASE-5328 > URL: https://issues.apache.org/jira/browse/HBASE-5328 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack > Attachments: 5328.txt, 5328v2.txt, 5328v2.txt > > > Here are some small changes in Master that make it more testable. Included > tests stand up a Master and then fake it into thinking that three > regionservers are registering making master assign root and meta, etc. -- 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] [Assigned] (HBASE-5570) Compression tool section is referring to wrong link in HBase Book.
[ https://issues.apache.org/jira/browse/HBASE-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-5570: Assignee: Doug Meil Ok if I assign this to you Mr. Doug? > Compression tool section is referring to wrong link in HBase Book. > -- > > Key: HBASE-5570 > URL: https://issues.apache.org/jira/browse/HBASE-5570 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 0.90.7, 0.92.2, 0.94.0, 0.96.0 >Reporter: Laxman >Assignee: Doug Meil >Priority: Trivial > Labels: documentaion > > http://hbase.apache.org/book/ops_mgt.html#compression.tool > Above section is refering to itself (recursive) in HBase book. > This needs to be corrected. -- 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] [Assigned] (HBASE-4608) HLog Compression
[ https://issues.apache.org/jira/browse/HBASE-4608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-4608: Assignee: stack (was: Li Pi) > HLog Compression > > > Key: HBASE-4608 > URL: https://issues.apache.org/jira/browse/HBASE-4608 > Project: HBase > Issue Type: New Feature >Reporter: Li Pi >Assignee: stack > Fix For: 0.94.0 > > Attachments: 4608-v19.txt, 4608-v20.txt, 4608-v22.txt, 4608v1.txt, > 4608v13.txt, 4608v13.txt, 4608v14.txt, 4608v15.txt, 4608v16.txt, 4608v17.txt, > 4608v18.txt, 4608v5.txt, 4608v6.txt, 4608v7.txt, 4608v8fixed.txt > > > The current bottleneck to HBase write speed is replicating the WAL appends > across different datanodes. We can speed up this process by compressing the > HLog. Current plan involves using a dictionary to compress table name, region > id, cf name, and possibly other bits of repeated data. Also, HLog format may > be changed in other ways to produce a smaller HLog. -- 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] [Assigned] (HBASE-5426) How to Set Up a Pseudo-Distributed Mode for HBase
[ https://issues.apache.org/jira/browse/HBASE-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-5426: Assignee: Doug Meil Mind parsing this for its goodness Mr Meil? > How to Set Up a Pseudo-Distributed Mode for HBase > - > > Key: HBASE-5426 > URL: https://issues.apache.org/jira/browse/HBASE-5426 > Project: HBase > Issue Type: Improvement > Components: documentation >Affects Versions: 0.92.0 > Environment: RedHat 7, Ubuntu 10 >Reporter: Bing Li >Assignee: Doug Meil > Labels: documentation > Fix For: 0.92.0 > > Original Estimate: 48h > Remaining Estimate: 48h > > Hi, all, > I just made a summary about the experiences to set up a pseudo-distributed > mode HBase. > 1) RedHat 9 is not suitable for running HBase and Hadoop. I don't know the > reasons. Now Ubuntu is my choice. > 2) After the pseudo-distributed mode of HDFS is configured, it is required to > configure the hbase-env.sh and hbase-site.xml. The book, HBase the Definitive > Guide, does not mentions hbase.env.xml. > 3) It should set up JAVA_HOME, HBASE_CLASSPATH and HBASE_MANAGES_ZK. My > hbase-env.sh is as follows. > export JAVA_HOME=/opt/jdk1.6.1/ > export HBASE_CLASSPATH=/opt/hbase-0.92.0/conf > export HBASE_OPTS="-XX:+UseConcMarkSweepGC" > export HBASE_MANAGES_ZK=true > 4) When configuring hbase-site.xml, the property, hbase.cluster.distributed, > must be set also. The book, HBase the Definitive Guide, does not do that > either. My hbase-site.xml is as follows. > > > > >hbase.rootdir >hdfs://localhost:9000/hbase > > >dfs.replication >1 > > >hbase.cluster.distributed >true > > > I am a new user of HBase. Your suggestions are highly appreciated. > Best regards, > Bing -- 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] [Assigned] (HBASE-5412) HBase book, section 2.6.4, has deficient list of client dependencies
[ https://issues.apache.org/jira/browse/HBASE-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-5412: Assignee: Doug Meil Mind taking care of this one Doug? This looks like a 0.92.0ism so needs dnoting so in the book as for 0.92.0. Thanks. > HBase book, section 2.6.4, has deficient list of client dependencies > > > Key: HBASE-5412 > URL: https://issues.apache.org/jira/browse/HBASE-5412 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 0.92.0 >Reporter: Mike Spreitzer >Assignee: Doug Meil >Priority: Minor > Labels: documentation > Original Estimate: 1h > Remaining Estimate: 1h > > The current text in section 2.6.4 of the HBase book says this about client > dependencies: > Minimally, a client of HBase needs the hbase, hadoop, log4j, commons-logging, > commons-lang, and ZooKeeper jars in its CLASSPATH connecting to a cluster. > I tried that, and got an exception due to a class not being found. I fixed > that by searching for that class in the jars in lib/, and tried again. Got > an exception, due to a different class not found. I iterated until it > worked. When I was done, I found myself using the following JARs: > commons-configuration-1.6.jar hadoop-core-1.0.0.jar slf4j-api-1.5.8.jar > commons-lang-2.5.jar hbase-0.92.0.jar slf4j-log4j12-1.5.8.jar > commons-logging-1.1.1.jar log4j-1.2.16.jar zookeeper-3.4.2.jar -- 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] [Assigned] (HBASE-5397) [book] zookeeper quorum mistake
[ https://issues.apache.org/jira/browse/HBASE-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-5397: Assignee: Doug Meil Can you do this Doug? > [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 > > 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] [Assigned] (HBASE-5115) Change HBase "color" from purple to "International Orange (Engineering)"
[ https://issues.apache.org/jira/browse/HBASE-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-5115: Assignee: stack > Change HBase "color" from purple to "International Orange (Engineering)" > > > Key: HBASE-5115 > URL: https://issues.apache.org/jira/browse/HBASE-5115 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack > Attachments: 01_orange.png, 01_orange.svg > > > See http://en.wikipedia.org/wiki/International_orange See the bit about the > color of the golden gate bridge. -- 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] [Assigned] (HBASE-5172) HTableInterface should extend java.io.Closeable
[ https://issues.apache.org/jira/browse/HBASE-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-5172: Assignee: stack > HTableInterface should extend java.io.Closeable > --- > > Key: HBASE-5172 > URL: https://issues.apache.org/jira/browse/HBASE-5172 > Project: HBase > Issue Type: Bug >Reporter: Zhihong Yu >Assignee: stack > Attachments: 5172.txt > > > Ioan Eugen Stan found this issue. -- 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] [Assigned] (HBASE-5152) Region is on service before completing initialization when doing rollback of split, it will affect read correctness
[ https://issues.apache.org/jira/browse/HBASE-5152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-5152: Assignee: chunhui shen > Region is on service before completing initialization when doing rollback of > split, it will affect read correctness > > > Key: HBASE-5152 > URL: https://issues.apache.org/jira/browse/HBASE-5152 > Project: HBase > Issue Type: Bug >Reporter: chunhui shen >Assignee: chunhui shen > Fix For: 0.92.0, 0.94.0 > > Attachments: 5152-v2.txt, hbase-5152.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] [Assigned] (HBASE-4519) 25s sleep when expiring sessions in tests
[
https://issues.apache.org/jira/browse/HBASE-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reassigned HBASE-4519:
Assignee: nkeywal
Nicolas, you might want to take a look at thi sone.
> 25s sleep when expiring sessions in tests
> -
>
> Key: HBASE-4519
> URL: https://issues.apache.org/jira/browse/HBASE-4519
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 0.90.4
>Reporter: Jean-Daniel Cryans
>Assignee: nkeywal
> Fix For: 0.92.0
>
>
> There's a hardcoded 25 seconds sleep in HBaseTestingUtility.expireSession:
> {code}
> int sessionTimeout = 5 * 1000; // 5 seconds
> ...
> final long sleep = sessionTimeout * 5L;
> LOG.info("ZK Closed Session 0x" + Long.toHexString(sessionID) +
> "; sleeping=" + sleep);
> Thread.sleep(sleep);
> {code}
> I'm pretty sure this can be lowered at lot, and it would speed up a couple of
> tests. The only thing I'm afraid of is if this was made to accomodate flaky
> tests.
--
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] [Assigned] (HBASE-2675) Quick "smoke tests" testsuite
[ https://issues.apache.org/jira/browse/HBASE-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-2675: Assignee: nkeywal Assigning this to you Nicolas since it looks like you are fixing this at mo. > Quick "smoke tests" testsuite > - > > Key: HBASE-2675 > URL: https://issues.apache.org/jira/browse/HBASE-2675 > Project: HBase > Issue Type: Test >Reporter: Benoit Sigoure >Assignee: nkeywal >Priority: Minor > > It would be nice if there was a known subset of the tests that run fast (e.g. > not more than a few seconds) and quickly help us check whether the code isn't > horribly broken. This way one could run those tests at a frequent interval > when iterating and only run the entire testsuite at the end, when they think > they're done, since doing so is very time consuming. > Someone would need to identify which tests really focus on the core > functionality and add a target in the build system to just run those tests. > As a bonus, it would be awesome++ if the core tests ran, say, 10x faster than > they currently do. There's a lot of "sleep"-based "synchronization" in the > tests and it would be nice to remove some of that where possible to make the > tests run as fast as the machine can handle them. -- 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] [Assigned] (HBASE-4559) Refactor TestAvroServer into an integration test
[ https://issues.apache.org/jira/browse/HBASE-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-4559: Assignee: Jesse Yates > Refactor TestAvroServer into an integration test > > > Key: HBASE-4559 > URL: https://issues.apache.org/jira/browse/HBASE-4559 > Project: HBase > Issue Type: Improvement > Components: test >Reporter: Jesse Yates >Assignee: Jesse Yates > Attachments: java_HBASE_4559.txt > > > TestAvroServer is a beefy test, spins up a mini cluster, does a large series > of manipulations and then spins it down. It take about 2 mins to run on a > local machine, which on the high side for a 'unit' test. > This is part of the implentation discussed in > http://search-hadoop.com/m/L9OzBNEOJK1 -- 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] [Assigned] (HBASE-3387) Pair does not deep check arrays for equality.
[ https://issues.apache.org/jira/browse/HBASE-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-3387: Assignee: Jesse Yates > Pair does not deep check arrays for equality. > -- > > Key: HBASE-3387 > URL: https://issues.apache.org/jira/browse/HBASE-3387 > Project: HBase > Issue Type: Bug > Components: util >Affects Versions: 0.90.1 > Environment: Any (discovered in Ubuntu 10.10 using TRUNK). >Reporter: Jesse Yates >Assignee: Jesse Yates > Attachments: HBASE-3387-revert.patch, HBASE-3387.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > Pair does not deep check arrays for equality. It merely does x.equals(y) for > the sent Object. However, with any type of array this is merely going to > compare the array pointers, rather than the underlying data structure. > It requires a rewriting of the private equals method in Pair to check for > elements being an array, then checking the underlying elements. -- 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] [Assigned] (HBASE-4454) Add failsafe plugin to build and rename integration tests
[ https://issues.apache.org/jira/browse/HBASE-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-4454: Assignee: Jesse Yates > Add failsafe plugin to build and rename integration tests > - > > Key: HBASE-4454 > URL: https://issues.apache.org/jira/browse/HBASE-4454 > Project: HBase > Issue Type: Improvement >Reporter: Jesse Yates >Assignee: Jesse Yates > Fix For: 0.92.0 > > Attachments: mvn_HBASE-4454.patch > > > Add the maven-failsafe-plugin to the build process so we can run integration > tests with "mvn verify". This will also involve a renaming of integration > tests to conform to a new integration test regex. > This is a stopgap measure while we until break them out into their own module. -- 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] [Assigned] (HBASE-4561) Update Maven documentation in book
[ https://issues.apache.org/jira/browse/HBASE-4561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-4561: Assignee: Jesse Yates > Update Maven documentation in book > -- > > Key: HBASE-4561 > URL: https://issues.apache.org/jira/browse/HBASE-4561 > Project: HBase > Issue Type: Improvement > Components: documentation >Reporter: Jesse Yates >Assignee: Jesse Yates >Priority: Minor > Attachments: book_HBASE-4561.txt > > > The maven documentation is a little out of date and has recently led to some > confusion about tests. This would cleanup the maven documents in the book to > be more explicit about how maven should be used. -- 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] [Assigned] (HBASE-4531) hbase-4454 failsafe broke mvn site; back it out or fix
[
https://issues.apache.org/jira/browse/HBASE-4531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reassigned HBASE-4531:
Assignee: Akash Ashok
> hbase-4454 failsafe broke mvn site; back it out or fix
> --
>
> Key: HBASE-4531
> URL: https://issues.apache.org/jira/browse/HBASE-4531
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Assignee: Akash Ashok
>Priority: Blocker
> Fix For: 0.92.0
>
> Attachments: HBase-4531-v2.patch, HBase-4531-v2.patch,
> HBase-4531.patch
>
>
> mvn site is broke in head of trunk. If I back out the last pom change it
> works again:
> {code}
>
> r1177168 | stack | 2011-09-29 05:42:13 + (Thu, 29 Sep 2011) | 1 line
> HBASE-4454 Add failsafe plugin to build and rename integration tests
> {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] [Assigned] (HBASE-4497) If region opening fails after updating META HBCK reports it as inconsistent and scanning the region throws NSRE
[ https://issues.apache.org/jira/browse/HBASE-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-4497: Assignee: stack > If region opening fails after updating META HBCK reports it as inconsistent > and scanning the region throws NSRE > --- > > Key: HBASE-4497 > URL: https://issues.apache.org/jira/browse/HBASE-4497 > Project: HBase > Issue Type: Bug >Reporter: ramkrishna.s.vasudevan >Assignee: stack >Priority: Critical > > As per the discussion in the mail chain "HBCK reporting of possible mismatch > in RS assignment" this JIRA is created. > Consider two RS-> RS1 and RS2. > A region tries to open in RS1. But it takes a while. The RS1 has still not > updated meta and transitioned the node from OPENING to OPENED > So timeout assigns the region to RS2. RS2 successfully updates the META and > opens the region. > Now RS1 tries to act on the region by first updating the META and then > transiting the node to OPENING to OPENED. > RS1 transiting the node to OPENING to OPENED will fail. But the META entry > will have RS1 as the latest. > Now HBCK reports this as an inconsistency and if we try to scan the Region we > get NotServingRegionException. -- 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] [Assigned] (HBASE-4507) Create checkAndPut variant that exposes timestamp / UUID
[ https://issues.apache.org/jira/browse/HBASE-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-4507: Assignee: stack > Create checkAndPut variant that exposes timestamp / UUID > > > Key: HBASE-4507 > URL: https://issues.apache.org/jira/browse/HBASE-4507 > Project: HBase > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: stack > > Michael checked the checkAndPut which doesn't expose timestamp. A variant of > checkAndPut should be created to expose timestamp which is written into a > column specified by additional parameters. -- 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] [Assigned] (HBASE-4503) Purge deprecated HBaseClusterTestCase
[ https://issues.apache.org/jira/browse/HBASE-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reassigned HBASE-4503: Assignee: stack > Purge deprecated HBaseClusterTestCase > - > > Key: HBASE-4503 > URL: https://issues.apache.org/jira/browse/HBASE-4503 > Project: HBase > Issue Type: Improvement >Reporter: stack >Assignee: stack > Attachments: 4503-v2.txt, 4503.txt > > > It could gain us a few minutes on overall test run in the cases where we > don't spin up a cluster for each 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
