Hi,
With version 1.4.x, the multi-threaded mode is still not the default, but I
would like to fully support it. It's still beta however. With version
1.4.x, table-level locking is no longer used by default. Instead, MVCC is
used.
Regards,
Thomas
On Wednesday, May 28, 2014, Brian Craft
Can you post a thread dump, so we can see where it is blocked?
Also which version is this, and what does your DB URL look like?
On 2014-05-25 20:24, Brian Craft wrote:
I'm doing a large insert into .. select * from CSVREAD ..., which is in a
transaction. It seems to be blocking
readers,
Version 1.3.171. The only option I'm setting is MVCC, like
somefile;MVCC=TRUE. I'll try to get a thread dump in a few minutes.
Does this mean readers should not be blocked during the insert?
On Tuesday, May 27, 2014 4:18:01 AM UTC-7, Noel Grandin wrote:
Can you post a thread dump, so we can
The overall load characteristics of the app are that there are many
readers, doing queries that are *usually* sub-second, and occasional large
batch inserts/deletes of, say, hundreds of thousands of rows. The main
goals are to not block readers, and minimize exposure of readers to
incompletely
Ah, it's actually somefile;CACHE_SIZE=65536;;MVCC=TRUE
Not sure if the double semicolon is a problem.
b.c.
On Tuesday, May 27, 2014 10:45:29 AM UTC-7, Brian Craft wrote:
Version 1.3.171. The only option I'm setting is MVCC, like
somefile;MVCC=TRUE. I'll try to get a thread dump in a few
qtp507284179-81 is the reader, which seems to be blocked indefinitely.
clojure-agent-send-off-pool-5 is the writer, doing insert into .. select
csvread
db is jdbc:h2:/data/cancer/cavm-testing;CACHE_SIZE=65536;MVCC=TRUE
--
You received this message because you are subscribed to the
H2 is not multi-threaded in this version. So a single long running
statement will block everything else. You'll either need to split it up
into smaller inserts (can still be a single transaction, just smaller
queries), or you could try turning on MULTI_THREADED=1.
There is multi-threaded
I'm doing a large insert into .. select * from CSVREAD ..., which is in a
transaction. It seems to be blocking readers, regardless of whether MVCC is
enabled. Is this expected? If I understand the threads on MVCC, it will
allow readers to execute concurrent with a running transaction, but
