# Nexus Repository Manager HA-C issues

**URL:** <https://community.sonatype.com/t/nexus-repository-manager-ha-c-issues/2293>\
**Category:** Sonatype Nexus Repository\
**Created:** [August 7, 2019, 11:30am UTC](https://community.sonatype.com/t/nexus-repository-manager-ha-c-issues/2293 "2019-08-07T11:30:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mdeluca](https://avatars.discourse-cdn.com/v4/letter/m/d9b06d/32.png) [@mdeluca](https://community.sonatype.com/u/mdeluca)\
**Post date:** [August 7, 2019, 11:30am UTC](https://community.sonatype.com/t/nexus-repository-manager-ha-c-issues/2293/1 "2019-08-07T11:30:32Z")

</div>

Hi Everyone,

A few months back my team and I tried running Nexus Repository Manager Pro as an HA-Cluster. During our tests everything worked fine but when we migrated the system to production the HA-Cluster had some severe issues which lead to a crash. We immediately switched back to our old Nexus server (Windows based) and a few weeks later we just went ahead and migrated the old system to a single instance of Nexus Repository Manager running on RHEL7.  
My team is questioning the HA-C Feature eversince and we’re not quite sure if we should try to enable HA-C again with the latest version 3.18.  
We have a lot of developers depending on the Nexus Repository Manager and a HA-C would be ideal since a crash of the single node would stop the development in our company.

Is anyone running Nexus as an HA-C? If you do, what’s your experience with it?

Cheers,  
Marco

---

<div class="post-metadata">

**Author:** ![nickcook](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/nickcook/32/399_2.png) [@nickcook](https://community.sonatype.com/u/nickcook)\
**Post date:** [August 7, 2019, 11:56am UTC](https://community.sonatype.com/t/nexus-repository-manager-ha-c-issues/2293/2 "2019-08-07T11:56:10Z")

</div>

Hey Marco,

Thanks for taking the time to post this. I know there were some customers who had issues with HA-C in earlier versions, but I believe _most_ of those issues have been resolved in 3.18.

Let me poke around and see if we have any other customers that can share their experience with 3.18.

Cheers,  
Nick

---

<div class="post-metadata">

**Author:** ![vgavin](https://avatars.discourse-cdn.com/v4/letter/v/7cd45c/32.png) [@vgavin](https://community.sonatype.com/u/vgavin)\
**Post date:** [August 7, 2019, 12:31pm UTC](https://community.sonatype.com/t/nexus-repository-manager-ha-c-issues/2293/3 "2019-08-07T12:31:45Z")

</div>

Hi Marco  
We use HA-C on RHEL7  
We’ve had stability issues in the past (eg replication issues and nodes dropping out of the cluster) but we’ve been running 3.16.2-01 for a few months now and it has been a lot better - so I’d recommend running a test that or anything newer

Victor

---

<div class="post-metadata">

**Author:** ![rhbywater](https://avatars.discourse-cdn.com/v4/letter/r/b9e5f3/32.png) [@rhbywater](https://community.sonatype.com/u/rhbywater)\
**Post date:** [August 7, 2019, 11:02pm UTC](https://community.sonatype.com/t/nexus-repository-manager-ha-c-issues/2293/4 "2019-08-07T23:02:44Z")

</div>

Agree with @vgavin. We are running a three node HA-C 3.16 cluster on RHEL7 and apart from the odd small issues that are slowly getting fixed up (mostly nothing functional just things like odd logging etc.).

I did do a trial on an early version of Nexus 3 HA-C which had all kinds of issues but when I revisited and implemented a 3.15 cluster all these issues were gone.