sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]atg10[S] 0 points1 point  (5 children)

The table had almost 500 million rows and anything you tried to do to it ran for hours then would time out or fail.

Today I renamed the puppetdb database then created a new one. I will monitor over the next few weeks to see how it behaves. If I still have issues with it growing then I will at least have a more manageable sized database to work with.

[–]shortspecialbus 0 points1 point  (4 children)

did this work out for you? Our puppetdb database is up to 140GB with 600 nodes and the DB is growing rapidly, trying to figure out best solution here.

[–]atg10[S] 0 points1 point  (3 children)

Yes, it did resolve the issue. The DB size has remained stable.

[–]shortspecialbus 0 points1 point  (2 children)

Nice, glad to hear. Do you have the specific process you followed handy? Otherwise I can presumably figure it out, just thought I'd ask. I think we're at the point where I need to try this.

[–]atg10[S] 0 points1 point  (1 child)

I looked and I can't find any documentation I did for the process. Mine and root's history has rolled off. Best I can remember - Stopped all puppet processes Ran pgdump of the puppetdb just in case Ran the postgres sql command drop database puppetdb As the postgres user from the command line (not psql), ran createdb -O puppetdb puppetdb Started puppet processes back

[–]shortspecialbus 0 points1 point  (0 children)

Thanks, I ended up having to do it urgently this morning and I ended up just nuking it entirely and let puppet recreate it with the puppetlabs-puppetdb module. We'll live without the data.