Parallel processing of transactions on different databases is not happening with tungsten

[GoogleCodeExporter]

What steps will reproduce the problem?

1.  Master: Execute DDL "create table .. as select * from " on DB1 which should 
run for greater than few minutes..
2.  Wait for point 1)  to complete.
3.  Master: Execute few DMLs on DB2 after point 1) completes. These DMLs can be 
one or two insert statements which should take less than second time to execute.

What is the expected output?
Transaction on DB2 should be finished first on slave.

What do you see instead?
It is not executing parallel transaction on DB2 (slave), instead it is waiting 
for transaction on DB1 to complete on slave.

What version of the product are you using?
MySQL version: 5.5.17-55-log
Tungsten version: tungsten-replicator-2.0.5

On what operating system?
OS version: Ubuntu  x86_64 GNU/Linux
...

Please provide any additional information below.
- Please find below execution steps and attaching related files.

1. test_db.sql.gz
- Please unzip this file and import it on blank database.
2.  slow_query.sql
- Execute query in file but before that change database name with database you 
have created to import above data.
3. create_small_db.sh
- Once slow_query.sql execution completes on master then execute 
create_small_db.sh and provide new database name as parameter so it will create 
second database and then executes insert statements on it.

Original issue reported on code.google.com by shaham...@gmail.com on 3 Jul 2012 at 3:15

Attachments:

• test_db.sql.gz
• slow_query.sql
• create_small_db.sh
• create.sql
• dept.sql
• category.sql
• emp.sql

[GoogleCodeExporter]

How many channels were enabled?  Can you load the static-svc.properties file so 
that we can see the parallel replication configuration?  Thanks!

Original comment by robert.h...@continuent.com on 6 Jul 2012 at 4:22

[GoogleCodeExporter]

Another thing that would be helpful is the output of 'thl list' that shows the 
log for these transactions.  If you have transactions that somehow cross 
schemas, even with multiple channels Tungsten will serialize these fully across 
all channels.  

Original comment by robert.h...@continuent.com on 6 Jul 2012 at 4:24