(bcc'd to onap-discuss for visibility on the reply and redirected to onap-tsc)
No Gary it was not implemented and since your email popped up as I was getting to send an update about this, I'll just use it as a reply. 😊 There was insufficient input from the TSC for us to follow through with the down time this morning. As such we are now targeting Thursday morning for this downtime. While granted the request was sent out late afternoon Pacific time, when I last checked my email at 10PM there had been 5 responses. I was expecting to find additional input over night from TSC Members in Asia, Europe and a couple from the East Coast when I checked again at 5AM this morning, but there were none. Unless we hear a specific "NO" from TSC Members we will proceed with the down time tomorrow to keep from holding up the Community. Best Regards, -kenny Kenny Paul, Technical Program Manager, The Linux Foundation [email protected], 510.766.5945 San Francisco Bay Area, Pacific Time Zone From: Gary Wu <[email protected]> Date: Wednesday, May 2, 2018 at 10:49 AM Has this nexus3 change been implemented? Thanks, Gary From: [email protected] [mailto:[email protected]] On Behalf Of Kenny Paul Sent: Tuesday, May 01, 2018 4:47 PM To: onap-tsc <[email protected]> Cc: Anil Belur <[email protected]>; Jeremy Phelps <[email protected]> Subject: [onap-tsc] TSC MEMBERS Approval/Acknowledgment Needed- Requesting Nexus3 downtime Importance: High (bcc'd to onap-release to avoid cross posting) When: Requesting May 2nd, 6:00 am to 7:00 am Pacific, Alternative: May 3, 6:00 am to 7:00 am Pacific What: Increasing ONAP's Nexus3 server's heap size to 6 gig and enable additional logging Why: Based upon a meeting today between the Community and LFIT - Part of ongoing work to address performance issues pulling docker images Impact: Jenkins and Nexus3 will be unavailable during this time Risk: Low Background: Docker image pulls are subject to hanging in mid-stream for minutes at a time. A recent network fix on the part of our service provider has addressed bandwidth issues which were contributing to this behavior, however with one bottleneck removed a new issue has been identified. It is believed that the jobs are pausing whenever normal garbage collection tasks are triggered. The most likely cause of this is the result of the heap size being set to default values which is not taking full advantage of the memory available. This change will set the heap size to match what is currently in place for ONAP's Nexus2 server. During this down time logging will also be enabled to track additional system information in the event that the planned fix does not correct the problem. Alternative: Leave system as-is until after the release Best Regards, -kenny Kenny Paul, Technical Program Manager, The Linux Foundation [email protected], 510.766.5945 San Francisco Bay Area, Pacific Time Zone
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
