[SERVER-9912] Client Application is receiving error connecting to mongo sharded cluster database Created: 12/Jun/13  Updated: 12/Jun/13  Resolved: 12/Jun/13

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 2.2.1
Fix Version/s: None

Type: Task Priority: Critical - P2
Reporter: Manjula Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS - CentOS release 6.2 (Final)

CPU - 6 core, 24 proc
MEM -94GB


Participants:

 Description   

Sharded Cluster , with 2 shards , each with 4 node replica set

shards:

{ "_id" : "rset001", "host" : "rset001/pnjctgmongo01:27101,pnjctgmongo02:27102,pwbctgmongo01:27103,pwbctgmongo02:27104" } { "_id" : "rset002", "host" : "rset002/pnjctgmongo03:27201,pnjctgmongo04:27202,pwbctgmongo03:27203,pwbctgmongo04:27204" }

 Comments   
Comment by Manjula [ 12/Jun/13 ]

This seems to be application related.

Closing the ticket for now.

Thanks
Manjula.

Comment by Manjula [ 12/Jun/13 ]

This is the error received by the Client

... 1 line omitted ...
com.mongodb.MongoException$Network: can't call something : pnjcldmongovip.barnesandnoble.com/161.221.214.214:27999/catalog
at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:227)
at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:305)
at com.mongodb.DBCursor._check(DBCursor.java:369)
at com.mongodb.DBCursor._hasNext(DBCursor.java:498)
at com.mongodb.DBCursor.hasNext(DBCursor.java:523)
at com.bn.cmservice.nosql.mongo.MongoServiceImpl.retrieveData(MongoServiceImpl.java:839)
at com.bn.cmservice.nosql.mongo.MongoServiceImpl.getIn(MongoServiceImpl.java:369)
... 52 lines omitted ...
at com.mongodb.DBPort.go(DBPort.java:119)
at com.mongodb.DBPort.call(DBPort.java:79)

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