Hi, just to keep you up-to-date before continuing with the tasks mentioned in my previous message.
Yesterday I launched the 3rd import process on the test environment, and it complained for /pageStore: Transaction log could not be truncated; size: 1768 MB/ but the import process continued (it was configured to continue on errors). Getting this error message seems strange: the JDBC url was /jdbc:h2:file:/path/to/mirror/db;MODE=PostgreSQL;CACHE_SIZE=65536;FILE_LOCK=SOCKET;LOG=1;MAX_LOG_SIZE=1024;AUTO_SERVER=TRUE;AUTO_SERVER_PORT=9092;/ while the 1st import completed with no problems at all (having the same jdbc url). I don't know the db size at that point cause I wasn't there. Then the scheduled nightly import runned with no problems, but now the database is ~17gb. So the database is not 10 times the expected size (I'd prefer to prepare the smaller db before), anyway I ran the recovery tool on it. Here you are the statistics after this run I can only notice quite strange negative numbers, but I am not aware of their precise meaning... BTW now I'm trying to export and reimport data just to rerun the recovery and give you the 2nd statistics: I've started the h2 console, and I'm still waiting for it to open the db session (actually it started more than 30 minutes ago) . I don't understand what the h2 console thread is doing: it uses some cpu with no disk access with the following stack (probably immutable) I've also tried to sampling it with jvisualvm, but the number of invocations of /java.io.DataInputStream.readInt()/ doesn't change. Nonetheless it continues using a CPU core (not at 100%). Further annotations (just in case): 1) between the 2nd and 3rd import I stopped Tomcat. I tried to see if the database was accessible through the h2 console (launching the h2 jar from the CLI). It was ok. Then I started Tomcat but I forgot to kill the h2 console jvm. I launched the import but it failed cause the DB was locked by the console jvm instance. I simply killed that jvm and relaunched the 3rd import. 2) the first time I used the recovery tool on the 17gb db I had to kill it cause I had not enough free space on the disk. Then I copied the db into another machine and relaunched the recovery process that gave the statistics inserted above. Thomas Mueller-6 wrote > Hi, > > How large is the database exactly, and how does it grow exactly? Are you > completely sure it doesn't stop growing? If yes, could you kill the > process > while the database is about 10 times as big as it should be, and then run > the recovery tool, and post the statistics part of the the output? And > then, could you shrink the file (for example by export to SQL script / > import from SQL script), run recovery again, and post the statistics of > this new file? > > Regards, > Thomas > > > On Tue, Aug 13, 2013 at 6:27 PM, davide.cavestro > < > davide.cavestro@ > >wrote: > >> I didn't measure it, but it was certainly lower. I'll give you more data >> asap. >> >> >> Noel Grandin wrote >> > On Tue, Aug 13, 2013 at 5:56 PM, davide.cavestro >> > < >> >> > davide.cavestro@ >> >> > > wrote: >> >> I've tried replacing setCharacterStream() with setString() but the db >> >> size >> >> still continues to increase. Is there any way to get an idea of actual >> >> fragmentation of internal data-structures? >> >> >> > >> > Sorry, no, no idea. >> > But I thought we were chasing a bug where shutdown was taking too >> > long, in which case making this change should make a difference. >> > Did you measure your new shutdown time with this change? >> > >> > -- >> > 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 >> an >> > email to >> >> > h2-database+unsubscribe@ >> >> > . >> > To post to this group, send email to >> >> > h2-database@ >> >> > . >> > Visit this group at http://groups.google.com/group/h2-database. >> > For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> >> >> -- >> View this message in context: >> http://h2-database.66688.n3.nabble.com/h2-Continuous-Increase-in-H2-db-size-after-dropping-and-loading-same-data-repeatedly-tp4026836p4027132.html >> Sent from the H2 Database mailing list archive at Nabble.com. >> >> -- >> 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 an >> email to > h2-database+unsubscribe@ > . >> To post to this group, send email to > h2-database@ > . >> Visit this group at http://groups.google.com/group/h2-database. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- > 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 an > email to > h2-database+unsubscribe@ > . > To post to this group, send email to > h2-database@ > . > Visit this group at http://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/groups/opt_out. -- View this message in context: http://h2-database.66688.n3.nabble.com/h2-Continuous-Increase-in-H2-db-size-after-dropping-and-loading-same-data-repeatedly-tp4026836p4027139.html Sent from the H2 Database mailing list archive at Nabble.com. -- 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 an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
