[SERVER-6581] mongos GLE needs to report errmsg when sub-GLE commands error on shard/shards Created: 24/Jul/12  Updated: 11/Jul/16  Resolved: 07/Aug/12

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 2.2.0-rc1

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Mathias Stearn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-6639 getLastError to Mongos gives an empty... Closed
Related
related to JAVA-593 NullPointerException at com.mongodb.W... Closed
Operating System: ALL
Participants:

 Description   

We warn in the logs when this happens, but we don't actually report an error message.



 Comments   
Comment by auto [ 07/Aug/12 ]

Author:

{u'date': u'2012-08-07T06:27:04-07:00', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}

Message: SERVER-6516, SERVER-6581 adapt shard_gle_insert.js to changed strings

The "err" strings sent for socket exceptions have been enhanced,
but jstests/sharding/shard_gle_insert.js was expecting the old
strings. Different OSes report different errors on socket failures,
so just require that they begin with "socket exception" and don't
check the rest of the message.
Branch: master
https://github.com/mongodb/mongo/commit/71338264726c7e0815e8799197ecf68af2aff939

Comment by Eric Milkie [ 07/Aug/12 ]

I think you broke a gle Windows unit test with that last commit:

Unit test failure -- received response from getLastError:
	"err" : "socket exception [SEND_ERROR] for 127.0.0.1:30001",
	"code" : 9001,
	"n" : 0,
	"ok" : 1
{
assert failed

http://buildlogs.mongodb.org/build/502078d6d2a60f1327000368/test/5020aefcd2a60f3689000242/

Comment by auto [ 06/Aug/12 ]

Author:

{u'date': u'2012-08-06T10:15:08-07:00', u'email': u'mathias@10gen.com', u'name': u'Mathias Stearn'}

Message: Use names rather than numbers in SocketException SERVER-6516 SERVER-6581
Branch: master
https://github.com/mongodb/mongo/commit/61b1e6cbad741a72b78f54f6330cb05895b95d7b

Comment by auto [ 06/Aug/12 ]

Author:

{u'date': u'2012-08-06T09:58:27-07:00', u'email': u'mathias@10gen.com', u'name': u'Mathias Stearn'}

Message: SERVER-6581 test that error messages are reported when GLE command fails

Written by greg
Branch: master
https://github.com/mongodb/mongo/commit/7eaba0fa4a1dd0dfd4594223efc5525003ce2d6e

Comment by auto [ 06/Aug/12 ]

Author:

{u'date': u'2012-08-06T09:54:15-07:00', u'email': u'mathias@10gen.com', u'name': u'Mathias Stearn'}

Message: SERVER-6581 report error message in gle when the command itself fails

Written by greg
Branch: master
https://github.com/mongodb/mongo/commit/6cc98c3fcc9ce25bfaa33512f3c8a55095acbd5a

Comment by auto [ 06/Aug/12 ]

Author:

{u'date': u'2012-08-06T09:46:25-07:00', u'email': u'mathias@10gen.com', u'name': u'Mathias Stearn'}

Message: SERVER-6516 SERVER-6581 better reporting in GLE codepaths

Written by greg
Branch: master
https://github.com/mongodb/mongo/commit/02a1bd5afdd4baf1029b27c32d3a73c0c8023814

Generated at Thu Feb 08 03:12:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.