jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Mueller <muel...@adobe.com>
Subject Re: svn commit: r1368425 - in /jackrabbit/oak/trunk: oak-jcr/src/main/java/org/apache/jackrabbit/oak/jcr/ oak-jcr/src/main/java/org/apache/jackrabbit/oak/jcr/observation/ oak-jcr/src/main/java/org/apache/jackrabbit/oak/jcr/osgi/ oak-jcr/src/main/java
Date Thu, 16 Aug 2012 09:49:31 GMT

>In general the repository shutdown should IMO *never* block for any
>background tasks. A "kill -9" on a JVM process should IMHO be considered a
>valid way to shutdown a repository running inside the JVM, so there's
>nothing that the repository should expect a background task to finish in
>time for shutdown.

I agree.

Unless if we want to optimize for the 'quick startup' case (I don't think
we should at this stage). For a quick startup, it does make sense to wait
until the background threads, for example indexing, have finished. If not,
it will (has to) still work, but startup is slower because the indexing
has to be done at that time, and at that time the nodes are no longer in
the cache. But I think we should wait with such optimizations until we
have a good reason.


View raw message