[SERVER-7447] Sharded legacy-static build goes into uninterruptible sleep on kernel 2.6.16 Created: 23/Oct/12 Updated: 11/Jul/16 Resolved: 28/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregor Macadam | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
https://groups.google.com/forum/?fromgroups=#!topic/mongodb-user/iKEK4ZISvSc These days, i need to scale out my single node mongodb service into a step1. start config process ) mongos> db.runCommand( {addshard:"10.163.138.88:10000"}) mongos> db.runCommand( { "enablesharding" : "query"}) mongos> db.runCommand({ "shardcollection" : "query.DailyPcQueryStats", And i test the 2 machines as stand-alone mongodb service. And i almost And i test like this: I start all mongodb cluster processes on 1 machine( |
| Comments |
| Comment by Stennie Steneker (Inactive) [ 28/Oct/13 ] |
|
Closing as per last comment on Google Groups:
|
| Comment by Eliot Horowitz (Inactive) [ 10/Jan/13 ] |
|
The legacy-static build is a bit odd because its statically linked. |