Cannot load too much records in one time about droonga-engine

[kou]

How many database size? (du -hc DB_DIR)
If database size is 2GiB over, droonga-engine process also uses 2GiB over. It is a natural behavior.

By the way, why did you use -KILL? The process didn't receive -TERM?

[piroor]

When I saw 98% memory usage with too large swap, the database was 10GiB or more. RAM of machines are 8GB (node1), 8GB (node2) and 6GB (node3). The 6GB RAM machine (node3) was dead at first. So, as you described, it leached to the maximum size of the on-memory database... OK I've understood.

Hmm, then, I think I have to shrink the database to benchmark it.

By the way, why did you use -KILL? The process didn't receive -TERM?

First I tried kill $(cat ~/droonga/droonga-engine.pid) but some processes were still there. So I killed rest processes with "-KILL" option to stop them certainly.

[piroor]

On the other hand, Groonga can load such too much records in one time simply. So I think this should be fixed by Droonga, even if we activate partitioning of databases.