[
https://issues.apache.org/jira/browse/HBASE-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13550500#comment-13550500
]
Jean-Daniel Cryans commented on HBASE-7534:
-------------------------------------------
bq. Go commit. See if it fixes the fails.
FWIW the current failures are unrelated to this, from what I can tell the
machine where Jenkins runs is either slow or something is slowing us down. For
example in build 717's log for TestReplication.queueFailover:
{noformat}
2013-01-09 06:14:47,771 DEBUG
[RegionServer:1;vesta.apache.org,41495,1357711464011-EventThread.replicationSource,2]
regionserver.ReplicationSource(638): Replicating 3
2013-01-09 06:14:49,730 INFO [Thread-1887] replication.TestReplication(779):
Only got 9720 rows instead of 17576 current i=-16
2013-01-09 06:14:55,176 INFO [Thread-1887] replication.TestReplication(779):
Only got 9720 rows instead of 17576 current i=-15
2013-01-09 06:14:56,789 DEBUG
[RegionServer:1;vesta.apache.org,41495,1357711464011-EventThread.replicationSource,2]
regionserver.ReplicationSource(651): Replicated in total: 1837
{noformat}
You can see that it took 9 seconds to replicate a bunch of rows and no progress
is made. It runs way faster than that on my machine.
> [replication] TestReplication.queueFailover can fail because
> HBaseTestingUtility.createMultiRegions is dangerous
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-7534
> URL: https://issues.apache.org/jira/browse/HBASE-7534
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.3
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Fix For: 0.96.0, 0.94.5
>
> Attachments: HBASE-7534.patch
>
>
> {{HBaseTestingUtility.createMultiRegions}} is an abomination, it uses an
> already existing table and hot replaces the regions in it. I've seen
> TestReplication failing a few times because the "old" first region is still
> assigned and tried to flush but crashed due to the fact that the region's
> folder is missing in HDFS:
> {noformat}
> 2013-01-04 10:04:45,500 DEBUG
> [RegionServer:1;172.21.3.117,57114,1357322589018.cacheFlusher]
> regionserver.Store(844): Renaming flushed file at
> hdfs://localhost:57099/user/jdcryans/hbase/test/62c85f8a6e3d0e32b2fb21326537f5a6/.tmp/b938b33268064312abfc250d2eeca61d
> to
> hdfs://localhost:57099/user/jdcryans/hbase/test/62c85f8a6e3d0e32b2fb21326537f5a6/f/b938b33268064312abfc250d2eeca61d
> 2013-01-04 10:04:45,500 WARN [IPC Server handler 8 on 57099]
> namenode.FSDirectory(422): DIR* FSDirectory.unprotectedRenameTo: failed to
> rename
> /user/jdcryans/hbase/test/62c85f8a6e3d0e32b2fb21326537f5a6/.tmp/b938b33268064312abfc250d2eeca61d
> to
> /user/jdcryans/hbase/test/62c85f8a6e3d0e32b2fb21326537f5a6/f/b938b33268064312abfc250d2eeca61d
> because destination's parent does not exist
> 2013-01-04 10:04:45,503 WARN
> [RegionServer:1;172.21.3.117,57114,1357322589018.cacheFlusher]
> regionserver.Store(847): Unable to rename
> hdfs://localhost:57099/user/jdcryans/hbase/test/62c85f8a6e3d0e32b2fb21326537f5a6/.tmp/b938b33268064312abfc250d2eeca61d
> to
> hdfs://localhost:57099/user/jdcryans/hbase/test/62c85f8a6e3d0e32b2fb21326537f5a6/f/b938b33268064312abfc250d2eeca61d
> 2013-01-04 10:04:45,504 WARN [DataStreamer for file
> /user/jdcryans/hbase/.logs/172.21.3.117,57113,1357322588994/172.21.3.117%2C57113%2C1357322588994.1357322683769]
> hdfs.DFSClient$DFSOutputStream$DataStreamer(2873): DataStreamer Exception:
> org.apache.hadoop.ipc.RemoteException:
> org.apache.hadoop.hdfs.server.namenode.LeaseExpiredException: No lease on
> /user/jdcryans/hbase/.logs/172.21.3.117,57113,1357322588994/172.21.3.117%2C57113%2C1357322588994.1357322683769
> File does not exist. [Lease. Holder:
> DFSClient_hb_rs_172.21.3.117,57113,1357322588994, pendingcreates: 1]
> {noformat}
> Eventually the test times out because both region servers on the master
> cluster are dead.
> It can be easily fixed by pre-creating the table with enough regions.
> FWIW a bunch of other tests are using this facility, my IDE tells me that the
> 3 methods are called 25 times outside of {{HBaseTestingUtility}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
