Incomplete Transactions and MgoPurge
anastasiamac edited this page Jul 26, 2016
·
9 revisions
Pages 44
- Home
- API best practices
- Azure provider design implementation notes
- Blocking bugs
- Bootstrap Internals (WIP)
- Boring Techniques
- Bug fixes and patching
- CI Tests
- Code Review Checklists
- Containers
- Creating New Repos
- Debugging Juju
- Debugging Juju Misc Topics Pointers
- Debugging Races
- Diagnosing MongoDB Performance
- Faster LXD
- Feature Documentation
- Getting Mongo dump
- Guidelines for writing workers
- Hacking upload tools
- howto: implement effective config structs
- Implementing environment providers
- Incomplete Transactions and MgoPurge
- Interactive Commands
- Intermittent failures
- Juju Logging
- Juju Scripts
- Juju Storage (WIP)
- Juju User Documentation
- KVM instance creation
- Login into MongoDB
- Managing complexity
- mgo txn example
- MgoPurgeTool
- Misc Topics
- Mongo Issues
- MongoDB and Consistency
- pprof facility
- Reviewboard Tips and Tricks
- Stop Start Machine Agent
- Stress Test
- Triaging Bugs
- Update Launchpad Dependency
- Writing Unit Tests
- Show 29 more pages…
Navigation
Testing
Releases
Documentation
Development
- READ BEFORE CODING
- Blocking bugs process
- Bug fixes and patching
- Contributing
- Code Review Checklists
- Creating New Repos
-
MongoDB and Consistency
- [mgo/txn Example] (https://github.com/juju/juju/wiki/mgo-txn-example)
- Scripts
- Update Launchpad Dependency
- Writing workers
- Reviewboard Tips
Debugging and QA
- Debugging Juju
- [Faster LXD] (https://github.com/juju/juju/wiki/Faster-LXD)
Clone this wiki locally
Symptom
cannot find transaction ObjectIdHex("..")
Solution
Before running the tool, please sanity check the system:
- Shut down machine agents on all state servers: stop machine agent;
- Make sure that MongoDB replicaset is in good state - on each state server, login into its MongoDB and find out database opinion on the health and status of replicaset by running
rs.status(). There should be one PRIMARY node on one of the state severs and the rest should be SECONDARY.
Run the mgopurge tool on any state server. You should get output of what the tool is doing. If you encounter any further problems, this output may be of value, please keep it handy.
After the tool is run, restart machine agents: start machine agent.
These instructions are adapted from mgopurge original one to cater for HA as well as different series.