[SERVER-37383] View resolution on mongos does not retry if a resolved namespace becomes a view Created: 28/Sep/18  Updated: 29/Oct/23  Resolved: 02/Oct/18

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: 4.1.4

Type: Bug Priority: Major - P3
Reporter: Nicholas Zolnierz Assignee: Nicholas Zolnierz
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Query 2018-10-08
Participants:
Linked BF Score: 22

 Description   

Retrying cluster commands for view resolution has been consolidated here, however this only retries once and so the resolved view error can make it back to the shell (which crashes).



 Comments   
Comment by Githook User [ 02/Oct/18 ]

Author:

{'name': 'Nick Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com', 'username': 'nzolnierzmdb'}

Message: SERVER-37383: View resolution on mongos does not retry if a resolved namespace becomes a view
Branch: master
https://github.com/mongodb/mongo/commit/17648f3539352e4395910600dd87ccb048bb2e36

Comment by Esha Maharishi (Inactive) [ 02/Oct/18 ]

Ah I see, yeah if the response format depends on the command, then it makes sense for the retry loop to be in each command.

Comment by Nicholas Zolnierz [ 02/Oct/18 ]

Interesting idea, though I don't think we'd want to retry for all types of commands? Also may be tricky since some commands have special response formatting (like count here).

Comment by Esha Maharishi (Inactive) [ 02/Oct/18 ]

Just a thought - Would it make sense to catch the "cannot run command on view" error in the top-level retry loop in mongos (where stale version errors are caught) and retry the command as an agg from there?

Generated at Thu Feb 08 04:45:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.