[jira] [Resolved] (HBASE-25186) TestMasterRegionOnTwoFileSystems is failing after HBASE-25065
[ https://issues.apache.org/jira/browse/HBASE-25186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-25186. --- Resolution: Fixed > TestMasterRegionOnTwoFileSystems is failing after HBASE-25065 > - > > Key: HBASE-25186 > URL: https://issues.apache.org/jira/browse/HBASE-25186 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 3.0.0-alpha-1, 2.4.0 >Reporter: ramkrishna.s.vasudevan >Assignee: Duo Zhang >Priority: Blocker > Fix For: 3.0.0-alpha-1, 2.4.0 > > > After HBASE-25065, we are having a test case failure with > TestMasterRegionOnTwoFileSystems. > The reason is that we manually trigger a WAL roll on the master region. As > part of the WAL roll we expect the Master region's WAL will also be moved > from region oldWAL dir to the global oldWAL directory. This happens after > afterRoll() method in AbstractWALRoller. > Since now the WAL archival is asynchronous the afterRoll() method does not > find any WAL file to be moved in the local region oldWAL dir. So the movement > to global oldWAL dir does not happen. > The test case checks for the file in the oldWAL dir and since it is not found > the test timesout. WE need a way to fix this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25186) TestMasterRegionOnTwoFileSystems is failing after HBASE-25065
[ https://issues.apache.org/jira/browse/HBASE-25186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-25186. --- Resolution: Fixed > TestMasterRegionOnTwoFileSystems is failing after HBASE-25065 > - > > Key: HBASE-25186 > URL: https://issues.apache.org/jira/browse/HBASE-25186 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 3.0.0-alpha-1, 2.4.0 >Reporter: ramkrishna.s.vasudevan >Assignee: Duo Zhang >Priority: Blocker > Fix For: 3.0.0-alpha-1, 2.4.0 > > > After HBASE-25065, we are having a test case failure with > TestMasterRegionOnTwoFileSystems. > The reason is that we manually trigger a WAL roll on the master region. As > part of the WAL roll we expect the Master region's WAL will also be moved > from region oldWAL dir to the global oldWAL directory. This happens after > afterRoll() method in AbstractWALRoller. > Since now the WAL archival is asynchronous the afterRoll() method does not > find any WAL file to be moved in the local region oldWAL dir. So the movement > to global oldWAL dir does not happen. > The test case checks for the file in the oldWAL dir and since it is not found > the test timesout. WE need a way to fix this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-25186) TestMasterRegionOnTwoFileSystems is failing after HBASE-25065
[ https://issues.apache.org/jira/browse/HBASE-25186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-25186. --- Hadoop Flags: Reviewed Resolution: Fixed Pushed to master and branch-2. Thanks [~ram_krish] for reviewing. > TestMasterRegionOnTwoFileSystems is failing after HBASE-25065 > - > > Key: HBASE-25186 > URL: https://issues.apache.org/jira/browse/HBASE-25186 > Project: HBase > Issue Type: Bug >Affects Versions: 3.0.0-alpha-1, 2.4.0 >Reporter: ramkrishna.s.vasudevan >Assignee: Duo Zhang >Priority: Blocker > Fix For: 3.0.0-alpha-1, 2.4.0 > > > After HBASE-25065, we are having a test case failure with > TestMasterRegionOnTwoFileSystems. > The reason is that we manually trigger a WAL roll on the master region. As > part of the WAL roll we expect the Master region's WAL will also be moved > from region oldWAL dir to the global oldWAL directory. This happens after > afterRoll() method in AbstractWALRoller. > Since now the WAL archival is asynchronous the afterRoll() method does not > find any WAL file to be moved in the local region oldWAL dir. So the movement > to global oldWAL dir does not happen. > The test case checks for the file in the oldWAL dir and since it is not found > the test timesout. WE need a way to fix this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
