FYI We learned a lesson and i just wanna tell you.
Using HSQL for recovery log we saw a static memory usage increase by logging the garbage collector (JVM_OPTIONS -verbose:gc -Xloggc:<file> -XX:+PrintGCTimeStamps -XX:+PrintGCDetails ) after extensive write operations. First we thought it was a cache inside sequoia but it was HSQL, that was used for the recovery log. The jdbc-url contained a db-file configuration, but HSQL was configured to use "memory" tables. So the recovery log was stored in memory and caused the memory usage increase of the sequoia process. After a lot of write operations, the sequoia got an Out of Memory. We changed the HSQL properties to use "cached" tables and now everything works fine. Stefan
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
