External components (Clickhouse,PG, VM) improvements
General
Escalation
General
Escalation
Description
How to test
None
How to document
We need to list specific versions of supported external components (every release need)
How to share to users in RN - New section?
Activity
Show:
Nurlan Moldomurov February 12, 2024 at 9:41 AM
Duplicate
Details
Details
Assignee
Unassigned
UnassignedReporter
Nailya Kutlubaeva
Nailya KutlubaevaPriority
Labels
Needs QA
Yes
Needs Doc
Yes
Planned Version/s
Story Points
2
Parent
Smart Checklist
Open Smart Checklist
Smart Checklist

Open Smart Checklist
Created November 1, 2023 at 9:31 AM
Updated March 5, 2024 at 10:02 PM
Resolved February 12, 2024 at 9:41 AM
External Postgres issues:
PERCONA_TEST_POSTGRES_USERNAME but PERCONA_TEST_POSTGRES_DBPASSWORD. I think it should be PERCONA_TEST_POSTGRES_PASSWORD
Why PMM tries to use pmm-managed database as default? Database with such name can’t be created
External Clickhouse improvements:
Allow possibility to use external Clckhouse with username and password, now we have the only next variables for Clickhouse PERCONA_TEST_PMM_CLICKHOUSE_BLOCK_SIZE, PERCONA_TEST_PMM_CLICKHOUSE_DATASOURCE_ADDR, PERCONA_TEST_PMM_CLICKHOUSE_ADDR, (btw why do we have 2 these variables?) PERCONA_TEST_PMM_CLICKHOUSE_DATABASE, PERCONA_TEST_PMM_CLICKHOUSE_POOL_SIZE
And it was found that if PMM uses all external components, all internal components are still running (retest with env vars needed here to confirm).