You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <di...@incubator.apache.org> on 2004/12/03 06:34:22 UTC

[jira] Updated: (DIREVE-92) Add JVM shutdown hook to prevent loss of cached entries

     [ http://nagoya.apache.org/jira/browse/DIREVE-92?page=history ]

Alex Karasulu updated DIREVE-92:
--------------------------------

    Summary: Add JVM shutdown hook to prevent loss of cached entries  (was: Add JVM shutdown hook to prevent loss of caches before next flush)

> Add JVM shutdown hook to prevent loss of cached entries
> -------------------------------------------------------
>
>          Key: DIREVE-92
>          URL: http://nagoya.apache.org/jira/browse/DIREVE-92
>      Project: Directory Eve
>         Type: Bug
>   Components: eve
>     Reporter: Alex Karasulu
>     Assignee: Alex Karasulu
>      Fix For: 0.8.0

>
> Looks like you can loose data if you shutdown the server after writing to it if you shutdown before a sync operation.  This is similar to the buffer cache idea.  At this point all writes are not persisted until a sync or buffers fill.  We will have the option later to use ACID transactions for perisiting on each write.  This is slower but safer.
> For now we just need a JVM hook to sync on shutdown.  This way all caches get flushed to disk before terminating when signals are trapped.  Gotta figure out how to do this.  Phoenix did this nicely.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira