[jira] [Commented] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035430#comment-17035430 ] Emmanuel Lécharny commented on DIRSERVER-2299: -- I'm trying to get a release cut this week. Mavibot will be available in this release, as it's already available in previous releases, but not at the level of fonctionalities I consider 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
[jira] [Commented] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035354#comment-17035354 ] Rashid Mahmood commented on DIRSERVER-2299: --- Thanks for your feeback. Is there planned date for next release? can we expect working Mavibot backend in next release? > 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
[jira] [Commented] (DIRSERVER-2299) Missing Indexes after Restart
[ https://issues.apache.org/jira/browse/DIRSERVER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035173#comment-17035173 ] Emmanuel Lécharny commented on DIRSERVER-2299: -- Look, there are bugs, and sometime some bugs are more difficult to get fixed. Also, this is open source software. You get what you put in it. There are no hundred of paid people working on the server, fixing bugs on demand, all that for free. If you think ApacheDS is critical for your business, then it's probably time to consider investing more than just pushing mails asking if it's production ready. Otherwise, you probably have alternatives : OpenLDAP is one of them. In the mean time, we just can do one thing : do our best to get things working, in the spare time our day-job and family life leave us. > 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
