#7787 Missing indexes for automountmapname and automountkey
Closed: fixed Opened by cheimes.

Issue

Bug shows https://pagure.io/freeipa/issue/6722 unindexed searches for two automount related attributes. Unindexed filters can cause performance issues. Automount is commonly used to automatically mount user home directories or other shared resources.

The unindexed filters are:

- Unindexed Filter: (&(automountmapname=auto.direct)(objectclass=automountmap)) (occurrances 2)
- Unindexed Filter: (&(automountmapname=auto.master)(objectclass=automountmap)) (occurrances 2)
- Unindexed Filter: (&(automountkey=*)(objectclass=automount)) (occurrances 4)

There is already an index cn=automountkey,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config. However automountkey is only index for eq. A automountkey=* filter seems to use pres index only.

Steps to Reproduce

  1. install IPA system with automount integration
  2. configure automount for home dirs
  3. log in

Actual behavior

logconf.pl shows unindexed filters

Expected behavior

No unindexed filters

Version/Release/Distribution

freeipa-server-4.7.0-3

Additional info:


Metadata Update from @cheimes:
- Issue tagged with: performance

Metadata Update from @cheimes:
- Custom field on_review adjusted to https://github.com/freeipa/freeipa/pull/2649

master:

  • 0fb87bfe827b10af25fcd35c327b33977053e0e3 LDAPUpdate: Batch index tasks
  • ed436e4b62c9d3ec02111d486ba77bd09e9838fc Add more LDAP indices
  • a34d92d25c97feb778d4c222704d8ac32e146768 Create reindex task for ipaca DB

ipa-4-6:

  • 55f18a8bd51267dacf6d048ac94179c1a44714b0 LDAPUpdate: Batch index tasks
  • f29ab7730b3b8866f9a10ddaffb0b828b53b1436 Add more LDAP indices
  • 26d90cdd69641d07a11b8f8ddbd340aded42280d Create reindex task for ipaca DB

ipa-4-7:

  • ad37e0c2b76afda289b7795f518ae9a1e0703151 LDAPUpdate: Batch index tasks
  • 903cfe390311b8e21273ceeb2a889974aabc1708 Add more LDAP indices
  • e484c4ba0a54813b84fffab5944d5ccec7a2c3b8 Create reindex task for ipaca DB

The new indices will be available in 4.7.3 and next 4.6 update.

Metadata Update from @cheimes:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Metadata