[CDRIVER-683] Temporary write failure does not disconnect node Created: 20/May/15  Updated: 19/Oct/16  Resolved: 16/Sep/15

Status: Closed
Project: C Driver
Component/s: None
Affects Version/s: 1.2.0
Fix Version/s: 1.2-rc0

Type: Bug Priority: Major - P3
Reporter: Hannes Magnusson Assignee: Hannes Magnusson
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to CDRIVER-830 Exhaust cursors must destroy the stre... Closed
is related to CDRIVER-810 mongoc_cluster_disconnect_node() does... Closed

 Description   

I don't have a repro for this - discovered this hunting down another issue:

However, browsing the code - especially _mongoc_cluster_run_command() - you can see the expectation form mongoc_stream_writev() is the same as from _mongoc_buffer_append_from_stream(): disconnect from the node on failure.

There is only one caller of mongoc_stream_writev() that will explicitly disconnect the node: mongoc_cluster_sendv_to_server().



 Comments   
Comment by Githook User [ 11/Jan/16 ]

Author:

{u'username': u'bjori', u'name': u'Hannes Magnusson', u'email': u'bjori@php.net'}

Message: CDRIVER-683 & CDRIVER-810: Disconnect from a node properly

Even in single threaded mode
Branch: 1.3.0-dev
https://github.com/mongodb/mongo-c-driver/commit/11760f87794a9e2d7e35ccb379eb1e09e9a8e700

Comment by Githook User [ 26/Oct/15 ]

Author:

{u'username': u'bjori', u'name': u'Hannes Magnusson', u'email': u'bjori@php.net'}

Message: CDRIVER-683 & CDRIVER-810: Disconnect from a node properly

Even in single threaded mode
Branch: debian
https://github.com/mongodb/mongo-c-driver/commit/11760f87794a9e2d7e35ccb379eb1e09e9a8e700

Comment by Githook User [ 16/Sep/15 ]

Author:

{u'username': u'bjori', u'name': u'Hannes Magnusson', u'email': u'bjori@php.net'}

Message: CDRIVER-683 & CDRIVER-810: Disconnect from a node properly

Even in single threaded mode
Branch: 1.2.0-dev
https://github.com/mongodb/mongo-c-driver/commit/11760f87794a9e2d7e35ccb379eb1e09e9a8e700

Comment by A. Jesse Jiryu Davis [ 11/Aug/15 ]

Need a mock_server_t test, probably reproducible if you connect to a mock server, do a successful operation, and then mock_server_destroy the server and attempt another operation with the same socket.

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