Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13197

Investigate changes in SERVER-38691: serverInfo not present in explain output for aggregation

      Description

      Downstream Change Summary

      Previously, an aggregation explain plan would sometimes not include serverInfo; this has been fixed.

      Also, for a sharded explain plan, we previously only included the serverInfo for each shard. Now we also include the serverInfo for the mongos. (https://docs.mongodb.com/manual/reference/explain-results/index.html#serverinfo)

      Description of Linked Ticket

      Explain output for find commands include a  serverInfo object that contains version information:

      > db.foo.explain().find().finish().serverInfo
      {
      	"host" : "MacBook-Pro.local",
      	"port" : 27017,
      	"version" : "4.1.4",
      	"gitVersion" : "2f4b5918497b09a226a3ec5dcff930edd52ea1e9"
      } 

      However, this information is not available for aggregation commands:

      > db.foo.explain().aggregate([])
      {
      	"stages" : [
      		{
      			"$cursor" : {
      				"query" : {
      					
      				},
      				"queryPlanner" : {
      					"plannerVersion" : 1,
      					"namespace" : "test.foo",
      					"indexFilterSet" : false,
      					"parsedQuery" : {
      						
      					},
      					"queryHash" : "8B3D4AB8",
      					"winningPlan" : {
      						"stage" : "COLLSCAN",
      						"direction" : "forward"
      					},
      					"rejectedPlans" : [ ]
      				}
      			}
      		}
      	],
      	"ok" : 1
      } 

      This would be helpful to include for more complete information when troubleshooting .

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

            Assignee:
            jeffrey.allen@mongodb.com Jeffrey Allen
            Reporter:
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              3 years, 46 weeks, 3 days ago