This message was deleted.
# puppet-enterprise
s
This message was deleted.
m
yeah the orchestrator has its own “prune” this is specifically for the classifier, puppet_enterprise:profileorchestrator:job_prune_threshold
b
yep. And current PE 2019.8.12 has a bug where the prune in the orchestrator works only during service restart, that all makes it a bit confusing.
m
the classifier one just seems to delete anything over the threshold from the node_check_ins table
in the classifierdb
b
ah good to know, thanks
m
classifier_node_check_in_storage is off by default now so that prune wont ever have any work either
b
yep. We currently have that enabled in our test env to see how it effects the database performance
m
ah! hence the questions 🙂