Highlighted
Absent Member.
Absent Member.
335 views

Create or copy an attribute index?


Hi there,
The eDir 8.8.8 documentation seems ambiguous to me. I want a second
server to have a live custom index that I created. The documentation
says:
> If you've found a particular index to be useful on one server and you
> see the need for this index on
> another server, you can copy the index definition from one server to
> another


and later it says > 6 Use the columns provided to move a copy of the index to the desired
> server.


So is it the definition that gets copied or the full index? If it is
the full index, will it automatically update on the second server or is
it static?

Cheers,
Kirk


--
kmaule
------------------------------------------------------------------------
kmaule's Profile: https://forums.netiq.com/member.php?userid=306
View this thread: https://forums.netiq.com/showthread.php?t=50965

Labels (1)
0 Likes
5 Replies
Highlighted
Absent Member.
Absent Member.

Re: Create or copy an attribute index?

Just the definition is copied; the index data probably should never be
copied for a number of technical reasons including:

1. Different servers hold different data; one with replica of partition
A, another with replica of partition B, another with no replicas at all...
index data synchronization doesn't make sense.

2. Indexes likely point to EIDs, which are DIB-specific identifiers.
Thus, moving an index with one DIB's identifiers to another DIB is pointless.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Create or copy an attribute index?


Sounds good. The index REALLY helped query performance. Before we were
45 seconds per user migrated and after we were 1.33 seconds!
The attributes were workforceID and managerWorkforceID.

Cheers,
Kirk


--
kmaule
------------------------------------------------------------------------
kmaule's Profile: https://forums.netiq.com/member.php?userid=306
View this thread: https://forums.netiq.com/showthread.php?t=50965

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Create or copy an attribute index?


That was for 19,000 users BTW.


--
kmaule
------------------------------------------------------------------------
kmaule's Profile: https://forums.netiq.com/member.php?userid=306
View this thread: https://forums.netiq.com/showthread.php?t=50965

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Create or copy an attribute index?

Yes, anytime you can add an index to help with value or substring searches
you'll likely feel the relief from the system quickly. Indexes come on
very quickly, which is nice, and once there they really do amazing things.

I once helped a customer who had a terribly-written, third-party
application. That application had the brilliant code within to query the
directory for an object having customAttrWhatever=configData and the
object which had that attribute had a bunch of configuration data. There
was only one object that had this value in the whole tree and every single
user login required a lookup of the data. It become clear that this
application was crap at this point: Why didn't it cache the setting it
read a couple hundred times per second? why didn't it cache the DN, or
let the admin set the DN, of the object rather than using a lookup by an
attribute value? Argh! In the application vendor's defense, they did
document to index this attribute.

Before indexing the attribute one user might get logged in and then the
server went to high utilization and never recovered until eDirectory was
killed. The DIB had a couple million objects so the full scan of the DIB
to find all objects with that attribute set to that value was non-trivial.
If allowed to finish, the lookup for the object took a couple of minutes;
reminer: this needs to happen with every user login, and there were
normally about 100/second.

After adding the index the search returned in tiny parts of a single
second. The application was still crap, but at least it was crap with
data provided to it over and over and over very quickly.

There is an 'elapse.pl' CoolSolution from Novell/NetIQ that you can feed
output from ndstrace (+TIME +LDAP) which can tell you if any searches are
running long. If so, you can investigate to see if they can be optimized
(are they searching by value or substring) and then add indexes if
appropriate. Not a bad idea after adding new applications, migrating data
around, building new trees or adding servers, etc.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Create or copy an attribute index?

On 5/29/2014 9:05 AM, kmaule wrote:
>
> Sounds good. The index REALLY helped query performance. Before we were
> 45 seconds per user migrated and after we were 1.33 seconds!
> The attributes were workforceID and managerWorkforceID.


My favorite example was an AIX system, using the IBM equiv of PAM (They
call it LAM I think) and when doing an ls -al, it was crawling. We were
in a meeting, the guy showing us the performance was onscreen.

I added an index of uidNumber while he was talking. An integer field,
only 2000 entries, indexed almost as fast as I enabled it.

He actually jumped out of his seat when suddenly the ls -al output sped
up immenesly. (Every time it looked up a user or group for
owner/group/root in the directory listing, it was hitting uidNumber).

Indexes are great.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.