search

lwhay / asterixdb

Automatically exported from code.google.com/p/asterixdb
0 stars 0 forks source link

create dataverse ddl recovery test fails #691

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
recovery_ddl/dataverse_recovery tests fails.
When the test failed, the transaction log file size is 0 even if we ran a 
transaction which creates a new dataverse. Therefore, the recovery after the 
asterix instance is killed can't recover correctly since the log file is empty.

Original issue reported on code.google.com by kiss...@gmail.com on 10 Dec 2013 at 7:50

GoogleCodeExporter commented 9 years ago 
There are concurrent operations, one is a sharp checkpoint and the other is to 
create a new dataverse. While the checkpoint is going on, the ddl query comes 
in and is processed concurrently. This checkpoint removes the log file even if 
the effect of the newly created dataverse was not flushed before removing the 
log file.

This issue is found by Pei's recovery_ddl test and fixed in branch.

Original comment by kiss...@gmail.com on 10 Dec 2013 at 8:55

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision ac2652fcfbcc.

Original comment by kiss...@gmail.com on 10 Dec 2013 at 11:24