Rudder

All our ids in reports database are based on integer which limits to 2147483647 the number of entries. That can be reached in a 18 month period for a ~250 node installation with around 50 rules, 2 or 3 directives by rules. So we need to use a 64 bits int to not hit that rather low limit.

Since it's a big change, we will not fix it in our stable version but in a latest one (2.10), and give workaound with manual validation for other version.

More precissely, we are going to:

• Fix Scala code and database schema in 2.10.x (#4831)
  • So new installations will not have the problem anymore
  • That will have no impact on existing installation

• Add two scripts (#4832):
  • One that will only warn the user that their table is still using int if it's the case, and pointing to possible workaround
  • One that should be ran manually to migrate the database

This scripts will be provided with Rudder 2.10.1, but for other people, we need to have information to guide them toward the workarounds:

• Add an entry in the FAQ that will explain how to detect it, analyse it, fix the issue.

Note:

command used to get type of column:

psql -U rudder -h localhost -p 15432 -Atc "select data_type from information_schema.columns where table_name='archivedruddersysevents' and column_name='id';"