"Jin Heo" <[EMAIL PROTECTED]> writes: > > I encouters some erros about duplicate key problems when request rates > are high. If the request rate is low, then it's okay. I guess the > problem is that most of the tables in the TPCW implementation doesn't > use auto incremented > primary key. So before inserting a new record, it reads the max id > value in the table and increases it by one for the new id. After > insertion opertaion, TPCW commits transaction. MySQL server works > correctly with the operation. > But with Sequoia, it looks like the operation deosn't perform > automicly and the read operatation sometimes is stale. >
This should work iff the backend transactionIsolation level is REPEATABLE_READ or above, with or without sequoia. To better understand this issue, here is what I would try (with and without sequoia): - vary & check the transaction isolation level - vary the number of client threads - try WaitForCompletion policy="all" This is very interesting, thanks for sharing it. _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
