# Updating to Nexus 3.23.0 causes 100% CPU load with GC

**URL:** <https://community.sonatype.com/t/updating-to-nexus-3-23-0-causes-100-cpu-load-with-gc/4137>\
**Category:** Sonatype Nexus Repository\
**Created:** [May 7, 2020, 8:07am UTC](https://community.sonatype.com/t/updating-to-nexus-3-23-0-causes-100-cpu-load-with-gc/4137 "2020-05-07T08:07:34Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![ado](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/ado/32/769_2.png) [@ado](https://community.sonatype.com/u/ado)\
**Post date:** [May 7, 2020, 8:07am UTC](https://community.sonatype.com/t/updating-to-nexus-3-23-0-causes-100-cpu-load-with-gc/4137/1 "2020-05-07T08:07:34Z")

</div>

Hello!  
Yesterday, at night, we’ve updated our docker instance of Nexus to 3.23.0  
In the morning when developers start to trigger they build and requests go to Nexus we have see the following:  
Log message:  
`2020-05-07 07:25:29,543+0000 INFO [elasticsearch[97E976DC-49B0040B-E218D207-BCD3BD80-233B626D][scheduler][T#1]] *SYSTEM org.elasticsearch.monitor.jvm - [97E976DC-49B0040B-E218D207-BCD3BD80-233B626D] [gc][old][5032][29] duration [5s], collections [1]/[5.3s], total [5s]/[44s], memory [2.6gb]->[2.6gb]/[3.9gb], all_pools {[young] [1.2mb]->[23.9mb]/[1.1gb]}{[survivor] [0b]->[0b]/[119mb]}{[old] [2.6gb]->[2.6gb]/[2.6gb]}`

At this moment CPU was at 100% load.

 ![Screenshot from 2020-05-07 12-55-18](https://canada1.discourse-cdn.com/flex047/uploads/communitysonatype/original/2X/c/c4b314d5891ebf446f9931c6cd09c98b49f36dc6.png)  
Interesting moment that nexus have a huge amount of RAM free…

After that web-interface kick off anyone with error “server disconnected”

File descriptors starts to grow:

 ![Screenshot from 2020-05-07 12-55-08](https://canada1.discourse-cdn.com/flex047/uploads/communitysonatype/original/2X/4/40eaa686fd80cae5a8b87639ff67e19d80599ebf.png)

Server doesn’t do anything. No logs, no responses, nothing. The last log string was about starting GC.

After restarting Nexus all goes fine for about 2 hours and repeats again.

Our memory settings for jvm is next:

```auto
-Xms4G 
-Xmx4G 
-XX:MaxDirectMemorySize=17530M

```

Followed by official documentation: [Sonatype Nexus Repository System Requirements](https://help.sonatype.com/repomanager3/system-requirements#SystemRequirements-Memory)

For the experiment for now we extend the XMS and XMX to 5G.

Does some of GC settings changes in this release?  
I did not find anything about that in Release Notes.  
Any advise or workaround to fix that? If a minor increase of XMS and XMX don’t solve the problem we will go back to the previous version.

May be this is not a best place for such question, so I’ve created a ticket: [What Happened To issues.sonatype.org? - Documentation](https://issues.sonatype.org/browse/NEXUS-23826)

---

_[View the full topic](https://community.sonatype.com/t/updating-to-nexus-3-23-0-causes-100-cpu-load-with-gc/4137)._