Experts,
I am using OPA Batch processor and perform calculations over a huge records.
We observed a OPA view, looping through millions of statements whilst holding a lock on the main table.
A few occasion it took 97 minutes to release the lock. and we found that it was stuck pending a lock release on the main table.
I guess, it may the sessions transaction setting to be at fault here
i.e. all statements inside 1 transaction waiting for a final commit or rollback, rather than isolated single transactions.
This is when you set Implicit_Transactions ON at the start of the database connection.
Is there anyway to change it, to be ‘off’ without too much hassle in the config of the OPA engine?
we are running the Engine API Example from the command line as below.
java -jar May17/determinations-batch.jar --version --database "jdbc:sqlserver://DBServer;databaseName=DBName;applicationName=appName;" --userid DBUser--password DBPassword --processors 4 --config $1 --driver com.microsoft.sqlserver.jdbc.SQLServerDriver --driversrc May17/lib/sqljdbc4.jar
Thanks,
Abhishek