directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-1377) Potential concurrency issue when adding/modifying/deleting entries at a high rate
Date Wed, 08 Jul 2009 16:57:15 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728796#action_12728796
] 

Emmanuel Lecharny commented on DIRSERVER-1377:
----------------------------------------------

As of today, here is the status :
- I have run 2 000 000 add/delete using the MultiThreadedTest class. All was fine
- *but* the OneLevel index is broken. We can't any more do searches using this index, after
the test has run
- more precisely, the index is corrupted after only a few thousands of updates
- I can't craft a scenario corrupting the index, so it's pretty hard to understand why it
happens.

We decided to commit the current code, because in any case, it's way safer than the code we
have. We also want to substitute the AVLTree we are using internally with a simple array,
allowing us to have a better control, and potentially less odd that it can be a bug in AvlTree

Another action would be to test the server with this MultiThreadedTest against a previous
version of the server (1.5.3) to see if this issue was present then.

> Potential concurrency issue when adding/modifying/deleting entries at a high rate
> ---------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1377
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1377
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.5.4
>            Reporter: Emmanuel Lecharny
>            Priority: Blocker
>             Fix For: 1.5.5
>
>
> When adding/deleting entries with many clients (a client add and delete an entry many
times), we may have some concurrency problem, as the index are updated without concurrent
acces protection.
> Synchronizing the classes where we update the index might help.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message