- 
    Type:Bug 
- 
    Resolution: Fixed
- 
    Priority:Major - P3 
- 
    Affects Version/s: None
- 
    Component/s: None
- 
        Sharding EMEA
- 
        Fully Compatible
- 
        ALL
- 
        v7.1
- 
        Sharding EMEA 2023-10-02
- 
        42
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
After fixing FSM error reporting in SERVER-81007, the agg_graph_lookup workload began failing with the following error(s):
[fsm_workload_test:agg_graph_lookup] uncaught exception: Error: 4 threads with tids [5,7,8,9] threw [fsm_workload_test:agg_graph_lookup] [fsm_workload_test:agg_graph_lookup] Foreground jstests/concurrency/fsm_workloads/agg_graph_lookup.js [fsm_workload_test:agg_graph_lookup] Error: [640570] != [175] are not equal [fsm_workload_test:agg_graph_lookup] [fsm_workload_test:agg_graph_lookup] doassert@src/mongo/shell/assert.js:20:14 [fsm_workload_test:agg_graph_lookup] assert.eq@src/mongo/shell/assert.js:176:17 [fsm_workload_test:agg_graph_lookup] getQueryResults@/data/mci/46ca11bf285ecfebbdaf8a92b7afbe95/src/jstests/concurrency/fsm_workloads/agg_graph_lookup.js:40:32 [fsm_workload_test:agg_graph_lookup] query@/data/mci/46ca11bf285ecfebbdaf8a92b7afbe95/src/jstests/concurrency/fsm_workloads/agg_graph_lookup.js:49:25 [fsm_workload_test:agg_graph_lookup] runFSM@/data/mci/46ca11bf285ecfebbdaf8a92b7afbe95/src/jstests/concurrency/fsm_libs/fsm.js:157:20 [fsm_workload_test:agg_graph_lookup] @eval:8:19 [fsm_workload_test:agg_graph_lookup] main@/data/mci/46ca11bf285ecfebbdaf8a92b7afbe95/src/jstests/concurrency/fsm_libs/worker_thread.js:229:23
(full log)
- depends on
- 
                    SERVER-81335 Query operations that avoid going through the network when a shard is targeting only itself should create a fresh operation context -         
- Open
 
-         
- related to
- 
                    SERVER-81007 FSM workloads no longer fail when $config.states functions throw exceptions -         
- Closed
 
-