[SERVER-32049] significant performance degradation on mongo server with ~140K collections Created: 21/Nov/17 Updated: 06/Dec/22 Resolved: 12/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.2.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Avraham Apelbaum | Assignee: | Backlog - Triage Team |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | collections, wiredtiger | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Triage
|
| Participants: |
| Description |
|
Hi, Another question: By default mongo closes FDs after 28hrs by default, except for the startup options `file_manager=(close_idle_time=300)` is there any "dynamic" parameter . we can use ? Or maximum number of open files is 265000 Br |
| Comments |
| Comment by Ramon Fernandez Marina [ 12/Feb/18 ] | |
|
tapuhi, we haven't heard back from you for a long time, so I'm going to close this ticket. If this is still an issue for you please feel free to comment here. Thanks, | |
| Comment by Bruce Lucas (Inactive) [ 21/Nov/17 ] | |
|
Hi Avraham, We have made improvements in 3.4 in workloads with a large number of tables (see You can change the WiredTiger engine configuration dynamically using setParameter, e.g.
Bruce | |
| Comment by Avraham Apelbaum [ 21/Nov/17 ] | |
|
I forgot to mention we use WireTiger as storage engine. |