[SERVER-20469] FSM tests - capability to run more than one instance at the same time Created: 17/Sep/15  Updated: 15/Oct/15  Resolved: 07/Oct/15

Status: Closed
Project: Core Server
Component/s: Concurrency, Testing Infrastructure
Affects Version/s: 3.1.8
Fix Version/s: 3.2.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: Jonathan Abrahams
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-19529 FSM tests - add cleanupOptions for ru... Closed
Backwards Compatibility: Fully Compatible
Sprint: TIG 9 (09/18/15), TIG A (10/09/15)
Participants:

 Description   

The FSM test suite is now being used for other purposes:

  • Powercycle testing
  • Backup/restore
  • Upgrade/downgrade

It provides very good coverage of many DB operations.

Issues that limits invoking the suite to run against a MongoDB cluster more than one at a time include:

  • Database names may conflict
    • Some database names are created in the workload, others are assigned from a global function
  • Database cleanup
  • Resource limitations
    • Too many open files
    • Too much disk space
    • Too much memory

This task will eliminate any database naming conflicts and add a cleanup option to ensure that the database cleanup is done only for those that were created by the FSM test harness.



 Comments   
Comment by Githook User [ 07/Oct/15 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-20469 FSM tests - capability to run more than one instance at the same time using a dbNamePrefix executionOption
Branch: master
https://github.com/mongodb/mongo/commit/a1b78e4835486f19262a6673c210092dea8ca7e1

Comment by Jonathan Abrahams [ 18/Sep/15 ]

The parallel mode provides some of this functionality, but is limited in the way it works as the workloads run in sets, not completely independently of each other.

Generated at Thu Feb 08 03:54:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.