[
https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035118#comment-17035118
]
Rashid Mahmood commented on DIRSERVER-2299:
-------------------------------------------
I already mentioned in issue description which version we are using. If new
version is using one .db file then why repair command generates a zero byte
size no named .db file, see 4th comment.
I still dont understand why index information was lost after server stop,
possible reason could be that indexes were never written on file-system and
were kept in memory.
Is there any tool from ApacheDS to validate the database for corruption and to
explore the meta information inside database?
We are afraid that in production environment we can face severe search issues
(because of indexing) or possible data corruption issues with data replication.
Is ApacheDS Production Ready?
> Missing Indexes after Restart
> -----------------------------
>
> Key: DIRSERVER-2299
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2299
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: index, ldap
> Affects Versions: 2.0.0.AM25
> Reporter: Rashid Mahmood
> Priority: Major
> Attachments: ApacheDS 2.0.0.AM24-example-structure.png, ApacheDS
> 2.0.0.AM25-example-structure.png, after-repair.png,
> image-2020-02-06-16-53-48-839.png, image-2020-02-11-17-02-41-811.png,
> index-config.png
>
>
> We have decided to use ApacheDS (version 2.0.0.AM25) for Authentication in
> our product. Ldap Server and Directory Service are being used in Embedded
> Mode.
>
> During our Tests we found that after Restart, some of the Entries via Indexed
> Attribute Search Filter are not comming in search result. After considering
> various possibilities we found that it is Indexing problem. We used Repair
> commnd and then we see those entries in search results.
>
> Why some of the indexes were missing even it was a gracefull shutdown?
>
> We want to avoid repair command after every restart unless it is really
> necessary. Our product will serve in future more than 50K users, we have fear
> that it would cost us a lot if we encounter those unexpected problems.
>
> These are two attributes used in our search filters
> dn: ads-indexAttributeId=mail,ou=indexes,ads-partitionId=tsi,ou=part
> itions,ads-directoryServiceId=default,ou=config
> ads-indexattributeid: mail
> ads-indexHasReverse: FALSE
> ads-indexcachesize: 1000
> objectclass: ads-index
> objectclass: ads-jdbmIndex
> objectclass: ads-base
> objectclass: top
> ads-enabled: TRUE
> dn: ads-indexAttributeId=telID,ou=indexes,ads-partitionId=tsi,ou=part
> itions,ads-directoryServiceId=default,ou=config
> ads-indexattributeid: telID
> ads-indexHasReverse: FALSE
> ads-indexcachesize: 1000
> objectclass: ads-index
> objectclass: ads-jdbmIndex
> objectclass: ads-base
> objectclass: top
> ads-enabled: TRUE
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
