Menu

#227 DMLThreadTest fails to read records sometimes

V1.2 Beta
open-accepted
performance (7)
7
2008-05-21
2008-05-07
No

For smaller values of lock timeout =500 microsecs,
sometimes the index structures are getting corrupted.

This is the sample output

[praba@prabakaran performance]$ ./DMLThreadTest
11063:3086744464:Mutex.cxx:159:Unable to get the mutex , tried 10 times
11063:3086744464:Chunk.cxx:375:Unable to acquire chunk Mutex
11063:3086744464:TableImpl.cxx:376:Error in inserting to index
11063:3086744464:TableImpl.cxx:385:Unable to insert index node for tuple 17ee5ae4
RETURNING EARLY: -6
Insert: Thread 3086744464 0: Total rows :626 Time taken:26 ms
Insert: Thread 3076254608 1: Total rows :10000 Time taken:93 ms
Tuples found: 10626
Index Tuples found: 627
Select: Thread 0: Total rows :627 Time taken:1 ms
Select: Thread 1: Total rows :10000 Time taken:47 ms

Discussion

  • Prabakaran Thirumalai

    Logged In: YES
    user_id=1500244
    Originator: YES

    This is because return value is not checked in HashIndex.cxx during bucket list insert failure. This is fixed now. With this fix, the frequency is reduced but the problem is still there and now it is rarely reproducible. run the same test many times again and again to reproduce the issue. set lock timeout =40 microsecs

     
  • Prabakaran Thirumalai

    • assigned_to: nobody --> prabatuty
    • status: open --> open-accepted
     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.