LI82452: ELASTIC CURATOR FAILURE IN 10.0.1.5-IFIX3 AND 10.0.4.0 CAUSES RETENTION (CRON) JOB TO FAIL

APAR status

• Closed as program error.

Error description

• All the analytics retention jobs are failing to clean up old
  indices in ElasticSearch. This leads to uncontrolled analytics
  disk space increase and user has to manually delete old indices.
  

Local fix

Problem summary

• The retention (cron) job fails with the following messages and
  error shown in the log:
  
  <span style="font-family:courier new,courier,monospace">Ready to
  perform data retention with unit: days and unit_count: 30
  CURATOR_PATH = /usr/local/bin/curator. Starting curator
  process...
  Traceback (most recent call last):
    File \/usr/local/bin/curator\, line 11, in <module>
      load_entry_point(elasticsearch-curator==5.4.1,
  console_scripts, curator)()
  ...
  TypeError: load() missing 1 required positional argument:
  Loader</span>
  
  The result is that <span style="background-color:rgb(255, 255,
  255)">analytics data indices are not cleaned up after the
  specified retention period, which defaults to 90 days. This
  leads to uncontrolled analytics </span><span
  style="background-color:rgb(255, 255, 255)">disk space increase
  and users must manually delete old </span><span
  style="background-color:rgb(255, 255, 255)">indices from
  analytics storage.</span>
  
  <span style="background-color:rgb(255, 255, 255)">Note: The
  rollover (cron) job is not impacted.</span>
  

Problem conclusion

• All affected users should upgrade to API Connect version
  10.0.4.0-ifix1 or 10.0.1.5-ifix4 to restore expected behavior.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  API CONNECT ENT

• Fixed component ID

  5725Z2201

Applicable component levels