[
https://issues.apache.org/jira/browse/DIRSERVER-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307186#comment-16307186
]
Emmanuel Lecharny commented on DIRSERVER-2216:
----------------------------------------------
Sadly, yes, M24 is not immune :/
I'm currently working on Mavibot, expecting to have it ready ASAP, but I have a
limited amount of dedicated time for it, between my day job and my 10m old baby
:/
Currently, transaction has been implemented, with a better cache, I still have
to handle the cleanup, but I'm thinking of using Mavibot as is (ie, with no
handling of 'dead' versions). This would mean teh database will never shrink
automatically; but for a few tens of thousands entry, that should be acceptable
(and reloading the full data would create a shrinked database).
> Data corruption with the export
> -------------------------------
>
> Key: DIRSERVER-2216
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2216
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: installer-plugin
> Environment: Windows
> Reporter: prisy cherian
> Fix For: 2.0.0-M24
>
> Attachments: ldap_backup_2017-12-28_13-13-15.ldif
>
>
> Hi,
> We are using Apache DS in Windows for an year now.
> We started with 50 users for development and everything was working as
> expected.
> We scheduled backups every 2 hours.
> Later in Production, LDAP data hangs & Search stops to work throwing USER NOT
> FOUND or LDAP Connection Timeout Exception or Attribute not found etc. The
> exception differs every time, eventually we found out in one of the back up
> files that it is Data Corruption.
> Everytime, we had to restore the backup & it is more than 10 times by now.
> We have around 11,000 users now. We schedule backup every day.
> We found a similar issue happening in M17 & M20 with the large number of user
> import-export.
> Is this issue with JDBM Backend is still in M24 also?
> Can you please suggest ?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
