Memory leak in ADS ?

• Key: DIRSERVER-681
• Type: Bug
• Status: Closed
• Resolution: Invalid
• Priority: Blocker
• Assignee: Unassigned
• Reporter: Emmanuel Lecharny
• Affects Version/s: 1.0-RC3

Description

When doing thousands of searches, at a point, the memory get exhausted, and the server stop to deliver responses.

The first bet is that we have a memory leak somwhere. Using yourkit shows that the heap increase continuously while search requests are being processed.

However, I have done an extensive test whith all cache set to 1, and launched an heavy test (100 000 random search requests over a 10 000 entries base), with a Heap size set to 25 M, and everything is running fast (even if it's slow).

So the second bet would be that cache setting is to big in regard to the allocated memory, and we just exhaust memory using too much cache.

I will try to do a 12H test with 1 sized cache tonite, and a 48H test with 100 sized cache on tuesday and wenesday, to check which hypothese is the good one (hope the second will be it :).

Comments

[Emmanuel Lecharny]

The server is now running for more than 7 hours, with 5 clients searching for random entries. The cache has been set to standard value.

So far, it's seems to be perfectly ok. We may not have any memory leak, or at least not an important one.

The test will be running 11 more hours.

[Emmanuel Lecharny]

I have made a long test ( more than 27 hours, doing 900 searches requests per socond for a total of 10 614 000 random searches requests, on a server with only 256 Mbyte.

Everything went fine, except that my computer overheated and rebooted itself on wednesday when the temperature cimbed up to 37°C outside in Paris ...

No memory leak.

Let's close the issue for the moment.

[Emmanuel Lecharny]

Seems to be a false alarm. The memory should be carrefully set when using huge caches.

[Emmanuel Lecharny]

It was not a fix ...

[Emmanuel Lecharny]

Ok, now, the definitive status is correct