[CDRIVER-3694] Failure to decompress is handled inconsistently Created: 30/May/20  Updated: 31/Mar/22

Status: Backlog
Project: C Driver
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Kevin Albertson Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

A failure to decompress an OP_COMPRESSED message is inconsistently considered a network error.

mongoc_cluster_try_recv and mongoc_cluster_run_command_opquery does not consider it a network error.

mongoc_cluster_run_opmsg considers it a network error, and run through the network error logic (close the application connection, and if the generation is not stale, mark the server unknown and clear the pool).

I'm not sure under what situations there could be a failure to decompress an OP_COMPRESSED message. That needs to be answered. Whatever the answer is, the behavior should be consistent.


Generated at Wed Feb 07 21:18:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.