Global Search not indexing newly created records

We are currently experiencing an issue with elastic search on our enterprise 10.0.4 instance hosted on premise. Newly created records are not being indexed and cannot be searched in the global search. We have attempted to reindex, which resolves all CRM records at that time, but any newly created records remain unsearchable.

Can anybody offer any advice?

Regards

Christopher 

Parents
  • Hi ,

    Here are a few things I would recommend checking:

    • Is the 'Elasticsearch Queue Scheduler' set to active and run as often as possible? This scheduler queues the actual records to be indexed to Elasticsearch
    • If you go into the scheduler record view, do you see jobs regularly being run? If not, there may be another scheduler causing a critical failure during your cron runs preventing this scheduler from triggering.
    • If you do see jobs regularly running, run the following queries:
      SELECT 
          date_modified, 
          status, 
          resolution, 
          message 
      FROM 
          job_queue 
      WHERE 
          name = 'Elasticsearch Queue Scheduler' 
      ORDER BY 
          date_modified DESC 
      LIMIT 
          0,10;

      The above query should show the results of the most recent scheduler attempts. The message should read something like 'Create consumers for: Leads, Accounts, ...' as it queues records for the respective modules to be indexed.
      SELECT 
          date_modified, 
          status, 
          resolution, 
          message,
          data 
      FROM 
          job_queue 
      WHERE 
          name = 'Elasticsearch Queue Consumer' 
      ORDER BY 
          date_modified DESC 
      LIMIT 
          0,50;

      The above query should show the results of the most recent attempts to index records. The data column represents the module it indexed and the message should output how many records were indexed for that module (e.g. 'Processed 3 records in 1 second(s)').

    Let me know what you find!

    Chris

Reply
  • Hi ,

    Here are a few things I would recommend checking:

    • Is the 'Elasticsearch Queue Scheduler' set to active and run as often as possible? This scheduler queues the actual records to be indexed to Elasticsearch
    • If you go into the scheduler record view, do you see jobs regularly being run? If not, there may be another scheduler causing a critical failure during your cron runs preventing this scheduler from triggering.
    • If you do see jobs regularly running, run the following queries:
      SELECT 
          date_modified, 
          status, 
          resolution, 
          message 
      FROM 
          job_queue 
      WHERE 
          name = 'Elasticsearch Queue Scheduler' 
      ORDER BY 
          date_modified DESC 
      LIMIT 
          0,10;

      The above query should show the results of the most recent scheduler attempts. The message should read something like 'Create consumers for: Leads, Accounts, ...' as it queues records for the respective modules to be indexed.
      SELECT 
          date_modified, 
          status, 
          resolution, 
          message,
          data 
      FROM 
          job_queue 
      WHERE 
          name = 'Elasticsearch Queue Consumer' 
      ORDER BY 
          date_modified DESC 
      LIMIT 
          0,50;

      The above query should show the results of the most recent attempts to index records. The data column represents the module it indexed and the message should output how many records were indexed for that module (e.g. 'Processed 3 records in 1 second(s)').

    Let me know what you find!

    Chris

Children