Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reindexing can sometimes run longer than expected #3478

Closed
TheWitness opened this issue Apr 19, 2020 · 0 comments
Closed

Reindexing can sometimes run longer than expected #3478

TheWitness opened this issue Apr 19, 2020 · 0 comments
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team resolved A fixed issue
Milestone
1.2.12

Comments

@TheWitness
Copy link
Member

Describe the bug

After noticing that a Re-Index was taking a very long time, it was found that during any one single Data Query Re-Index, Graphs and Data Sources for ALL Data Queries are re-evaluated/remapped leading to very long device Re-Index times.

To Reproduce

Steps to reproduce the behavior:

  1. Goto a Device with Many Data Queries and some with hundreds to thousands of rows

  2. Re-Index on a Data Query with only a few rows.

  3. Notice that the Re-Index takes an inordinate amount of time.

Expected behavior

Cacti should be performing optimal Re-Indexes
@TheWitness TheWitness added the bug Undesired behaviour label Apr 19, 2020
@TheWitness TheWitness added this to the 1.2.12 milestone Apr 19, 2020
TheWitness added a commit that referenced this issue Apr 19, 2020
@TheWitness
Fixing Issue #3478
9121e3a 
Data Query Re-Index is not optimal causing very long Re-Index times
@TheWitness TheWitness added the resolved A fixed issue label Apr 19, 2020
This was referenced Apr 22, 2020
Closed
Merged
@netniV netniV added the confirmed Bug is confirm by dev team label Apr 26, 2020
@netniV netniV changed the title Data Query Re-Index is not optimal causing very long Re-Index times Reindexing can sometimes run longer than expected May 3, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Aug 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team resolved A fixed issue
Projects
None yet
Milestone
1.2.12
Development

No branches or pull requests
2 participants
@TheWitness @netniV