[DOCS-8096] Comment on: "HTTP REST interface on MongoDB 2.4.8" Created: 13/Jun/16 Updated: 30/Oct/23 Resolved: 03/Mar/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Docs Collector User (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
PROD Location: https://docs.mongodb.com/manual/reference/limits/ |
||
| Participants: | |
| Days since reply: | 48 weeks, 5 days ago |
| Description |
|
The Simple REST Api call returns less records compared to the unix db.users.count(). Apparently the REST call returns 48,955 and unix db count for same "users" object returns 52500. When we run the REST url on Chrome, we notice : 11:56:07.580 [websvr] Socket http response send() errno:32 Broken pipe error. Assuming this is something to do with socket timeout setting that can be increased so the REST output accomadates all 52000 odd records. Please advise if there is any config that we can manage the timeout value. |
| Comments |
| Comment by Ashley Brown [ 03/Mar/23 ] |
|
MongoDB 2.4 is EOL |