There is a timeout for full-text index commit operations. This avoids that the system waits for Exalead to complete a full-text index commit without any time limit, i.e. possibly forever.

The timeout is defined in the 'Exalead' element of 'ServerConfig' by parameters 'CommitTimeoutBase' and 'CommitTimeoutPerObject':

   <Exalead

     BaseCommandUrlV5="http://localhost:10010/search-api/search"

     BasePapiServerUrlV5="http://localhost:10002"

     ShowRefinements="true"

     CommitTimeoutBase="10000"

     CommitTimeoutPerObject="50"/>

Both parameters are expressed in milliseconds. The total time-out time for a commit operation is 'CommitTimeoutBase' plus 'CommitTimeoutPerObject' times the number of objects being indexed. Their default values are 20000 (20 seconds) and 200 respectively.

For example, using the default values, the time-out when indexing 500 objects is 2000+200*500 = 120000 = 120 seconds = 2 minutes.

If a full-text index commit does not complete within the specified time-out the system logs (or displays) an error:

   Exalead index commit failed: exceeded the XX seconds time-out

where XX is the computed time-out.

When requesting just a full-text index commit using

    srv4 commitindex

the system uses 100,000 as the number of objects to compute the time-out.

The time-out applies only to Exalead version 5.x (Cloud View), not to the previous versions 4.x.