Actions
Bug #10642
closed
When Rudder starts, compliance takes a long time to display (blocked by recent changes?)
Added by Nicolas CHARLES about 7 years ago. Updated over 2 years ago.
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
When starting the Rudder app, with a lot (dozens of) millions) changes, compliance don't really get computed, as long as recent changes are not fetched
on the postgresql side, we see only one query for the changes, and nothing else
So, either the web interface is blocked because of this query, and can't compute further the compliance once it's done, or we have an issue with the connection pool, and only one query at a time active
Updated by François ARMAND about 7 years ago
- Subject changed from Query to get all recent changes seems to be blocking to When Rudder starts, compliance takes a long time to display (blockek by recent changes?)
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
Updated by François ARMAND about 7 years ago
- Subject changed from When Rudder starts, compliance takes a long time to display (blockek by recent changes?) to When Rudder starts, compliance takes a long time to display (blocked by recent changes?)
- Description updated (diff)
- Priority changed from 0 to 17
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.1.2 to 4.1.3
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.3 to 4.1.4
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.4 to 4.1.5
Updated by Alexis Mousset almost 7 years ago
- Target version changed from 4.1.5 to 4.1.6
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.6 to 4.1.7
- Priority changed from 32 to 31
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.7 to 4.1.8
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.8 to 4.1.9
- Priority changed from 31 to 30
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.9 to 4.1.10
- Priority changed from 30 to 29
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.10 to 4.1.11
- Priority changed from 29 to 28
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.11 to 4.1.12
- Priority changed from 28 to 27
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.12 to 4.1.13
Updated by Vincent MEMBRÉ almost 6 years ago
- Target version changed from 4.1.13 to 4.1.14
Updated by Benoît PECCATTE almost 6 years ago
- Target version changed from 4.1.14 to 4.1.15
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.15 to 4.1.16
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.16 to 4.1.17
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.17 to 4.1.18
- Priority changed from 27 to 0
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.1.18 to 4.1.19
Updated by Alexis Mousset over 5 years ago
- Target version changed from 4.1.19 to 4.1.20
Updated by François ARMAND about 5 years ago
- Target version changed from 4.1.20 to 4.1.21
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 4.1.21 to 4.1.22
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 4.1.22 to 4.1.23
Updated by Vincent MEMBRÉ almost 5 years ago
- Target version changed from 4.1.23 to 4.1.24
Updated by Vincent MEMBRÉ almost 5 years ago
- Target version changed from 4.1.24 to 588
Updated by Alexis Mousset almost 5 years ago
- Target version changed from 588 to 5.0.13
There has been some improvements in 5.0, but there part of the problem remains (e.g. global compliance is still not cached).
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.13 to 5.0.14
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.14 to 5.0.15
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.15 to 5.0.16
Updated by Alexis Mousset over 4 years ago
- Target version changed from 5.0.16 to 5.0.17
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 5.0.17 to 5.0.18
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 5.0.18 to 5.0.19
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 5.0.19 to 5.0.20
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 5.0.20 to 797
Updated by Benoît PECCATTE almost 3 years ago
- Target version changed from 797 to 6.1.14
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 6.1.14 to 6.1.15
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 6.1.15 to 6.1.16
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.16 to 6.1.17
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.17 to 6.1.18
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.18 to 6.1.19
Updated by François ARMAND over 2 years ago
- Status changed from New to Resolved
There was a lot of enhancement relative to compliance computation along the years. I'm closing that ticket and if we spot a specific problem on some case, we will open a new one.
Actions