Canonical Juju

Set "notablescan" on mongod in tests (and QA?)

Bug #1671720 reported by Andrew Wilkins
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
High
Unassigned

Bug Description

As suggested in https://bugs.launchpad.net/juju/+bug/1671258/comments/10, we should investigate passing --notablescan to mongod, to prevent queries that would perform a (slow/resource-intensive) collection scan. This should help to prevent future occurrences of bugs like lp:1671258.

Revision history for this message
Anastasia (anastasia-macmood) wrote :

As this is a tech-debt item, I am lowering its Importance.

Changed in juju:
milestone: 2.2-rc1 → none
importance: High → Low
Revision history for this message
William Grant (wgrant) wrote :

This would have revealed issues that caused numerous outages (some more than a day long!) on production systems. Is it really low priority?

Revision history for this message
Anastasia (anastasia-macmood) wrote :

No, it's not low priority if it affected production. The only indication of it's severity I had was it was tagged as "tech-debt". Consider tagging it as "canonical-is", please!

I'll put it back upto High. I doubt it will be addressed in the next milestone though.

Changed in juju:
importance: Low → High
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.

Changed in juju:
status: Triaged → Expired
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.