You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the bulk walk size is set to -1, it should auto-detect, but in the latest release, the bulk_walk_size never changes from -1 to the optimum vavelue.
To Reproduce
Steps to reproduce the behavior:
Update your devices to bulk walk auto-detect -1 "UPDATE host SET bulk_walk_size=-1"
Force a Re-Index of all devices "poller_reindex_hosts.php --id=all --qid=all --debug"
Note that the bulk_walk_size has not reset to the detected value "SELECT bulk_walk_size, count(*) AS hosts FROM host GROUP BY bulk_walk_size"
Expected behavior
Cacti should default the 'bulk_walk_size' to 0.
The text was updated successfully, but these errors were encountered:
TheWitness
changed the title
When running reindexes the Cacti Device bulk walk size does not shift from -1 to the best size
The default 'bulk_walk_size' is -1 which means a device will never find it's optimal bulk walk size
Aug 13, 2023
The default 'bulk_walk_size' is -1 which means a device will never find it's optimal bulk walk size
netniV
changed the title
The default 'bulk_walk_size' is -1 which means a device will never find it's optimal bulk walk size
When a bulk walk size is set to automatic, this is not always set to the optimal value
Sep 3, 2023
Describe the bug
When the bulk walk size is set to -1, it should auto-detect, but in the latest release, the bulk_walk_size never changes from -1 to the optimum vavelue.
To Reproduce
Steps to reproduce the behavior:
Update your devices to bulk walk auto-detect -1 "UPDATE host SET bulk_walk_size=-1"
Force a Re-Index of all devices "poller_reindex_hosts.php --id=all --qid=all --debug"
Note that the bulk_walk_size has not reset to the detected value "SELECT bulk_walk_size, count(*) AS hosts FROM host GROUP BY bulk_walk_size"
Expected behavior
Cacti should default the 'bulk_walk_size' to 0.
The text was updated successfully, but these errors were encountered: