Project

General

Profile

Actions

Bug #4849

closed

Bug #4831: Reports cannot be inserted into postgresql due to a limit on ids

Add an entry in the FAQ about limit on id

Added by Vincent MEMBRÉ almost 10 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
1
Category:
Documentation
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

We need to add an entry in our FAQ on http://rudder-project.org to explain the problem, how to detect it, how t analyse it, and the available solutions.

  • It should include a request to see if the problem islikely to occur (select max(id) from ruddersysevents)
  • Some explanation (we use integeer id which is limiter to 2 billion ...)
  • Some different workaround ( upgrade to 2.10.2, and run the script ...)
Actions #1

Updated by Vincent MEMBRÉ almost 10 years ago

  • Pull Request set to https://github.com/Normation/rudder/pull/511
Actions #2

Updated by Vincent MEMBRÉ almost 10 years ago

  • Subject changed from Migration script to bigint locks databases for a too long time, having lots of casualties to Add an entry in the FAQ about limit on id
  • Description updated (diff)
  • Category changed from System integration to Documentation
  • Target version changed from 2.6.13 to 2.10.1
Actions #3

Updated by Vincent MEMBRÉ almost 10 years ago

  • Pull Request deleted (https://github.com/Normation/rudder/pull/511)
Actions #4

Updated by Vincent MEMBRÉ almost 10 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
Actions #5

Updated by Nicolas CHARLES almost 10 years ago

  • Status changed from Pending technical review to In progress
  • Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ

Vincent, this is fine, but a bit complex for standart user.
Could you modify the entry by having two cases:
- I upgraded to Rudder 2.10.1: run the script /opt/rudder/bin/rudder-upgrade-database , it will tell you if you need to upgrade Database, and let you choose your upgrade path (purge all reports from nodes, upgrade only last reports for each nodes, upgrade all reports)

- I can't upgrade to 2.10.1 or greater:here you put the "check if you are concerned" and "alter reports"

Actions #6

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.1 to 2.10.2
Actions #7

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.2 to 2.10.1
Actions #8

Updated by Vincent MEMBRÉ almost 10 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES

Updated! thank Nico!

Actions #9

Updated by Vincent MEMBRÉ almost 10 years ago

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

Updated by Vincent MEMBRÉ almost 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.1, which was released today.
Check out:

Actions

Also available in: Atom PDF