| Jörg Henne (JIRA) 2006-07-30, 7:11 am |
| [ http://issues.apache.org/jira/brows...=3Dcomments#ac=
tion_12424376 ]=20
=20
J=C3=B6rg Henne commented on DIRSERVER-685:
--------------------------------------
Great to see you have a look at this problem. I've noticed that upon unclea=
n shutdowns, updates are usually lost. A quick glance at the code indicated=
that the JDBM commit was only called during clean shutdown, so this issue =
was already on my list. Since even if there are not formal transactions, DS=
should try to ensure durability of updates. This means committing after ea=
ch update by default, despite the performance hit it will bring about.
> Modification on an entry should always be flushed to the disk
> -------------------------------------------------------------
>
> Key: DIRSERVER-685
> URL: http://issues.apache.org/jira/browse/DIRSERVER-685
> Project: Directory ApacheDS
> Issue Type: New Feature
> Reporter: Emmanuel Lecharny
> Priority: Critical
>
> When modifying an entry, we should always flush this entry to the disk.
> The JDBM backend, AFAIK, only update its cache, and a thread flush those =
caches periodicaly. However, I may be wrong (and I hope to be wrong 
--=20
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: htt=
p://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|