← Back to team overview

mahara-contributors team mailing list archive

[Bug 1457712] Re: More robust Elasticsearch data uploading

 

** Changed in: mahara
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1457712

Title:
  More robust Elasticsearch data uploading

Status in Mahara ePortfolio:
  Fix Committed

Bug description:
  The search/elasticsearch plugin has a cron job that loads data into
  the Elasticsearch server. Currently, this cron job has a couple of
  problems:

  1. It sends all the data from search_elasticsearch_queue in just one
  /_bulk operation. This means that if you've got a proxy server in
  front of your Elasticsearch server, it's quite likely to reject the
  request because it'll be larger than the allowed request size.

  2. It deletes the records from the queue table *before* attempting to
  upload them to Elasticsearch. If the upload fails, all of the records
  that were part of that bulk operation are basically lost and never get
  indexed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1457712/+subscriptions


References