search

br1ghtyang / asterixdb

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

ComponentLSN (LSN of LSM Index components) issues #591

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
1. FirstLSN of the in-memory component should be set to the LSN of an update 
log, not the LSN of the corresponding commit log. We currently set the firstLSN 
of the in-memory component to LSN of the commit log.
    ==> Check the usage of the FirstLSN and modify it correctly.
2. Revisit synchronized blocks in transactionContext by asking whether those 
blocks are necessary.
3. BaseOperationTracker maintains componentLSNs. We need to make sure which 
method reading/writing the LSNs should be synchronized and which are not. Also, 
let's put comments there why those synchronizations are needed or not since 
it's not obvious.

Original issue reported on code.google.com by kiss...@gmail.com on 30 Jul 2013 at 10:27

GoogleCodeExporter commented 8 years ago

Original comment by kiss...@gmail.com on 11 Oct 2013 at 12:29