[prev in list] [next in list] [prev in thread] [next in thread] 

List:       forgerock-opendj
Subject:    [Opendj] Crippled cluster - some questions
From:       klaus () vink-slott ! dk (Klaus Vink Slott)
Date:       2012-09-11 10:34:40
Message-ID: 504F13C0.3020301 () vink-slott ! dk
[Download RAW message or body]

Hi and thanks for your information Ludovic.

Further comments inline.

On 06-09-2012 10:52, Ludovic Poitou wrote:
> On Thursday, September 6, 2012 at 10:27 , Klaus Vink Slott wrote:
> 

>> I have a 2 server replication setup in production running without
>> troubles for a year with something like 300000 entries. After a crash
>> last week one server has not performed well. It is now running with 100%
>> CPU and responds slow.
After fighting several days with TLS problems (see next post), building
a replacement cluster, I decided to leave for weekend. On Friday I
closed all open ssh sessions including some to the loaded server. Now
looking at our monitoring system I see that the load dropped to normal
about the same time as I closed the last session before weekend. The
server is now behaving without problems.

While I was logged in last week I did shut down the OpenDJ instance, I
verified that the load went to zero - restarting the OpenDJ process,
load went high again. According to top, a java single process took all
cycles from one cpu.

I have absolutely no idea what made the difference!

[cut..]
>> ... "error occurred while reading from index
>> dc_sc_dc_ku_dc_dk_ds-sync-hist.ordering. The index seems to be corrupt"
> 
> There is a known issue with the ds-sync-hist index which has been
> resolved in OpenDJ 2.4.5.

Thanks. This made me decide to build a replacement cluster.


>> Does OpenDJ bring its own Java?
> 
> No it doesn't. You can check in the config/java.properties the Java Home
> that was used at install time. OpenDJ tries to keep using the same
> version to avoid surprises. 
I see.

-- 
Regards
Klaus
Sysadmin on
Faculty of Humanities
UniCPH



[prev in list] [next in list] [prev in thread] [next in thread]