Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title Charlie Sharpsteen commented on PDB-3879 Re: node-purge-ttl setting not working in 2017.3 Ah, I misread this the first time — thought the problem was that the node was not getting purged from search results, when the issue is that the node is getting purged from search results too quickly. I believe this is actually expected behavior. PE 2017.2 shipped PuppetDB 4.4 and 2017.3 shipped PuppetDB 5.1. One of the changes that happened between the 4.4 and 5.1 major version break was that the /pdb/query/v4 endpoint no longer returns results from expired or deactivated nodes by default: https://puppet.com/docs/puppetdb/5.2/release_notes.html#section-6 Daniel Mcilhagga Does the query work as expected if node_state = "inactive" is used instead of expired is not null or deactivated is not null ? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title Charlie Sharpsteen assigned an issue to Daniel Mcilhagga PuppetDB / PDB-3879 node-purge-ttl setting not working in 2017.3 Change By: Charlie Sharpsteen Assignee: Daniel Mcilhagga Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title Daniel Mcilhagga assigned an issue to Unassigned PuppetDB / PDB-3879 node-purge-ttl setting not working in 2017.3 Change By: Daniel Mcilhagga Assignee: Daniel Mcilhagga Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title Charlie Sharpsteen commented on PDB-3879 Re: node-purge-ttl setting not working in 2017.3 Daniel Mcilhagga The node-purge-ttl is only enforced during a PuppetDB garbage collection sweep. These can be resource intensive, so they don't happen continuously. By default, one happens at startup and then every 60 minutes afterwards, configurable via gc-interval in database.ini. Does the node disappear if you trigger a GC sweep by restarting pe-puppetdb? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title Charlie Sharpsteen assigned an issue to Daniel Mcilhagga PuppetDB / PDB-3879 node-purge-ttl setting not working in 2017.3 Change By: Charlie Sharpsteen Assignee: Daniel Mcilhagga Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title
Daniel Mcilhagga updated an issue
PuppetDB / PDB-3879
node-purge-ttl setting not working in 2017.3
Change By:
Daniel Mcilhagga
In 2017.2 when a node was marked as expired or deactivated it but node-purge-ttl wasn't invoked, it will was still searchable by using:{code:java} curl -X GET http://localhost:8080/pdb/query/v4 --data-urlencode 'query=nodes { expired is not null or deactivated is not null }' | python -m json.tool {code}Since 2017.3.*, if the node-purge-ttl setting is set to 0s (or any value) it will not be respected and the data is purged from the DB instantly. Running the above query does not display any results and any queries searching for all nodes so not show the nodes in question.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title
Daniel Mcilhagga created an issue
PuppetDB / PDB-3879
node-purge-ttl setting not working in 2017.3
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/03/21 6:38 AM
Priority:
Normal
Reporter:
Daniel Mcilhagga
In 2017.2 when a node was marked as expired or deactivated it but node-purge-ttl wasn't invoked, it will still searchable by using:
curl -X GET http://localhost:8080/pdb/query/v4 --data-urlencode 'query=nodes { expired is not null or deactivated is not null }' | python -m json.tool
Since 2017.3.*, if the node-purge-ttl setting is set to 0s (or any value) it will not be respected and the data is purged from the DB instantly. Running the above query does not display any results and any queries searching for all nodes so not show the nodes in question.
Add Comment
