Project

General

Profile

Actions

Bug #8423

closed

When updating a Rudder install, changes_executionTimeStamp_idx index is not created

Added by François ARMAND almost 5 years ago. Updated almost 5 years ago.

Status:
Released
Priority:
N/A
Category:
Packaging
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

The index that allows to get changes by rules is not created when migrating a Rudder instance. So, getting changes is extremelly slow.

Typically, if you are seing warning message: "[Store Agent Run Times] Task frequency is set too low! Last task took xxxx ms but tasks are scheduled every yyy ms.", you might missing that index.

The real diagnosis is on psql command line (after a psql -u rudder etc):

rudder=> \d ruddersysevents
[...table details....]
Indexes:
    "ruddersysevents_pkey" PRIMARY KEY, btree (id)
=>  "changes_executiontimestamp_idx" btree (executiontimestamp) WHERE eventtype::text = 'result_repaired'::text
    "component_idx" btree (component)
    "composite_node_execution_idx" btree (nodeid, executiontimestamp)
    "executiontimestamp_idx" btree (executiontimestamp)
    "keyvalue_idx" btree (keyvalue)
    "nodeid_idx" btree (nodeid)
    "ruleid_idx" btree (ruleid)
[...other info...]

So, we need to add a migration script to create that index.

Woraround: you can create the index by hand. When connected to Rudder db with psql, execute following query:

CREATE INDEX changes_executionTimeStamp_idx ON RudderSysEvents (executionTimeStamp) WHERE eventType = 'result_repaired';

Subtasks 2 (0 open2 closed)

Bug #8442: Update rudder-upgrade to create changes_executionTimeStamp_idx index if it doesn't existsReleasedBenoît PECCATTE2016-06-02Actions
Bug #8445: Borken build due to #8442ReleasedJonathan CLARKE2016-06-02Actions

Related issues

Related to Rudder - Bug #8424: When updating runs, hooks should really be asyncReleasedBenoît PECCATTE2016-05-30Actions
Actions #1

Updated by François ARMAND almost 5 years ago

  • Related to Bug #8424: When updating runs, hooks should really be async added
Actions #2

Updated by Nicolas CHARLES almost 5 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
Actions #3

Updated by Nicolas CHARLES almost 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/1109
Actions #4

Updated by Nicolas CHARLES almost 5 years ago

  • Status changed from Pending technical review to Pending release
Actions #5

Updated by Vincent MEMBRÉ almost 5 years ago

  • Category changed from System integration to Packaging
Actions #6

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.17, 3.1.11 and 3.2.4 which were released today.

Actions

Also available in: Atom PDF