Thanks for your continued support and excellent work on this great product.

We have 20+ customers in the field on ApacheDS M16. The vast majority of them 
have been using it the last 6 months without issue.
However in a few of the larger installs, where there are 4-6 application 
servers, we've had some trouble.
On a dozen or so occasions, partitions have randomly become inoperable. The 
only recourse in these cases is to restore the partitions from a backup.
I'm pretty sure this is due to the concurrency challenges Emmanuel has 
explained in emails over the past year.

When this situation occurs there is a prolonged downtime as we work with the 
customers to restore.
As one might expect, we're getting pressure for answers and so I'm looking for 
some guidance.

A few questions:
Would upgrading our installed base to M17 lessen exposure to this concurrency 
situation?

Should we sit tight and wait for another release that may offer additional 
guard conditions or something more to address this?

I know there is an effort to replace JDBM with a Mavibot backend, is this 
something we can look for in 3, 6, 12 months?

On this side, there is a significant cost to uplift these customers so we'd 
rather not do it twice.
However, we saw that M16 is no longer available for download so we're trying to 
determine our best path forward.

Many thanks, Carlo Accorsi

Reply via email to