Hi Mike, Thanks for letting me know!
This seems to be there is something wrong when we set memory component Ids, especially with multiple partitions on one NC sharing one primary index operation tracker, which makes LSM component lifecycle management much more complicated. However, I couldn't reproduce it on my local, even after running it a lot of times...But I'll keep digging to see which part is wrong. Best regards, Chen Luo On Fri, Nov 10, 2017 at 8:43 PM, Michael Blow <[email protected]> wrote: > Hi Chen, > > I noticed this failure on Jenkins for a minor interface exception > refactoring change, can you take a look? > > > <https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-verify-asterix-app/2209/> > https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit- > verify-asterix-app/2209/ > > *16:25:40* SEVERE: SEARCH failed to enter components on {"class" : > "LSMBTree", "dir" : > "/home/jenkins/jenkins/workspace/asterix-gerrit-verify-asterix-app/asterixdb/asterix-app/target/io/dir/asterix_nc1/iodevice1/storage/partition_1/test/LineID_idx_idx_LineID_suppkey", > "memory" : 2, "disk" : 1}*16:25:40* java.lang.IllegalStateException: LSM > memory component receives illegal id. Old id [1510360027993,1510360027993], > new id [1510360027993,1510360027993]*16:25:40* at > org.apache.hyracks.storage.am.lsm.common.impls.AbstractLSMMemoryComponent.resetId(AbstractLSMMemoryComponent.java:276)*16:25:40* > at > org.apache.asterix.common.ioopcallbacks.AbstractLSMIOOperationCallback.recycled(AbstractLSMIOOperationCallback.java:205) > > > Thanks! > > -MDB >
