Re: DB corruption (double get for block) fixed in M25 or upcoming M26?

2019-09-11 Thread Emmanuel Lécharny 

Hi Mike,


I checked, and what has been added is the support of the Transaction 
extended operation in the server. It obviously uses the internal 
transaction system in plave in M25, so I don't think it will fix the 
issue you are facing.


Bottom line, we really have to get rid if JDBM - the internal DB 
library-  which seems to be unreliable. Some effort has been started 
years ago, but stalled, with Mavibot. We are no that far from having a 
solid new DB, but I can't promise to be able to have it running before 
the end of this year...



On 11/09/2019 21:32, Michael Grove wrote:

Thanks for the response.

  


Re:

  


Now, and I have to check, I *think* we have added transaction support at

a higher level, and it may be only present in M26 (which is to be

released soon).

  


Did you get a chance to determine if transaction support has been added at a
higher level in M26?  If it hasn't, am I correct that there's not an
expectation that M26 fixes this issue?

  


Thanks.

  


-mike




-
To unsubscribe, e-mail: users-unsubscr...@directory.apache.org
For additional commands, e-mail: users-h...@directory.apache.org

RE: DB corruption (double get for block) fixed in M25 or upcoming M26?

2019-09-11 Thread Michael Grove 
Thanks for the response.

 

Re:

 

Now, and I have to check, I *think* we have added transaction support at 

a higher level, and it may be only present in M26 (which is to be 

released soon).

 

Did you get a chance to determine if transaction support has been added at a
higher level in M26?  If it hasn't, am I correct that there's not an
expectation that M26 fixes this issue?

 

Thanks.

 

-mike

Re: DB corruption (double get for block) fixed in M25 or upcoming M26?

2019-09-06 Thread Emmanuel Lécharny 

Hi Michael,

On 06/09/2019 15:51, Michael Grove wrote:

Hi all,

  


I'm hitting the "ERR_554 double get for block" errors that I've seen
discussed in many email messages and issues for Apache DS.  Most of the
reports of that problem appear to be before version M25.  E.g.

  


https://issues.apache.org/jira/browse/DIRSERVER-2172

https://issues.apache.org/jira/browse/DIRSERVER-2192

  


I'm using M25 on Windows.  At
https://directory.apache.org/apacheds/news.html it says

  


But the major improvement is the cross-indexes transaction support that has
been added, which is expecting to solve the database corruption issue we are
facing for years.

  


In the "ApacheDS db corrupt" thread available at
http://mail-archives.apache.org/mod_mbox/directory-users/201907.mbox/browser
, a user on M24 was told there was no fix for this issue "with the released
version", which I trust means M25, since M25 had been out well before this
July 2019 post.



yes, it applies to M25.




  


Am I correct that the M25 note of "expecting to solve the database
corruption issue we are facing for years" is in fact not the case, and that
M25 is known to suffer from this DB corruption issue still?


If you are still hit by the issue, it seems that the 'expectation' was 
not fulfilled :/



Now, and I have to check, I *think* we have added transaction support at 
a higher level, and it may be only present in M26 (which is to be 
released soon).



The problem is that it's hard to reproduce, we just see the effects.



That July 2019
thread suggested a fix would be available "in the coming weeks."  Is there a
rough ETA on that?  We're trying to decide whether to hold out for M26 or
switch to a different LDAP server.


We are expecting to release M26 soon (ie a week or two).



  At times for us our directory server
goes down multiple times daily due to this problem during lots of concurrent
use.  The repair mode hasn't worked effectively, so I just keep reverting to
snapshots that have the base LDIF imported.



If you want a proven stable LDAP server, you can switch to OpenLDAP: we 
are quite compatible when it comes to the schema. You will just have to 
configure the server to fits your need.




-
To unsubscribe, e-mail: users-unsubscr...@directory.apache.org
For additional commands, e-mail: users-h...@directory.apache.org