Jira (PDB-5255) Update to new tk-jetty9 version to enable TLSv1.3 by default
Title: Message Title Molly Waggett updated an issue PuppetDB / PDB-5255 Update to new tk-jetty9 version to enable TLSv1.3 by default Change By: Molly Waggett Epic Link: PE-28367 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413568.1630005756000.118096.1630020060087%40Atlassian.JIRA.
Jira (PDB-5255) Update to new tk-jetty9 version to enable TLSv1.3 by default
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-5255 Update to new tk-jetty9 version to enable TLSv1.3 by default Issue Type: Improvement Assignee: Unassigned Created: 2021/08/26 12:22 PM Priority: Normal Reporter: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/pup
Jira (PDB-5254) Initial blocking sync reporting unexpected error
Title: Message Title
Austin Blatt created an issue
PuppetDB / PDB-5254
Initial blocking sync reporting unexpected error
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/08/26 10:45 AM
Priority:
Normal
Reporter:
Austin Blatt
2021-08-23T01:58:35.183-07:00 ERROR [p.p.threadpool] Reporting unexpected error from thread initial-sync-4 to stderr and log
clojure.lang.ExceptionInfo: Output of update-for-command does not match schema:
[0;33m {:entity-status {:factsets {:phase missing-required-key}}} [0m
at puppetlabs.pe_puppetdb_extensions.sync.status$eval55307$update_for_command
Jira (PUP-11232) freeze string in the prime candidates files
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-11232 freeze string in the prime candidates files Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413213.1629801903000.117443.1629993060667%40Atlassian.JIRA.
Jira (PDB-5252) Determine size impact of trigram indexes on facts
Title: Message Title Andrei Filipovici commented on PDB-5252 Re: Determine size impact of trigram indexes on facts After that I deleted all the GIN indexes, run a vacuum full and recreated all indexes as GIST. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413371.1629877927000.117345.1629988140145%40Atlassian.JIRA.
Jira (PDB-5252) Determine size impact of trigram indexes on facts
Title: Message Title Andrei Filipovici commented on PDB-5252 Re: Determine size impact of trigram indexes on facts After I started PDB the sandbox shrunk to 22729 mb / 23832150982 bytes. After adding the remaining 9 indexes the sandbox size was 22766 mb / 23871586932 bytes. Total indexes size on table factsets was 151 mb / 158687232 bytes. Individual index size was: relation |size ---+ public.idx_factsets_jsonb_merged | 90 MB public.factsets | 37 MB public.factsets_hash_expr_idx | 8848 kB public.factsets_operating_system_idx | 7312 kB public.factsets_fqdn_idx | 5112 kB public.factsets_os_family_idx | 4840 kB public.factsets_system_uptime_idx | 4824 kB public.factsets_virtual_idx | 4712 kB public.factsets_puppetversion_idx | 4680 kB public.factsets_kernel_idx
Jira (PDB-5252) Determine size impact of trigram indexes on facts
Title: Message Title Andrei Filipovici updated an issue PuppetDB / PDB-5252 Determine size impact of trigram indexes on facts Change By: Andrei Filipovici Summary: Determine size impact of trigram index indexes on facts Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413371.1629877927000.117237.1629977220037%40Atlassian.JIRA.
Jira (PDB-5253) Investigate if we can add indexes on nested facts
Title: Message Title Andrei Filipovici updated an issue PuppetDB / PDB-5253 Investigate if we can add indexes on nested facts Change By: Andrei Filipovici Summary: Investigate if we can we add indexes on nested facts Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413374.1629878715000.117235.1629977160044%40Atlassian.JIRA.
Jira (PDB-5252) Determine size impact of trigram index on facts
Title: Message Title Andrei Filipovici updated an issue PuppetDB / PDB-5252 Determine size impact of trigram index on facts Change By: Andrei Filipovici Summary: Determine size impact of trigram index on facts size impact Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413371.1629877927000.117236.1629977160229%40Atlassian.JIRA.
Jira (PDB-3715) PuppetDB doesn't complete shutdown after migration fails
Title: Message Title Andrei Filipovici updated an issue PuppetDB / PDB-3715 PuppetDB doesn't complete shutdown after migration fails Change By: Andrei Filipovici Release Notes: Not Needed Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.216460.1508186567000.117218.1629976800031%40Atlassian.JIRA.
Jira (PDB-3715) PuppetDB doesn't complete shutdown after migration fails
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici PuppetDB / PDB-3715 PuppetDB doesn't complete shutdown after migration fails Change By: Andrei Filipovici Assignee: Andrei Filipovici Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.216460.1508186567000.117217.1629976740160%40Atlassian.JIRA.
Jira (PDB-3715) PuppetDB doesn't complete shutdown after migration fails
Title: Message Title Andrei Filipovici commented on PDB-3715 Re: PuppetDB doesn't complete shutdown after migration fails This bug is no longer reproducible. Tested it with PuppetDB version 7.9.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.216460.1508186567000.117200.1629976620026%40Atlassian.JIRA.
Jira (PDB-5253) Investigate if we can we add indexes on nested facts
Title: Message Title Andrei Filipovici updated an issue PuppetDB / PDB-5253 Investigate if we can we add indexes on nested facts Change By: Andrei Filipovici Attachment: query_plan_local.json Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413374.1629878715000.117193.1629976140031%40Atlassian.JIRA.
Jira (PDB-5253) Investigate if we can we add indexes on nested facts
Title: Message Title Andrei Filipovici commented on PDB-5253 Re: Investigate if we can we add indexes on nested facts We can use the nested index from PDB if we use the dotted projections on the inventory endpoint. An example would be: ["~", "facts.os.lsb.distid", "MND.*"] The query plan for the above query is in the attachement. If we use the fact-contents endpoint with a query like this: ["and", ["=", "path", ["os", "lsb", "distid"]], ["~", "value", "MND.*"]] the index will not be used. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PDB-5253) Investigate if we can we add indexes on nested facts
Title: Message Title Andrei Filipovici commented on PDB-5253 Re: Investigate if we can we add indexes on nested facts Used this query with explain analyze for the nested fact os.lsb.distid: EXPLAIN analyse select (stable||volatile->'os'->'lsb'->>'distid') from factsets where ((stable||volatile)->'os'->'lsb'->>'distid') ~ '.*MND'; The result shows it performed a sequencial scan: Seq Scan on factsets (cost=0.00..50.22 rows=72 width=32) (actual time=1.850..34.532 rows=1 loops=1) Filter: (stable || volatile) -> 'os'::text) -> 'lsb'::text) ->> 'distid'::text) ~ '.*MND'::text) Rows Removed by Filter: 999 Planning time: 3.502 ms Execution time: 34.757 ms After that I created an index for that fact with: CREATE INDEX dist_id_values_idx ON factsets USING GIN (((stable||volatile)->'os'->'lsb'->>'distid') gin_trgm_ops); Running the same explain analyse query resulted:
Jira (PDB-5253) Investigate if we can we add indexes on nested facts
Title: Message Title Bogdan Irimie assigned an issue to Andrei Filipovici PuppetDB / PDB-5253 Investigate if we can we add indexes on nested facts Change By: Bogdan Irimie Assignee: Andrei Filipovici Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413374.1629878715000.117123.1629962160044%40Atlassian.JIRA.
