Details
Major Description
Summary: I'm running an internal build (3516) of EE, and I'm seeing a large amount of memory being taken up by memcached and erl. I'm running a similar setup to releases of 6.x, where I never saw this kind of spike.
I have not yet had time to try and attach a debugger, but if I'm able to and when I get to it, I will update this ticket.
I've run cbcollect as requested when I brought this up in #engineering on Slack (Dave Rigby). However, the file is too big to attach (100mb limit), so I will try to figure out some other way to send this file (and update this ticket). UPDATE: Here's a WeTransfer link: https://we.tl/t-8dMptSTZU9 - this is only available for 7 days. I will keep the file on my local machine. If you need it after 7 days let me know and I will WeTransfer it again.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Trond Norbye [ trond ] | Daniel Owen [ owend ] |
| Description |
*Summary*: I'm running an internal build (3516) of EE, and I'm seeing a large amount of memory being taken up by memcached and erl. I'm running a similar setup to releases of 6.x, where I never saw this kind of spike.
I have not yet had time to try and attach a debugger, but if I'm able to and when I get to it, I will update this ticket. I've run cbcollect as requested when I brought this up in #engineering on Slack (Dave Rigby). However, the file is too big to attach (100mb limit), so I will try to figure out some other way to send this file (and update this ticket) |
*Summary*: I'm running an internal build (3516) of EE, and I'm seeing a large amount of memory being taken up by memcached and erl. I'm running a similar setup to releases of 6.x, where I never saw this kind of spike.
I have not yet had time to try and attach a debugger, but if I'm able to and when I get to it, I will update this ticket. I've run cbcollect as requested when I brought this up in #engineering on Slack (Dave Rigby). However, the file is too big to attach (100mb limit), so I will try to figure out some other way to send this file (and update this ticket). *UPDATE*: Here's a WeTransfer link: https://we.tl/t-8dMptSTZU9 |
| Description |
*Summary*: I'm running an internal build (3516) of EE, and I'm seeing a large amount of memory being taken up by memcached and erl. I'm running a similar setup to releases of 6.x, where I never saw this kind of spike.
I have not yet had time to try and attach a debugger, but if I'm able to and when I get to it, I will update this ticket. I've run cbcollect as requested when I brought this up in #engineering on Slack (Dave Rigby). However, the file is too big to attach (100mb limit), so I will try to figure out some other way to send this file (and update this ticket). *UPDATE*: Here's a WeTransfer link: https://we.tl/t-8dMptSTZU9 |
*Summary*: I'm running an internal build (3516) of EE, and I'm seeing a large amount of memory being taken up by memcached and erl. I'm running a similar setup to releases of 6.x, where I never saw this kind of spike.
I have not yet had time to try and attach a debugger, but if I'm able to and when I get to it, I will update this ticket. I've run cbcollect as requested when I brought this up in #engineering on Slack (Dave Rigby). However, the file is too big to attach (100mb limit), so I will try to figure out some other way to send this file (and update this ticket). *UPDATE*: Here's a WeTransfer link: [https://we.tl/t-8dMptSTZU9] - this is only available for 7 days. I will keep the file on my local machine. If you need it after 7 days let me know and I will WeTransfer it again. |
| Fix Version/s | Mad-Hatter [ 15037 ] |
| Sprint | KV-Engine MH Beta Refresh [ 872 ] |
| Rank | Ranked lower |
| Assignee | Daniel Owen [ owend ] |
| Assignee | Richard deMellow [ richard.demellow ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Attachment | screenshot-1.png [ 72441 ] |
| Attachment | image-2019-08-20-10-50-51-899.png [ 72442 ] |
| Attachment | screenshot-2.png [ 72516 ] |
| Attachment | image-2019-08-21-10-19-25-036.png [ 72517 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Attachment | screenshot-of-build-6.5.0-4130.png [ 72807 ] |
| VERIFICATION STEPS |
1. install Couchbase Server EE on Windows
2. Set up a one node cluster 3. Load beer-sample bucket 4. Use Process Explorer in admin mode to monitor memory usage of memcached.exe 5. perform a pillow-fight against the beer-sample bucket Memory used during the pillow-fight shouldn't grow constantly and instead should stabilise. |
|
| Status | Resolved [ 5 ] | Closed [ 6 ] |