[PMM-1943] MongoDb QAN doesn't show new queries beause of CappedPositionLost error - Percona JIRA

XML

Word

Printable

Details

Type: Improvement
Status: Done
Priority: Medium
Resolution: Cannot Reproduce
Affects Version/s: 1.6.0
Fix Version/s: None
Component/s: QAN Agent
Labels:
None

Description

For some reason MongoDb QAn stopped fetching queries…
I checked QAN status and found an error:
"

getMore executor error: CappedPositionLost: CollectionScan died due to position in capped collection being deleted. Last seen record id:

I executed some commands suggested by Adamo:

use <yourdb>
db.getProfilingLevel()
db.setProfilingLevel(0)
db.system.profile.drop()

After that the error was dissapeared, I generated some new data, then checked Mongo QAN - No new data :disappointed:
I also restarted all services, but it didn’t help..
In pmm-mongo-queries.log:

2018/01/18 09:37:04.072763 WARNING data-sender Removed qan_1516268220061001909 because API returned 400: data.GetData: gzip: invalid header
2018/01/18 09:37:04.080111 WARNING data-sender Removed qan_1516268220068944599 because API returned 400: data.GetData: unexpected EOF
2018/01/18 09:47:34.077586 WARNING data-sender Removed qan_1516268820012313482 because API returned 400: data.GetData: gzip: invalid header

Attachments

Issue Links

relates to

PMM-1660 QAN for MongoDB not showing Data.

Done

PMM-3107 QAN - API returned 400

Done

PMM-4522 "CollectionScan died due to position in capped collection being deleted" error in pmm-agent.log for Mongodb

Done

mentioned in: Page Loading...; Page Loading...; Page Loading...

(1 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Nailya Kutlubaeva

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 18/Jan/18 10:07 AM

Updated:: 20/Dec/19 7:19 AM

Resolved:: 20/Dec/19 7:19 AM

Time Tracking

Estimated:

Not Specified

Remaining: