The problem still exists in 2.1.214 and with LOB_TIMEOUT=1000. The issue
could not be reproduced with the current git build, but we can't use any
build other than official release. May I know when the next official
release is?.
On Tue, May 23, 2023 at 5:41 AM Andrei Tokar wrote:
> And to
And to confirm that problem is still there, please run it against at least
latest released version (2.1.214), or even better against current git build.
I have that feeling that you just run queries with LOB in the result which
causes extensive LOB cloning. Try to add ;LOB_TIMEOUT=1000 (1 sec
Greetings!
On Sun, 2023-05-21 at 23:42 -0700, Arjun Sahoo wrote:
> Reproducing the test case is easy, keep on ingesting and deleting
> records, you will see the memory usage increasing over time. If if
> query the table simultaneously , you will reach the trend faster.
You will need to write a
(1) That is not expected behaviour, my H2 databases grow to a point and
then stabilise (and I run my H2 databases pretty hard)
(2) in-memory is slightly different, we have a couple of places where we do
things different because we know it's a memory database
--
You received this message because
Noel,
question for better understanding please: Would a MEM database not grow
exactly as a File backed database keeps growing forever?
Or in other words, is there any difference between a MEMORY database
and File backed at TEMP FS?
I ask because all my file backed H2 databases keep growing and
I don't have any obvious answers.
You can try 2 things.
First, try building H2 from git master and seeing if the changes since the
last official release help.
If that doesn't help, we're going to need a standalone test case (no
Spring, etc) to reproduce the problem and then we might be able to
I am using spring data jpa to delete the records.
@Modifying
@Transactional
@Query(value = "delete from table where start_time_ms <= :startTimeMs",
nativeQuery = true)
Integer deleteInBulkByStartTime(@Param("startTimeMs") Long startTimeMs) throws
SQLException;
Spring takes care of managing
check that all your transactions are being closed. Holding a transaction
open means that the storage cannot be freed.
>
>
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send
Hi,
I am using Spring boot In-Memory H2DB. I am storing latest 100k records in
the database, so keep on deleting old records and inserting new records.
Application runs fine for 4-5 hours, after that it throws OOM Exception.
The memory consumption keeps on increasing even after deleting old
