Issues
- Improve error messages when chunk is too large.SE-82Resolved issue: SE-82Andrii Dema
- pmm-dump error importing data "failed to send HTTP request to victoria metrics: timeout goroutine_id=1"SE-81Resolved issue: SE-81
- pmm-dump stores PMM password within the archiveSE-80Resolved issue: SE-80Andrii Dema
- pmm-dump show meta doesn't report any information about servicesSE-79Resolved issue: SE-79Andrii Dema
- PMM-Dump sets time stamp to incorrect value in the dump fileSE-78Resolved issue: SE-78Andrii Dema
- MYRAM parameter documentationSE-77Resolved issue: SE-77Andrii Dema
- Option version requires connection string for PMMSE-76Resolved issue: SE-76Andrii Dema
- PMM 2.19 is not showing data after importing a pmm-transferer dumpSE-74Resolved issue: SE-74Andrii Dema
- Unable to import file created using pmm-dump export stdoutSE-73Resolved issue: SE-73Andrii Dema
9 of 9
Improve error messages when chunk is too large.
Done
General
Escalation
General
Escalation
Description
Environment
None
Smart Checklist
Details
Assignee
Andrii DemaAndrii DemaReporter
Agustin GallegoAgustin GallegoFix versions
Affects versions
Priority
Medium
Details
Details
Assignee
Andrii Dema
Andrii DemaReporter
Agustin Gallego
Agustin GallegoFix versions
Affects versions
Priority
MediumSmart Checklist
Smart Checklist
Smart Checklist
Created June 8, 2022 at 10:58 PM
Updated March 7, 2024 at 9:36 AM
Resolved June 27, 2022 at 6:41 AM
Activity
Sveta SmirnovaJune 10, 2022 at 11:52 PM
Thank you for the reasonable feature request.
This is linked to SE-47. When the tool fails to import due to the chunk being too large, it would be nice if the tool outputs some relevant messages on how to fix it. SE-47 has the workaround for it, so we should either print those as a useful message, or point to the relevant URL in which we can see how to fix it and successfully import the dump.