[jira] [Created] (HBASE-27385) Rs shut down because of DroppedSnapshotException when memstore flushing
xufeng created HBASE-27385:
--
Summary: Rs shut down because of DroppedSnapshotException when
memstore flushing
Key: HBASE-27385
URL: https://issues.apache.org/jira/browse/HBASE-27385
Project: HBase
Issue Type: Bug
Components: regionserver
Affects Versions: 1.0.0
Reporter: xufeng
After memstore be flushed, flush marker will be writed to WAL.
But current wal being rolled now, the DroppedSnapshotException will happen.
if (wal != null) {
// write flush marker to WAL. If fail, we should throw
DroppedSnapshotException
FlushDescriptor desc =
ProtobufUtil.toFlushDescriptor(FlushAction.COMMIT_FLUSH,
getRegionInfo(), flushOpSeqId, committedFiles);
WALUtil.writeFlushMarker(wal, this.htableDescriptor, getRegionInfo(),
desc, sequenceId, true);
}
} catch (Throwable t) {
...
DroppedSnapshotException dse = new DroppedSnapshotException("region: " +
Bytes.toStringBinary(getRegionName()));
dse.initCause(t);
status.abort("Flush failed: " + StringUtils.stringifyException(t));
throw dse;
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (HBASE-7191) HBCK - Add offline create/fix hbase.version and hbase.id
[ https://issues.apache.org/jira/browse/HBASE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748477#comment-16748477 ] xufeng commented on HBASE-7191: --- [~stack] >> You could create one offline and copy it into place. yes , it works. >>On the id, I don't recall I also did not test it. ok :) thank you for your reply. > HBCK - Add offline create/fix hbase.version and hbase.id > - > > Key: HBASE-7191 > URL: https://issues.apache.org/jira/browse/HBASE-7191 > Project: HBase > Issue Type: Improvement > Components: hbck >Affects Versions: 0.94.1 >Reporter: Enis Soztutar >Priority: Major > Attachments: 7191-2.patch, hbck1-1.4-v1.patch > > > One of our clients run into a problem, in which they have the hbase.root.dir, > and cluster data, but their hbase.id and hbase.version files are corrupted. > HMaster creates those on start, but not if there is already existing data. > We can add smt like --fixIdFile, and ability for HBCK to do some offline > repairs for the version file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-7191) HBCK - Add offline create/fix hbase.version and hbase.id
[ https://issues.apache.org/jira/browse/HBASE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748354#comment-16748354 ] xufeng commented on HBASE-7191: --- Do we maintain the branch-1.* ？ in fact, I am writing the handbook of maintenance for the maintenance team。 The hbck tool is very important so I dig it 。but also found others problem. for example: 1. create the new table with some empty regions. 2. delete the .regioninfo file in one region folder(I want to make the INCONSISTENT and to fix it) 3. hbase hbck -fixHdfsOrphans result：the region folder will be sidelined because no data。 > HBCK - Add offline create/fix hbase.version and hbase.id > - > > Key: HBASE-7191 > URL: https://issues.apache.org/jira/browse/HBASE-7191 > Project: HBase > Issue Type: Improvement > Components: hbck >Affects Versions: 0.94.1 >Reporter: Enis Soztutar >Priority: Major > Attachments: 7191-2.patch, hbck1-1.4-v1.patch > > > One of our clients run into a problem, in which they have the hbase.root.dir, > and cluster data, but their hbase.id and hbase.version files are corrupted. > HMaster creates those on start, but not if there is already existing data. > We can add smt like --fixIdFile, and ability for HBCK to do some offline > repairs for the version file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-7191) HBCK - Add offline create/fix hbase.version and hbase.id
[ https://issues.apache.org/jira/browse/HBASE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xufeng updated HBASE-7191: -- Comment: was deleted (was: please help me to review the patch,thanks. the patch created base on 1.4 branch. ) > HBCK - Add offline create/fix hbase.version and hbase.id > - > > Key: HBASE-7191 > URL: https://issues.apache.org/jira/browse/HBASE-7191 > Project: HBase > Issue Type: Improvement > Components: hbck >Affects Versions: 0.94.1 >Reporter: Enis Soztutar >Priority: Major > Attachments: 7191-2.patch, hbck1-1.4-v1.patch > > > One of our clients run into a problem, in which they have the hbase.root.dir, > and cluster data, but their hbase.id and hbase.version files are corrupted. > HMaster creates those on start, but not if there is already existing data. > We can add smt like --fixIdFile, and ability for HBCK to do some offline > repairs for the version file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-7191) HBCK - Add offline create/fix hbase.version and hbase.id
[ https://issues.apache.org/jira/browse/HBASE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747391#comment-16747391 ] xufeng commented on HBASE-7191: --- please help me to review the patch,thanks. the patch created base on 1.4 branch. > HBCK - Add offline create/fix hbase.version and hbase.id > - > > Key: HBASE-7191 > URL: https://issues.apache.org/jira/browse/HBASE-7191 > Project: HBase > Issue Type: Improvement > Components: hbck >Affects Versions: 0.94.1 >Reporter: Enis Soztutar >Priority: Major > Attachments: 7191-2.patch, hbck1-1.4-v1.patch > > > One of our clients run into a problem, in which they have the hbase.root.dir, > and cluster data, but their hbase.id and hbase.version files are corrupted. > HMaster creates those on start, but not if there is already existing data. > We can add smt like --fixIdFile, and ability for HBCK to do some offline > repairs for the version file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-7191) HBCK - Add offline create/fix hbase.version and hbase.id
[ https://issues.apache.org/jira/browse/HBASE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747390#comment-16747390 ] xufeng commented on HBASE-7191: --- please help me to review the patch,thanks. the patch created base on 1.4 branch. > HBCK - Add offline create/fix hbase.version and hbase.id > - > > Key: HBASE-7191 > URL: https://issues.apache.org/jira/browse/HBASE-7191 > Project: HBase > Issue Type: Improvement > Components: hbck >Affects Versions: 0.94.1 >Reporter: Enis Soztutar >Priority: Major > Attachments: 7191-2.patch, hbck1-1.4-v1.patch > > > One of our clients run into a problem, in which they have the hbase.root.dir, > and cluster data, but their hbase.id and hbase.version files are corrupted. > HMaster creates those on start, but not if there is already existing data. > We can add smt like --fixIdFile, and ability for HBCK to do some offline > repairs for the version file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-7191) HBCK - Add offline create/fix hbase.version and hbase.id
[ https://issues.apache.org/jira/browse/HBASE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xufeng updated HBASE-7191: -- Attachment: hbck1-1.4-v1.patch > HBCK - Add offline create/fix hbase.version and hbase.id > - > > Key: HBASE-7191 > URL: https://issues.apache.org/jira/browse/HBASE-7191 > Project: HBase > Issue Type: Improvement > Components: hbck >Affects Versions: 0.94.1 >Reporter: Enis Soztutar >Priority: Major > Attachments: 7191-2.patch, hbck1-1.4-v1.patch > > > One of our clients run into a problem, in which they have the hbase.root.dir, > and cluster data, but their hbase.id and hbase.version files are corrupted. > HMaster creates those on start, but not if there is already existing data. > We can add smt like --fixIdFile, and ability for HBCK to do some offline > repairs for the version file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-7191) HBCK - Add offline create/fix hbase.version and hbase.id
[ https://issues.apache.org/jira/browse/HBASE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746933#comment-16746933 ] xufeng commented on HBASE-7191: --- hi, I made a patch for hbck1 base on 1.4 branch. where is the upload button :( > HBCK - Add offline create/fix hbase.version and hbase.id > - > > Key: HBASE-7191 > URL: https://issues.apache.org/jira/browse/HBASE-7191 > Project: HBase > Issue Type: Improvement > Components: hbck >Affects Versions: 0.94.1 >Reporter: Enis Soztutar >Priority: Major > Attachments: 7191-2.patch > > > One of our clients run into a problem, in which they have the hbase.root.dir, > and cluster data, but their hbase.id and hbase.version files are corrupted. > HMaster creates those on start, but not if there is already existing data. > We can add smt like --fixIdFile, and ability for HBCK to do some offline > repairs for the version file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (HBASE-7191) HBCK - Add offline create/fix hbase.version and hbase.id
[ https://issues.apache.org/jira/browse/HBASE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xufeng updated HBASE-7191: -- Comment: was deleted (was: hi, I made a patch for hbck1 base on 1.4 branch. anyone can review it? thanks :)) > HBCK - Add offline create/fix hbase.version and hbase.id > - > > Key: HBASE-7191 > URL: https://issues.apache.org/jira/browse/HBASE-7191 > Project: HBase > Issue Type: Improvement > Components: hbck >Affects Versions: 0.94.1 >Reporter: Enis Soztutar >Priority: Major > Attachments: 7191-2.patch > > > One of our clients run into a problem, in which they have the hbase.root.dir, > and cluster data, but their hbase.id and hbase.version files are corrupted. > HMaster creates those on start, but not if there is already existing data. > We can add smt like --fixIdFile, and ability for HBCK to do some offline > repairs for the version file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-7191) HBCK - Add offline create/fix hbase.version and hbase.id
[ https://issues.apache.org/jira/browse/HBASE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746932#comment-16746932 ] xufeng commented on HBASE-7191: --- hi, I made a patch for hbck1 base on 1.4 branch. anyone can review it? thanks :) > HBCK - Add offline create/fix hbase.version and hbase.id > - > > Key: HBASE-7191 > URL: https://issues.apache.org/jira/browse/HBASE-7191 > Project: HBase > Issue Type: Improvement > Components: hbck >Affects Versions: 0.94.1 >Reporter: Enis Soztutar >Priority: Major > Attachments: 7191-2.patch > > > One of our clients run into a problem, in which they have the hbase.root.dir, > and cluster data, but their hbase.id and hbase.version files are corrupted. > HMaster creates those on start, but not if there is already existing data. > We can add smt like --fixIdFile, and ability for HBCK to do some offline > repairs for the version file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-7191) HBCK - Add offline create/fix hbase.version and hbase.id
[ https://issues.apache.org/jira/browse/HBASE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739204#comment-16739204 ] xufeng commented on HBASE-7191: --- ok,I will try to do it :) > HBCK - Add offline create/fix hbase.version and hbase.id > - > > Key: HBASE-7191 > URL: https://issues.apache.org/jira/browse/HBASE-7191 > Project: HBase > Issue Type: Improvement > Components: hbck >Affects Versions: 0.94.1 >Reporter: Enis Soztutar >Priority: Major > Attachments: 7191-2.patch > > > One of our clients run into a problem, in which they have the hbase.root.dir, > and cluster data, but their hbase.id and hbase.version files are corrupted. > HMaster creates those on start, but not if there is already existing data. > We can add smt like --fixIdFile, and ability for HBCK to do some offline > repairs for the version file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-7191) HBCK - Add offline create/fix hbase.version and hbase.id
[ https://issues.apache.org/jira/browse/HBASE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737947#comment-16737947 ] xufeng commented on HBASE-7191: --- Can we move the connect() method to the position after offlineHdfsIntegrityRepair() method? > HBCK - Add offline create/fix hbase.version and hbase.id > - > > Key: HBASE-7191 > URL: https://issues.apache.org/jira/browse/HBASE-7191 > Project: HBase > Issue Type: Improvement > Components: hbck >Affects Versions: 0.94.1 >Reporter: Enis Soztutar >Priority: Major > Attachments: 7191-2.patch > > > One of our clients run into a problem, in which they have the hbase.root.dir, > and cluster data, but their hbase.id and hbase.version files are corrupted. > HMaster creates those on start, but not if there is already existing data. > We can add smt like --fixIdFile, and ability for HBCK to do some offline > repairs for the version file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-7191) HBCK - Add offline create/fix hbase.version and hbase.id
[ https://issues.apache.org/jira/browse/HBASE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737931#comment-16737931 ] xufeng commented on HBASE-7191: --- anybody here? I encounter this issue. hbase hbck can not repair offline hdfs problem. hbase failed to start because there is no version file on hdfs. try to do "hbase hbck -fixVersionFile"，but the tool will connect master, so failed. anyone can help me？ thank you。 > HBCK - Add offline create/fix hbase.version and hbase.id > - > > Key: HBASE-7191 > URL: https://issues.apache.org/jira/browse/HBASE-7191 > Project: HBase > Issue Type: Improvement > Components: hbck >Affects Versions: 0.94.1 >Reporter: Enis Soztutar >Priority: Major > Attachments: 7191-2.patch > > > One of our clients run into a problem, in which they have the hbase.root.dir, > and cluster data, but their hbase.id and hbase.version files are corrupted. > HMaster creates those on start, but not if there is already existing data. > We can add smt like --fixIdFile, and ability for HBCK to do some offline > repairs for the version file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-5828) TestLogRolling fails in 0.90 branch killing the test suite up on jenkins
[
https://issues.apache.org/jira/browse/HBASE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xufeng updated HBASE-5828:
--
Attachment: HBASE-5828_90_v1_100times_test_result.txt
HBASE-5828_90_v1.patch
I create a patch and run this patch 100 times by shell.
{noformat}
for((i=1;i=100;i++));
do
mvn clean -Dtest=TestLogRolling test
HBASE-5828_90_v1_100times_test_result.txt
mv target target_${i}
done
{noformat}
2 times（64th 75th）failed,I do not why happened now.
{noformat}
---
Test set: org.apache.hadoop.hbase.regionserver.wal.TestLogRolling
---
Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1,219.296 sec
FAILURE!
testLogRollOnPipelineRestart(org.apache.hadoop.hbase.regionserver.wal.TestLogRolling)
Time elapsed: 952.159 sec ERROR!
org.apache.hadoop.hbase.regionserver.wal.FailedLogCloseException: #1336683442040
at
org.apache.hadoop.hbase.regionserver.wal.HLog.cleanupCurrentWriter(HLog.java:802)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.rollWriter(HLog.java:560)
at
org.apache.hadoop.hbase.regionserver.wal.TestLogRolling.testLogRollOnPipelineRestart(TestLogRolling.java:476)
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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:165)
at org.apache.maven.surefire.Surefire.run(Surefire.java:107)
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.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:289)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1005)
Caused by: java.io.IOException: Error Recovery for block
blk_1933341499089292179_1016 failed because recovery from primary datanode
127.0.0.1:50920 failed 6 times. Pipeline was 127.0.0.1:50920. Aborting...
at
org.apache.hadoop.hdfs.DFSClient$DFSOutputStream.processDatanodeError(DFSClient.java:2741)
at
org.apache.hadoop.hdfs.DFSClient$DFSOutputStream.access$1500(DFSClient.java:2172)
at
org.apache.hadoop.hdfs.DFSClient$DFSOutputStream$DataStreamer.run(DFSClient.java:2371)
{noformat}
{noformat}
---
Test set: org.apache.hadoop.hbase.regionserver.wal.TestLogRolling
---
Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1,065.652 sec
FAILURE!
testLogRollOnPipelineRestart(org.apache.hadoop.hbase.regionserver.wal.TestLogRolling)
Time elapsed: 830.246 sec ERROR!
org.apache.hadoop.hbase.DroppedSnapshotException: region:
TestLogRolling,,1336675047757.bfce863e5843952e14649dc6fc8a53dd.
at
[jira] [Commented] (HBASE-5828) TestLogRolling fails in 0.90 branch killing the test suite up on jenkins
[ https://issues.apache.org/jira/browse/HBASE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13271146#comment-13271146 ] xufeng commented on HBASE-5828: --- @Rama Do you think doing as in trunk adding @before and @after will solve this problem? I think yes.In @Before,It will create a new cluster,new datanodes,new pipeline. Because the way the pipeline is formed may not be in our control right? Yes, but in this problem testLogRollOnPipelineRestart kill the datanodes in pipeline,So I think that this is a testcase problem. TestLogRolling fails in 0.90 branch killing the test suite up on jenkins Key: HBASE-5828 URL: https://issues.apache.org/jira/browse/HBASE-5828 Project: HBase Issue Type: Bug Reporter: stack Assignee: xufeng Attachments: TestLogRolling.java, org.apache.hadoop.hbase.regionserver.wal.TestLogRolling-output.rar See recent 0.90 builds up on jenkins: https://builds.apache.org/view/G-L/view/HBase/job/hbase-0.90/471/console -- 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-5828) TestLogRolling fails in 0.90 branch killing the test suite up on jenkins
[ https://issues.apache.org/jira/browse/HBASE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13271175#comment-13271175 ] xufeng commented on HBASE-5828: --- @Rama In fact,I run this case many times. if the meta and user regions are in the same server, it will ok. TestLogRolling fails in 0.90 branch killing the test suite up on jenkins Key: HBASE-5828 URL: https://issues.apache.org/jira/browse/HBASE-5828 Project: HBase Issue Type: Bug Reporter: stack Assignee: xufeng Attachments: TestLogRolling.java, org.apache.hadoop.hbase.regionserver.wal.TestLogRolling-output.rar See recent 0.90 builds up on jenkins: https://builds.apache.org/view/G-L/view/HBase/job/hbase-0.90/471/console -- 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-5828) TestLogRolling fails in 0.90 branch killing the test suite up on jenkins
[ https://issues.apache.org/jira/browse/HBASE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13271404#comment-13271404 ] xufeng commented on HBASE-5828: --- If anyone have no doubts on this is a test case problem. I think we have two choice to fix this problem: 1.roll the log writer belongs to the RS that holding the meta region before testLogRollOnPipelineRestart#deleteTable() executed. 2.By @Before and @After tag to start the cluster for every @test. plz give me suggestion,thanks. TestLogRolling fails in 0.90 branch killing the test suite up on jenkins Key: HBASE-5828 URL: https://issues.apache.org/jira/browse/HBASE-5828 Project: HBase Issue Type: Bug Reporter: stack Assignee: xufeng Attachments: TestLogRolling.java, org.apache.hadoop.hbase.regionserver.wal.TestLogRolling-output.rar See recent 0.90 builds up on jenkins: https://builds.apache.org/view/G-L/view/HBase/job/hbase-0.90/471/console -- 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-5828) TestLogRolling fails in 0.90 branch killing the test suite up on jenkins
[ https://issues.apache.org/jira/browse/HBASE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13272046#comment-13272046 ] xufeng commented on HBASE-5828: --- Hi Anyone can give me suggestion? TestLogRolling fails in 0.90 branch killing the test suite up on jenkins Key: HBASE-5828 URL: https://issues.apache.org/jira/browse/HBASE-5828 Project: HBase Issue Type: Bug Reporter: stack Assignee: xufeng Attachments: TestLogRolling.java, org.apache.hadoop.hbase.regionserver.wal.TestLogRolling-output.rar See recent 0.90 builds up on jenkins: https://builds.apache.org/view/G-L/view/HBase/job/hbase-0.90/471/console -- 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-5828) TestLogRolling fails in 0.90 branch killing the test suite up on jenkins
[
https://issues.apache.org/jira/browse/HBASE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13271013#comment-13271013
]
xufeng commented on HBASE-5828:
---
My Conclusion:
The the log writer pipeline of meta regionserver has been destroyed by
testLogRollOnDatanodeDeath().
when operate the Hlog on meta regionserver it will failed.
I think this is not a bug just a test problem.Like the other versions,We scan
segregate the test cluster by @before and @after tag.
My My Analysis::
1.I check the log from
https://builds.apache.org/view/G-L/view/HBase/job/hbase-0.90/472/artifact/trunk/target/surefire-reports/org.apache.hadoop.hbase.regionserver.wal.TestLogRolling-output.txt
Found the meta region and user region be deployed on different RS.It may cause
the problem.
{noformat}
Line 226: 2012-04-15 09:19:11,325 INFO
[MASTER_OPEN_REGION-hemera.apache.org:45266-0]
handler.OpenedRegionHandler(137): The master has opened the region
-ROOT-,,0.70236052 that was online on
serverName=hemera.apache.org,46368,1334481545408, load=(requests=0, regions=0,
usedHeap=71, maxHeap=1244)
Line 288: 2012-04-15 09:19:11,379 INFO
[MASTER_OPEN_REGION-hemera.apache.org:45266-1]
handler.OpenedRegionHandler(137): The master has opened the region
.META.,,1.1028785192 that was online on
serverName=hemera.apache.org,46368,1334481545408, load=(requests=0, regions=0,
usedHeap=71, maxHeap=1244)
Line 504: 2012-04-15 09:19:21,513 DEBUG
[MASTER_OPEN_REGION-hemera.apache.org:45266-2]
handler.OpenedRegionHandler(139): The master has opened the region
TestLogRolling,,1334481561377.369bae2d9411e5836a17df5e31b07b5e. that was online
on serverName=hemera.apache.org,46368,1334481545408, load=(requests=0,
regions=2, usedHeap=76, maxHeap=1244)
Line 8652: 2012-04-15 09:20:09,099 DEBUG
[MASTER_OPEN_REGION-hemera.apache.org:45266-3]
handler.OpenedRegionHandler(139): The master has opened the region
TestLogRolling,,1334481609001.198321df4a9c90eebcf670a2218d29f0. that was online
on serverName=hemera.apache.org,34725,1334481545432, load=(requests=0,
regions=0, usedHeap=129, maxHeap=1244)
{noformat}
2.In this issue we should find in case where the problem happened.
I reproduce this issue again，this time I added the debug code in
testLogRollOnPipelineRestart().
if (admin.tableExists(tableName)) {
admin.disableTable(tableName);
+LOG.info(xufeng7before delete table!);
admin.deleteTable(tableName);
+LOG.info(xufeng7after delete table!);
}
3.The test be killed And I just found the before delete table! no after
delete table! string in log.
It can ensure that the prroblem happened in admin.deleteTable(tableName).
This is the region assigned info
{noformat}
Line 226: 2012-05-08 16:45:17,603 INFO
[MASTER_OPEN_REGION-HADOOP-CI-AGENT-A:42383-0]
handler.OpenedRegionHandler(137): The master has opened the region
-ROOT-,,0.70236052 that was online on
serverName=HADOOP-CI-AGENT-A,49991,1336466711048, load=(requests=0, regions=0,
usedHeap=49, maxHeap=1348)
Line 288: 2012-05-08 16:45:17,696 INFO
[MASTER_OPEN_REGION-HADOOP-CI-AGENT-A:42383-1]
handler.OpenedRegionHandler(137): The master has opened the region
.META.,,1.1028785192 that was online on
serverName=HADOOP-CI-AGENT-A,49991,1336466711048, load=(requests=0, regions=0,
usedHeap=49, maxHeap=1348)
Line 505: 2012-05-08 16:45:28,099 DEBUG
[MASTER_OPEN_REGION-HADOOP-CI-AGENT-A:42383-2]
handler.OpenedRegionHandler(139): The master has opened the region
TestLogRolling,,1336466727648.b119d8cad80bc39cdd38b04421a67280. that was online
on serverName=HADOOP-CI-AGENT-A,57227,1336466711078, load=(requests=0,
regions=0, usedHeap=54, maxHeap=1348)
Line 8495: 2012-05-08 16:46:18,169 DEBUG
[MASTER_OPEN_REGION-HADOOP-CI-AGENT-A:42383-3]
handler.OpenedRegionHandler(139): The master has opened the region
TestLogRolling,,1336466777847.0117c81b3e59fdad15c4a4390156a558. that was online
on serverName=HADOOP-CI-AGENT-A,57227,1336466711078, load=(requests=0,
regions=0, usedHeap=68, maxHeap=1348)
{noformat}
This is my debug info:
{noformat}
Line 8526: 2012-05-08 16:46:28,138 INFO [main]
wal.TestLogRolling(339):
xufeng1cluster.getRegionServer(0)serverName=HADOOP-CI-AGENT-A,49991,1336466711048,
load=(requests=0, regions=2, usedHeap=72, maxHeap=1348)
Line 8527: 2012-05-08 16:46:28,138 INFO [main]
wal.TestLogRolling(344): xufeng1127.0.0.1:36932
Line 8528: 2012-05-08 16:46:28,138 INFO [main]
wal.TestLogRolling(345): xufeng1127.0.0.1:42887
Line 8529: 2012-05-08 16:46:28,138 INFO [main]
wal.TestLogRolling(351):
xufeng2cluster.getRegionServer(1)serverName=HADOOP-CI-AGENT-A,57227,1336466711078,
load=(requests=0, regions=1, usedHeap=72, maxHeap=1348)
Line 8530: 2012-05-08 16:46:28,138 INFO [main]
wal.TestLogRolling(356):
[jira] [Assigned] (HBASE-5828) TestLogRolling fails in 0.90 branch killing the test suite up on jenkins
[ https://issues.apache.org/jira/browse/HBASE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xufeng reassigned HBASE-5828: - Assignee: xufeng TestLogRolling fails in 0.90 branch killing the test suite up on jenkins Key: HBASE-5828 URL: https://issues.apache.org/jira/browse/HBASE-5828 Project: HBase Issue Type: Bug Reporter: stack Assignee: xufeng See recent 0.90 builds up on jenkins: https://builds.apache.org/view/G-L/view/HBase/job/hbase-0.90/471/console -- 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] [Updated] (HBASE-5828) TestLogRolling fails in 0.90 branch killing the test suite up on jenkins
[ https://issues.apache.org/jira/browse/HBASE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xufeng updated HBASE-5828: -- Attachment: TestLogRolling.java org.apache.hadoop.hbase.regionserver.wal.TestLogRolling-output.rar 1.The reproduce result. 2.The test file thar be added some debug code. TestLogRolling fails in 0.90 branch killing the test suite up on jenkins Key: HBASE-5828 URL: https://issues.apache.org/jira/browse/HBASE-5828 Project: HBase Issue Type: Bug Reporter: stack Assignee: xufeng Attachments: TestLogRolling.java, org.apache.hadoop.hbase.regionserver.wal.TestLogRolling-output.rar See recent 0.90 builds up on jenkins: https://builds.apache.org/view/G-L/view/HBase/job/hbase-0.90/471/console -- 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-5828) TestLogRolling fails in 0.90 branch killing the test suite up on jenkins
[ https://issues.apache.org/jira/browse/HBASE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13269543#comment-13269543 ] xufeng commented on HBASE-5828: --- I just review the code and have a speculation about this issue: If the region of META table assigned on regionserver_A. The region of user table assigned on regionserver_B. At first,the pipeline of regionserver_A and regionserver_B have the same datanodes. The testcase testLogRollOnDatanodeDeath will kill the all datanodes in pipeline which belongs to the hlog writer of regionserver_B. When the testcase testLogRollOnPipelineRestart to deleteTale,it will update the META data. Because the datanodes in pipeline of regionserver_A have been stoped,So it will fail. Test will wait in HBaseAdmin#deletaTable() until retries exhausted. After long time this test will be killed. TestLogRolling fails in 0.90 branch killing the test suite up on jenkins Key: HBASE-5828 URL: https://issues.apache.org/jira/browse/HBASE-5828 Project: HBase Issue Type: Bug Reporter: stack See recent 0.90 builds up on jenkins: https://builds.apache.org/view/G-L/view/HBase/job/hbase-0.90/471/console -- 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-5828) TestLogRolling fails in 0.90 branch killing the test suite up on jenkins
[
https://issues.apache.org/jira/browse/HBASE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13270158#comment-13270158
]
xufeng commented on HBASE-5828:
---
I added some debug log and reproduce it in my test env,I got the error that the
TestLogRolling be killed.
1.The region assignment info:
{noformat}
Line 227: 2012-05-08 10:33:46,705 INFO
[MASTER_OPEN_REGION-HADOOP-CI-AGENT-A:56223-0]
handler.OpenedRegionHandler(137): The master has opened the region
-ROOT-,,0.70236052 that was online on
serverName=HADOOP-CI-AGENT-A,36476,133620154, load=(requests=0, regions=0,
usedHeap=49, maxHeap=1348)
Line 288: 2012-05-08 10:33:46,797 INFO
[MASTER_OPEN_REGION-HADOOP-CI-AGENT-A:56223-1]
handler.OpenedRegionHandler(137): The master has opened the region
.META.,,1.1028785192 that was online on
serverName=HADOOP-CI-AGENT-A,36476,133620154, load=(requests=0, regions=0,
usedHeap=49, maxHeap=1348)
Line 505: 2012-05-08 10:33:57,224 DEBUG
[MASTER_OPEN_REGION-HADOOP-CI-AGENT-A:56223-2]
handler.OpenedRegionHandler(139): The master has opened the region
TestLogRolling,,133636745.7365edcbf8a8a078ce2c04f08a08e021. that was online
on serverName=HADOOP-CI-AGENT-A,59995,133620124, load=(requests=0,
regions=0, usedHeap=50, maxHeap=1348)
Line 8497: 2012-05-08 10:34:47,678 DEBUG
[MASTER_OPEN_REGION-HADOOP-CI-AGENT-A:56223-3]
handler.OpenedRegionHandler(139): The master has opened the region
TestLogRolling,,133687331.d0ba082226efdac56a16272b51d1147d. that was online
on serverName=HADOOP-CI-AGENT-A,59995,133620124, load=(requests=0,
regions=0, usedHeap=51, maxHeap=1348)
{noformat}
2.The piple line info,ensure the datanodes in pipeline of the rs that holding
the meta region did not change,it will cause the problem.
{noformat}
Line 8528: 2012-05-08 10:34:57,648 INFO [main]
wal.TestLogRolling(339):
xufeng1cluster.getRegionServer(0)serverName=HADOOP-CI-AGENT-A,59995,133620124,
load=(requests=0, regions=1, usedHeap=50, maxHeap=1348)
Line 8529: 2012-05-08 10:34:57,648 INFO [main]
wal.TestLogRolling(344): xufeng1127.0.0.1:47107
Line 8530: 2012-05-08 10:34:57,648 INFO [main]
wal.TestLogRolling(345): xufeng1127.0.0.1:33211
Line 8531: 2012-05-08 10:34:57,648 INFO [main]
wal.TestLogRolling(351):
xufeng2cluster.getRegionServer(1)serverName=HADOOP-CI-AGENT-A,36476,133620154,
load=(requests=0, regions=2, usedHeap=50, maxHeap=1348)
Line 8532: 2012-05-08 10:34:57,648 INFO [main]
wal.TestLogRolling(356): xufeng2127.0.0.1:33211
Line 8533: 2012-05-08 10:34:57,649 INFO [main]
wal.TestLogRolling(357): xufeng2127.0.0.1:47107
Line 9536: 2012-05-08 10:35:35,470 INFO [main]
wal.TestLogRolling(420):
xufeng3cluster.getRegionServer(0)serverName=HADOOP-CI-AGENT-A,59995,133620124,
load=(requests=9, regions=1, usedHeap=49, maxHeap=1348)
Line 9537: 2012-05-08 10:35:35,470 INFO [main]
wal.TestLogRolling(425): xufeng3127.0.0.1:43393
Line 9538: 2012-05-08 10:35:35,471 INFO [main]
wal.TestLogRolling(426): xufeng3127.0.0.1:41380
Line 9723: 2012-05-08 10:35:36,440 INFO [main]
wal.TestLogRolling(432):
xufeng4cluster.getRegionServer(1)serverName=HADOOP-CI-AGENT-A,36476,133620154,
load=(requests=0, regions=2, usedHeap=52, maxHeap=1348)
Line 9724: 2012-05-08 10:35:36,440 INFO [main]
wal.TestLogRolling(437): xufeng4127.0.0.1:33211
Line 9725: 2012-05-08 10:35:36,440 INFO [main]
wal.TestLogRolling(438): xufeng4127.0.0.1:47107
Line 9729: 2012-05-08 10:35:36,442 INFO [main]
wal.TestLogRolling(468):
xufeng5cluster.getRegionServer(0)serverName=HADOOP-CI-AGENT-A,59995,133620124,
load=(requests=9, regions=1, usedHeap=49, maxHeap=1348)
Line 9730: 2012-05-08 10:35:36,442 INFO [main]
wal.TestLogRolling(473): xufeng5127.0.0.1:43393
Line 9731: 2012-05-08 10:35:36,442 INFO [main]
wal.TestLogRolling(474): xufeng5127.0.0.1:41380
Line 9732: 2012-05-08 10:35:36,443 INFO [main]
wal.TestLogRolling(480):
xufeng6cluster.getRegionServer(1)serverName=HADOOP-CI-AGENT-A,36476,133620154,
load=(requests=0, regions=2, usedHeap=52, maxHeap=1348)
Line 9733: 2012-05-08 10:35:36,443 INFO [main]
wal.TestLogRolling(485): xufeng6127.0.0.1:33211
Line 9734: 2012-05-08 10:35:36,443 INFO [main]
wal.TestLogRolling(486): xufeng6127.0.0.1:47107
{noformat}
TestLogRolling fails in 0.90 branch killing the test suite up on jenkins
Key: HBASE-5828
URL: https://issues.apache.org/jira/browse/HBASE-5828
Project: HBase
Issue Type: Bug
Reporter: stack
See
[jira] [Commented] (HBASE-5828) TestLogRolling fails in 0.90 branch killing the test suite up on jenkins
[ https://issues.apache.org/jira/browse/HBASE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13270160#comment-13270160 ] xufeng commented on HBASE-5828: --- Q:Why the oter versions have not this problem? A:Because by @before and @after tag,every case will have the absolute test cluster. TestLogRolling fails in 0.90 branch killing the test suite up on jenkins Key: HBASE-5828 URL: https://issues.apache.org/jira/browse/HBASE-5828 Project: HBase Issue Type: Bug Reporter: stack See recent 0.90 builds up on jenkins: https://builds.apache.org/view/G-L/view/HBase/job/hbase-0.90/471/console -- 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-5828) TestLogRolling fails in 0.90 branch killing the test suite up on jenkins
[ https://issues.apache.org/jira/browse/HBASE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13270163#comment-13270163 ] xufeng commented on HBASE-5828: --- I can not access https://builds.apache.org/view/G-L/view/HBase/job/hbase-0.90/471/console Is the problem same to what I meeted? TestLogRolling fails in 0.90 branch killing the test suite up on jenkins Key: HBASE-5828 URL: https://issues.apache.org/jira/browse/HBASE-5828 Project: HBase Issue Type: Bug Reporter: stack See recent 0.90 builds up on jenkins: https://builds.apache.org/view/G-L/view/HBase/job/hbase-0.90/471/console -- 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-5828) TestLogRolling fails in 0.90 branch killing the test suite up on jenkins
[ https://issues.apache.org/jira/browse/HBASE-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13270177#comment-13270177 ] xufeng commented on HBASE-5828: --- @Ted Where the log file I can get? TestLogRolling fails in 0.90 branch killing the test suite up on jenkins Key: HBASE-5828 URL: https://issues.apache.org/jira/browse/HBASE-5828 Project: HBase Issue Type: Bug Reporter: stack See recent 0.90 builds up on jenkins: https://builds.apache.org/view/G-L/view/HBase/job/hbase-0.90/471/console -- 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-5894) Delete table failed but HBaseAdmin#deletetable report it as success
[
https://issues.apache.org/jira/browse/HBASE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13268987#comment-13268987
]
xufeng commented on HBASE-5894:
---
@Ted
Which patch has this problem?
Delete table failed but HBaseAdmin#deletetable report it as success
---
Key: HBASE-5894
URL: https://issues.apache.org/jira/browse/HBASE-5894
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.7, 0.92.2, 0.94.0
Environment: all versions
Reporter: xufeng
Assignee: xufeng
Priority: Minor
Attachments: HBASE-5894_90_patch_v1.patch,
HBASE-5894_90_patch_v1_surefire-report.html, HBASE-5894_92_patch_v1.patch,
HBASE-5894_92_patch_v1_surefire-report.html, HBASE-5894_94_patch_v1.patch,
HBASE-5894_94_patch_v1_surefire-report.html, HBASE-5894_trunk_patch_v1.patch,
HBASE-5894_trunk_patch_v1_surefire-report.html,
HBASE-5894_trunk_patch_v2.patch,
HBASE-5894_trunk_patch_v2_surefire-report.html
Reproduce this issue by following steps:
For reproduce it I add this code in DeleteTableHandler#handleTableOperation():
{noformat}
LOG.debug(Deleting region + region.getRegionNameAsString() +
from META and FS);
+if (true) {
+ throw new IOException(ERROR);
+}
// Remove region from META
MetaEditor.deleteRegion(this.server.getCatalogTracker(), region);
{noformat}
step1:create a table and disable it.
step2:delete it by HBaseAdmin#deleteTable() API.
result:after lone time, The log say the Table has been deleted, but in fact
if we do list in shell,the table also exists.
--
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] [Updated] (HBASE-5894) Delete table failed but HBaseAdmin#deletetable report it as success
[
https://issues.apache.org/jira/browse/HBASE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xufeng updated HBASE-5894:
--
Attachment: HBASE-5894_trunk_patch_v3.patch
Delete table failed but HBaseAdmin#deletetable report it as success
---
Key: HBASE-5894
URL: https://issues.apache.org/jira/browse/HBASE-5894
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.7, 0.92.2, 0.94.0
Environment: all versions
Reporter: xufeng
Assignee: xufeng
Priority: Minor
Attachments: HBASE-5894_90_patch_v1.patch,
HBASE-5894_90_patch_v1_surefire-report.html, HBASE-5894_92_patch_v1.patch,
HBASE-5894_92_patch_v1_surefire-report.html, HBASE-5894_94_patch_v1.patch,
HBASE-5894_94_patch_v1_surefire-report.html, HBASE-5894_trunk_patch_v1.patch,
HBASE-5894_trunk_patch_v1_surefire-report.html,
HBASE-5894_trunk_patch_v2.patch,
HBASE-5894_trunk_patch_v2_surefire-report.html,
HBASE-5894_trunk_patch_v3.patch
Reproduce this issue by following steps:
For reproduce it I add this code in DeleteTableHandler#handleTableOperation():
{noformat}
LOG.debug(Deleting region + region.getRegionNameAsString() +
from META and FS);
+if (true) {
+ throw new IOException(ERROR);
+}
// Remove region from META
MetaEditor.deleteRegion(this.server.getCatalogTracker(), region);
{noformat}
step1:create a table and disable it.
step2:delete it by HBaseAdmin#deleteTable() API.
result:after lone time, The log say the Table has been deleted, but in fact
if we do list in shell,the table also exists.
--
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] [Updated] (HBASE-5894) Delete table failed but HBaseAdmin#deletetable report it as success
[
https://issues.apache.org/jira/browse/HBASE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xufeng updated HBASE-5894:
--
Attachment: HBASE-5894_94_patch_v2.patch
HBASE-5894_90_patch_v2.patch
HBASE-5894_92_patch_v2.patch
@Ted
I also updated the others.
Maybe the patch created by eclipse has this problem.
Now I create the patch by TortoiseSVN.
Delete table failed but HBaseAdmin#deletetable report it as success
---
Key: HBASE-5894
URL: https://issues.apache.org/jira/browse/HBASE-5894
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.7, 0.92.2, 0.94.0
Environment: all versions
Reporter: xufeng
Assignee: xufeng
Priority: Minor
Attachments: HBASE-5894_90_patch_v1.patch,
HBASE-5894_90_patch_v1_surefire-report.html, HBASE-5894_90_patch_v2.patch,
HBASE-5894_92_patch_v1.patch, HBASE-5894_92_patch_v1_surefire-report.html,
HBASE-5894_92_patch_v2.patch, HBASE-5894_94_patch_v1.patch,
HBASE-5894_94_patch_v1_surefire-report.html, HBASE-5894_94_patch_v2.patch,
HBASE-5894_trunk_patch_v1.patch,
HBASE-5894_trunk_patch_v1_surefire-report.html,
HBASE-5894_trunk_patch_v2.patch,
HBASE-5894_trunk_patch_v2_surefire-report.html,
HBASE-5894_trunk_patch_v3.patch
Reproduce this issue by following steps:
For reproduce it I add this code in DeleteTableHandler#handleTableOperation():
{noformat}
LOG.debug(Deleting region + region.getRegionNameAsString() +
from META and FS);
+if (true) {
+ throw new IOException(ERROR);
+}
// Remove region from META
MetaEditor.deleteRegion(this.server.getCatalogTracker(), region);
{noformat}
step1:create a table and disable it.
step2:delete it by HBaseAdmin#deleteTable() API.
result:after lone time, The log say the Table has been deleted, but in fact
if we do list in shell,the table also exists.
--
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-5894) Table deletion failed but HBaseAdmin#deletetable reports it as success
[
https://issues.apache.org/jira/browse/HBASE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13269108#comment-13269108
]
xufeng commented on HBASE-5894:
---
Ted and Stack
Thanks for your help.
Table deletion failed but HBaseAdmin#deletetable reports it as success
--
Key: HBASE-5894
URL: https://issues.apache.org/jira/browse/HBASE-5894
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.7, 0.92.2, 0.94.0
Environment: all versions
Reporter: xufeng
Assignee: xufeng
Priority: Minor
Fix For: 0.90.7, 0.92.2, 0.96.0, 0.94.1
Attachments: HBASE-5894_90_patch_v1.patch,
HBASE-5894_90_patch_v1_surefire-report.html, HBASE-5894_90_patch_v2.patch,
HBASE-5894_92_patch_v1.patch, HBASE-5894_92_patch_v1_surefire-report.html,
HBASE-5894_92_patch_v2.patch, HBASE-5894_94_patch_v1.patch,
HBASE-5894_94_patch_v1_surefire-report.html, HBASE-5894_94_patch_v2.patch,
HBASE-5894_trunk_patch_v1.patch,
HBASE-5894_trunk_patch_v1_surefire-report.html,
HBASE-5894_trunk_patch_v2.patch,
HBASE-5894_trunk_patch_v2_surefire-report.html,
HBASE-5894_trunk_patch_v3.patch
Reproduce this issue by following steps:
For reproduce it I add this code in DeleteTableHandler#handleTableOperation():
{noformat}
LOG.debug(Deleting region + region.getRegionNameAsString() +
from META and FS);
+if (true) {
+ throw new IOException(ERROR);
+}
// Remove region from META
MetaEditor.deleteRegion(this.server.getCatalogTracker(), region);
{noformat}
step1:create a table and disable it.
step2:delete it by HBaseAdmin#deleteTable() API.
result:after lone time, The log say the Table has been deleted, but in fact
if we do list in shell,the table also exists.
--
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-5894) Delete table failed but HBaseAdmin#deletetable report it as success
[
https://issues.apache.org/jira/browse/HBASE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13267993#comment-13267993
]
xufeng commented on HBASE-5894:
---
Hi
Anyone can review it and give me some suggestion?
Delete table failed but HBaseAdmin#deletetable report it as success
---
Key: HBASE-5894
URL: https://issues.apache.org/jira/browse/HBASE-5894
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.7, 0.92.2, 0.94.0
Environment: all versions
Reporter: xufeng
Assignee: xufeng
Priority: Minor
Attachments: HBASE-5894_90_patch_v1.patch,
HBASE-5894_90_patch_v1_surefire-report.html, HBASE-5894_92_patch_v1.patch,
HBASE-5894_92_patch_v1_surefire-report.html, HBASE-5894_94_patch_v1.patch,
HBASE-5894_94_patch_v1_surefire-report.html, HBASE-5894_trunk_patch_v1.patch,
HBASE-5894_trunk_patch_v1_surefire-report.html,
HBASE-5894_trunk_patch_v2.patch,
HBASE-5894_trunk_patch_v2_surefire-report.html
Reproduce this issue by following steps:
For reproduce it I add this code in DeleteTableHandler#handleTableOperation():
{noformat}
LOG.debug(Deleting region + region.getRegionNameAsString() +
from META and FS);
+if (true) {
+ throw new IOException(ERROR);
+}
// Remove region from META
MetaEditor.deleteRegion(this.server.getCatalogTracker(), region);
{noformat}
step1:create a table and disable it.
step2:delete it by HBaseAdmin#deleteTable() API.
result:after lone time, The log say the Table has been deleted, but in fact
if we do list in shell,the table also exists.
--
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] [Updated] (HBASE-5894) Delete table failed but HBaseAdmin#deletetable report it as success
[
https://issues.apache.org/jira/browse/HBASE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xufeng updated HBASE-5894:
--
Attachment: HBASE-5894_trunk_patch_v2_surefire-report.html
HBASE-5894_94_patch_v1_surefire-report.html
HBASE-5894_92_patch_v1_surefire-report.html
HBASE-5894_90_patch_v1_surefire-report.html
HBASE-5894_trunk_patch_v2.patch
HBASE-5894_94_patch_v1.patch
HBASE-5894_92_patch_v1.patch
HBASE-5894_90_patch_v1.patch
@Ted
I have updated the trunk patch and created patch of the other versions,please
review,thanks.
All patch verified in real cluster by my reproduce steps.
Delete table failed but HBaseAdmin#deletetable report it as success
---
Key: HBASE-5894
URL: https://issues.apache.org/jira/browse/HBASE-5894
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.7, 0.92.2, 0.94.0
Environment: all versions
Reporter: xufeng
Assignee: xufeng
Priority: Minor
Attachments: HBASE-5894_90_patch_v1.patch,
HBASE-5894_90_patch_v1_surefire-report.html, HBASE-5894_92_patch_v1.patch,
HBASE-5894_92_patch_v1_surefire-report.html, HBASE-5894_94_patch_v1.patch,
HBASE-5894_94_patch_v1_surefire-report.html, HBASE-5894_trunk_patch_v1.patch,
HBASE-5894_trunk_patch_v1_surefire-report.html,
HBASE-5894_trunk_patch_v2.patch,
HBASE-5894_trunk_patch_v2_surefire-report.html
Reproduce this issue by following steps:
For reproduce it I add this code in DeleteTableHandler#handleTableOperation():
{noformat}
LOG.debug(Deleting region + region.getRegionNameAsString() +
from META and FS);
+if (true) {
+ throw new IOException(ERROR);
+}
// Remove region from META
MetaEditor.deleteRegion(this.server.getCatalogTracker(), region);
{noformat}
step1:create a table and disable it.
step2:delete it by HBaseAdmin#deleteTable() API.
result:after lone time, The log say the Table has been deleted, but in fact
if we do list in shell,the table also exists.
--
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-5894) Delete table failed but HBaseAdmin#deletetable report it as success
[
https://issues.apache.org/jira/browse/HBASE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13266545#comment-13266545
]
xufeng commented on HBASE-5894:
---
@Ted
If a test can be added to verify the fix, that would be nice.
In fact,I found this issue in TestLogRolling in 90 version.
One day the test be killed,I tracked it and found that it timeout in
deleteTable() becauseof the dfs problem.
I think that it is hard to add the new test to verify the fix,because it will
cost long time, the test will be killed or timeout(if we add @Test(timeout =
12)).
Maybe I am wrong,Can you suggest to me?
Delete table failed but HBaseAdmin#deletetable report it as success
---
Key: HBASE-5894
URL: https://issues.apache.org/jira/browse/HBASE-5894
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.7, 0.92.2, 0.94.0
Environment: all versions
Reporter: xufeng
Assignee: xufeng
Priority: Minor
Attachments: HBASE-5894_90_patch_v1.patch,
HBASE-5894_90_patch_v1_surefire-report.html, HBASE-5894_92_patch_v1.patch,
HBASE-5894_92_patch_v1_surefire-report.html, HBASE-5894_94_patch_v1.patch,
HBASE-5894_94_patch_v1_surefire-report.html, HBASE-5894_trunk_patch_v1.patch,
HBASE-5894_trunk_patch_v1_surefire-report.html,
HBASE-5894_trunk_patch_v2.patch,
HBASE-5894_trunk_patch_v2_surefire-report.html
Reproduce this issue by following steps:
For reproduce it I add this code in DeleteTableHandler#handleTableOperation():
{noformat}
LOG.debug(Deleting region + region.getRegionNameAsString() +
from META and FS);
+if (true) {
+ throw new IOException(ERROR);
+}
// Remove region from META
MetaEditor.deleteRegion(this.server.getCatalogTracker(), region);
{noformat}
step1:create a table and disable it.
step2:delete it by HBaseAdmin#deleteTable() API.
result:after lone time, The log say the Table has been deleted, but in fact
if we do list in shell,the table also exists.
--
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] [Created] (HBASE-5894) Delete table failed but HBaseAdmin#deletetable report it as success
xufeng created HBASE-5894:
-
Summary: Delete table failed but HBaseAdmin#deletetable report it
as success
Key: HBASE-5894
URL: https://issues.apache.org/jira/browse/HBASE-5894
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.7, 0.92.2, 0.94.0
Environment: all versions
Reporter: xufeng
Assignee: xufeng
Priority: Minor
Reproduce this issue by following steps:
For reproduce it I add this code in DeleteTableHandler#handleTableOperation():
{noformat}
LOG.debug(Deleting region + region.getRegionNameAsString() +
from META and FS);
+if (true) {
+ throw new IOException(ERROR);
+}
// Remove region from META
MetaEditor.deleteRegion(this.server.getCatalogTracker(), region);
{noformat}
step1:create a table and disable it.
step2:delete it by HBaseAdmin#deleteTable() API.
result:after lone time, The log say the Table has been deleted, but in fact if
we do list in shell,the table also exists.
--
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-5894) Delete table failed but HBaseAdmin#deletetable report it as success
[
https://issues.apache.org/jira/browse/HBASE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13264250#comment-13264250
]
xufeng commented on HBASE-5894:
---
I review the code and ensure that all versions have this problem.
Delete table failed but HBaseAdmin#deletetable report it as success
---
Key: HBASE-5894
URL: https://issues.apache.org/jira/browse/HBASE-5894
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.7, 0.92.2, 0.94.0
Environment: all versions
Reporter: xufeng
Assignee: xufeng
Priority: Minor
Reproduce this issue by following steps:
For reproduce it I add this code in DeleteTableHandler#handleTableOperation():
{noformat}
LOG.debug(Deleting region + region.getRegionNameAsString() +
from META and FS);
+if (true) {
+ throw new IOException(ERROR);
+}
// Remove region from META
MetaEditor.deleteRegion(this.server.getCatalogTracker(), region);
{noformat}
step1:create a table and disable it.
step2:delete it by HBaseAdmin#deleteTable() API.
result:after lone time, The log say the Table has been deleted, but in fact
if we do list in shell,the table also exists.
--
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] [Updated] (HBASE-5894) Delete table failed but HBaseAdmin#deletetable report it as success
[
https://issues.apache.org/jira/browse/HBASE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xufeng updated HBASE-5894:
--
Attachment: HBASE-5894_trunk_patch_v1_surefire-report.html
HBASE-5894_trunk_patch_v1.patch
Patch for trunk and verified in real cluster.
I will submit the patch for 90,92 and 94 after verified in real cluster and
done the unit test.
Delete table failed but HBaseAdmin#deletetable report it as success
---
Key: HBASE-5894
URL: https://issues.apache.org/jira/browse/HBASE-5894
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.7, 0.92.2, 0.94.0
Environment: all versions
Reporter: xufeng
Assignee: xufeng
Priority: Minor
Attachments: HBASE-5894_trunk_patch_v1.patch,
HBASE-5894_trunk_patch_v1_surefire-report.html
Reproduce this issue by following steps:
For reproduce it I add this code in DeleteTableHandler#handleTableOperation():
{noformat}
LOG.debug(Deleting region + region.getRegionNameAsString() +
from META and FS);
+if (true) {
+ throw new IOException(ERROR);
+}
// Remove region from META
MetaEditor.deleteRegion(this.server.getCatalogTracker(), region);
{noformat}
step1:create a table and disable it.
step2:delete it by HBaseAdmin#deleteTable() API.
result:after lone time, The log say the Table has been deleted, but in fact
if we do list in shell,the table also exists.
--
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-5894) Delete table failed but HBaseAdmin#deletetable report it as success
[
https://issues.apache.org/jira/browse/HBASE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13264279#comment-13264279
]
xufeng commented on HBASE-5894:
---
Please review the patch and give me some suggestion,thanks.
Delete table failed but HBaseAdmin#deletetable report it as success
---
Key: HBASE-5894
URL: https://issues.apache.org/jira/browse/HBASE-5894
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.7, 0.92.2, 0.94.0
Environment: all versions
Reporter: xufeng
Assignee: xufeng
Priority: Minor
Attachments: HBASE-5894_trunk_patch_v1.patch,
HBASE-5894_trunk_patch_v1_surefire-report.html
Reproduce this issue by following steps:
For reproduce it I add this code in DeleteTableHandler#handleTableOperation():
{noformat}
LOG.debug(Deleting region + region.getRegionNameAsString() +
from META and FS);
+if (true) {
+ throw new IOException(ERROR);
+}
// Remove region from META
MetaEditor.deleteRegion(this.server.getCatalogTracker(), region);
{noformat}
step1:create a table and disable it.
step2:delete it by HBaseAdmin#deleteTable() API.
result:after lone time, The log say the Table has been deleted, but in fact
if we do list in shell,the table also exists.
--
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-5894) Delete table failed but HBaseAdmin#deletetable report it as success
[
https://issues.apache.org/jira/browse/HBASE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13264339#comment-13264339
]
xufeng commented on HBASE-5894:
---
@Ted
The for loop in HBaseAdmin#deleteTable() cost too long time.
In fact When I verified this patch,My client code spent 50 min until return.
In test,If one test cost more than 900s(the value of
forkedProcessTimeoutInSeconds defined in pom.xml)
then this test will be killed and the others also will not run,is it?
Delete table failed but HBaseAdmin#deletetable report it as success
---
Key: HBASE-5894
URL: https://issues.apache.org/jira/browse/HBASE-5894
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.7, 0.92.2, 0.94.0
Environment: all versions
Reporter: xufeng
Assignee: xufeng
Priority: Minor
Attachments: HBASE-5894_trunk_patch_v1.patch,
HBASE-5894_trunk_patch_v1_surefire-report.html
Reproduce this issue by following steps:
For reproduce it I add this code in DeleteTableHandler#handleTableOperation():
{noformat}
LOG.debug(Deleting region + region.getRegionNameAsString() +
from META and FS);
+if (true) {
+ throw new IOException(ERROR);
+}
// Remove region from META
MetaEditor.deleteRegion(this.server.getCatalogTracker(), region);
{noformat}
step1:create a table and disable it.
step2:delete it by HBaseAdmin#deleteTable() API.
result:after lone time, The log say the Table has been deleted, but in fact
if we do list in shell,the table also exists.
--
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-5850) Refuse operations from Admin before master is initialized - fix for all branches.
[ https://issues.apache.org/jira/browse/HBASE-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13260278#comment-13260278 ] xufeng commented on HBASE-5850: --- @stack @Ted @Lars Thanks for your help,Thanks. Refuse operations from Admin before master is initialized - fix for all branches. - Key: HBASE-5850 URL: https://issues.apache.org/jira/browse/HBASE-5850 Project: HBase Issue Type: Bug Reporter: xufeng Assignee: xufeng Fix For: 0.90.7, 0.92.2, 0.94.0 Attachments: 5850-trunk.txt, No_patch_90_surefire-report.html, backport-5454(createTable)-to-94.patch, backport-5454(createTable)-to-94_surefire-report.html, backport-5454(createTable)-to-trunk.patch, backport-5454(createTable)-to-trunk_surefire-report.html, backport-5454-to-90-surefire-report.html, backport-5454-to-90.patch, backport-5454-to-92.patch, backport-5454-to-92_surefire-report.html This issue is needed in 0.90 0.92 also. And update the hbase-5454 patch that add the checkInitialized() into HMaster#createTable(). -- 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] [Updated] (HBASE-5850) Backport HBASE-5454 to 90 and 92 Refuse operations from Admin before master is initialized
[ https://issues.apache.org/jira/browse/HBASE-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xufeng updated HBASE-5850: -- Attachment: backport-5454-to-90-surefire-report.html No_patch_90_surefire-report.html I try to merge the HBASE-5833 patch to 0.90 version,but failed. Many compile errors happend. So I delete the TestMasterFailover java file and test again. There are some error but also exist if no patch. I also check the TestMasterFailover file and I think it is no relation with the patch. Backport HBASE-5454 to 90 and 92 Refuse operations from Admin before master is initialized --- Key: HBASE-5850 URL: https://issues.apache.org/jira/browse/HBASE-5850 Project: HBase Issue Type: Bug Reporter: xufeng Assignee: xufeng Fix For: 0.90.7, 0.92.2, 0.94.1 Attachments: 5850-trunk.txt, No_patch_90_surefire-report.html, backport-5454(createTable)-to-94.patch, backport-5454(createTable)-to-94_surefire-report.html, backport-5454(createTable)-to-trunk.patch, backport-5454(createTable)-to-trunk_surefire-report.html, backport-5454-to-90-surefire-report.html, backport-5454-to-90.patch, backport-5454-to-92.patch, backport-5454-to-92_surefire-report.html This issue is needed in 0.90 0.92 also. And update the hbase-5454 patch that add the checkInitialized() into HMaster#createTable(). -- 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-5850) Backport HBASE-5454 to 90 and 92 Refuse operations from Admin before master is initialized
[ https://issues.apache.org/jira/browse/HBASE-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259008#comment-13259008 ] xufeng commented on HBASE-5850: --- @Lars I think we should add checkInitialized() to HMaster#createTable() in trunk and 0.94. So I created the patch for trunk and 0.94. Backport HBASE-5454 to 90 and 92 Refuse operations from Admin before master is initialized --- Key: HBASE-5850 URL: https://issues.apache.org/jira/browse/HBASE-5850 Project: HBase Issue Type: Bug Reporter: xufeng Assignee: xufeng Fix For: 0.90.7, 0.92.2 Attachments: backport-5454(createTable)-to-94.patch, backport-5454(createTable)-to-94_surefire-report.html, backport-5454(createTable)-to-trunk.patch, backport-5454(createTable)-to-trunk_surefire-report.html, backport-5454-to-90.patch, backport-5454-to-92.patch, backport-5454-to-92_surefire-report.html This issue is needed in 0.90 0.92 also. And update the hbase-5454 patch that add the checkInitialized() into HMaster#createTable(). -- 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-5850) Backport HBASE-5454 to 90 and 92 Refuse operations from Admin before master is initialized
[ https://issues.apache.org/jira/browse/HBASE-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259345#comment-13259345 ] xufeng commented on HBASE-5850: --- @Ted Backport HBASE-5454 to 90 and 92 Refuse operations from Admin before master is initialized --- Key: HBASE-5850 URL: https://issues.apache.org/jira/browse/HBASE-5850 Project: HBase Issue Type: Bug Reporter: xufeng Assignee: xufeng Fix For: 0.90.7, 0.92.2, 0.94.1 Attachments: 5850-trunk.txt, backport-5454(createTable)-to-94.patch, backport-5454(createTable)-to-94_surefire-report.html, backport-5454(createTable)-to-trunk.patch, backport-5454(createTable)-to-trunk_surefire-report.html, backport-5454-to-90.patch, backport-5454-to-92.patch, backport-5454-to-92_surefire-report.html This issue is needed in 0.90 0.92 also. And update the hbase-5454 patch that add the checkInitialized() into HMaster#createTable(). -- 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-5850) Backport HBASE-5454 to 90 and 92 Refuse operations from Admin before master is initialized
[
https://issues.apache.org/jira/browse/HBASE-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259346#comment-13259346
]
xufeng commented on HBASE-5850:
---
@Ted
I get the 90 version at revision 1329041 from
http://svn.apache.org/repos/asf/hbase/branches/0.90.
But this error also exist.
${noformat}
---
T E S T S
---
Running org.apache.hadoop.hbase.master.TestMasterFailover
killed.
${noformat}
Does this error also exist in your test env?
Backport HBASE-5454 to 90 and 92 Refuse operations from Admin before master
is initialized
---
Key: HBASE-5850
URL: https://issues.apache.org/jira/browse/HBASE-5850
Project: HBase
Issue Type: Bug
Reporter: xufeng
Assignee: xufeng
Fix For: 0.90.7, 0.92.2, 0.94.1
Attachments: 5850-trunk.txt, backport-5454(createTable)-to-94.patch,
backport-5454(createTable)-to-94_surefire-report.html,
backport-5454(createTable)-to-trunk.patch,
backport-5454(createTable)-to-trunk_surefire-report.html,
backport-5454-to-90.patch, backport-5454-to-92.patch,
backport-5454-to-92_surefire-report.html
This issue is needed in 0.90 0.92 also.
And update the hbase-5454 patch that add the checkInitialized() into
HMaster#createTable().
--
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] [Updated] (HBASE-5850) Backport HBASE-5454 to 90 and 92 Refuse operations from Admin before master is initialized
[ https://issues.apache.org/jira/browse/HBASE-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xufeng updated HBASE-5850: -- Fix Version/s: 0.94.0 0.92.2 0.90.7 Backport HBASE-5454 to 90 and 92 Refuse operations from Admin before master is initialized --- Key: HBASE-5850 URL: https://issues.apache.org/jira/browse/HBASE-5850 Project: HBase Issue Type: Bug Reporter: xufeng Assignee: xufeng Fix For: 0.90.7, 0.92.2, 0.94.0 Attachments: backport-5454(createTable)-to-94.patch, backport-5454(createTable)-to-94_surefire-report.html, backport-5454(createTable)-to-trunk.patch, backport-5454(createTable)-to-trunk_surefire-report.html, backport-5454-to-90.patch, backport-5454-to-92.patch, backport-5454-to-92_surefire-report.html This issue is needed in 0.90 0.92 also. And update the hbase-5454 patch that add the checkInitialized() into HMaster#createTable(). -- 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] [Created] (HBASE-5850) Backport HBASE-5454 to 90 and 92 Refuse operations from Admin before master is initialized
xufeng created HBASE-5850: - Summary: Backport HBASE-5454 to 90 and 92 Refuse operations from Admin before master is initialized Key: HBASE-5850 URL: https://issues.apache.org/jira/browse/HBASE-5850 Project: HBase Issue Type: Bug Reporter: xufeng Assignee: xufeng This issue is needed in 0.90 0.92 also. And update the hbase-5454 patch that add the checkInitialized() into HMaster#createTable(). -- 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-5677) The master never does balance because duplicate openhandled the one region
[ https://issues.apache.org/jira/browse/HBASE-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258774#comment-13258774 ] xufeng commented on HBASE-5677: --- @stack see https://issues.apache.org/jira/browse/HBASE-5850 The master never does balance because duplicate openhandled the one region -- Key: HBASE-5677 URL: https://issues.apache.org/jira/browse/HBASE-5677 Project: HBase Issue Type: Bug Affects Versions: 0.90.6 Environment: 0.90 Reporter: xufeng Assignee: xufeng Fix For: 0.90.7, 0.92.2 Attachments: 5677-proposal.txt, 5677-proposal.txt, Backport-HBASE-5454-to-90.patch, Backport-HBASE-5454-to-92.patch, HBASE-5677-90-v1.patch, surefire-report_no_patched_v1.html, surefire-report_patched_v1.html If region be assigned When the master is doing initialization(before do processFailover),the region will be duplicate openhandled. because the unassigned node in zookeeper will be handled again in AssignmentManager#processFailover() it cause the region in RIT,thus the master never does balance. -- 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] [Updated] (HBASE-5850) Backport HBASE-5454 to 90 and 92 Refuse operations from Admin before master is initialized
[
https://issues.apache.org/jira/browse/HBASE-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xufeng updated HBASE-5850:
--
Attachment: backport-5454-to-90.patch
backport-5454-to-92_surefire-report.html
backport-5454-to-92.patch
backport-5454(createTable)-to-94_surefire-report.html
backport-5454(createTable)-to-94.patch
backport-5454(createTable)-to-trunk_surefire-report.html
backport-5454(createTable)-to-trunk.patch
@stack
All patch have been verified in real cluster.
The error of unit test in trunk be verified I think it is no relation whit the
patch.
I did not submit the 90 test result,because I meeted this problem:
${noformat}
Running org.apache.hadoop.hbase.master.TestMasterFailover
killed.
${noformat}
This problem also exist if there is no the patch.
Backport HBASE-5454 to 90 and 92 Refuse operations from Admin before master
is initialized
---
Key: HBASE-5850
URL: https://issues.apache.org/jira/browse/HBASE-5850
Project: HBase
Issue Type: Bug
Reporter: xufeng
Assignee: xufeng
Attachments: backport-5454(createTable)-to-94.patch,
backport-5454(createTable)-to-94_surefire-report.html,
backport-5454(createTable)-to-trunk.patch,
backport-5454(createTable)-to-trunk_surefire-report.html,
backport-5454-to-90.patch, backport-5454-to-92.patch,
backport-5454-to-92_surefire-report.html
This issue is needed in 0.90 0.92 also.
And update the hbase-5454 patch that add the checkInitialized() into
HMaster#createTable().
--
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
