Slowness of the Jira application caused by technological obsolescence

[Edgar Salgado Gallardo]

Good morning, a few days ago we detected slowness issues in the application, which we escalated with Atlassian. They told me it was a latency issue to the database.

When we contacted our DB, they told us the database needs to be migrated due to obsolescence. Our question is the following:

At the server or Jira node level, is it advisable to keep the same IP address when migrating? Or is it better to change the IP address during migration?

We have two nodes, but it is advisable to request new IP addresses. Can we add them as new nodes and, once the configuration is complete, simply deactivate the old IP addresses?

The same applies to the database. Is it advisable to keep the same IP address?
Is it better to request a new IP address and configure it as a replica? Once replication is correct, set it to productive and disable the obsolete IP addresses.

[Philipp Sendek]

Hi @Edgar Salgado Gallardo

without additional insights on what your infrastructure looks like and which applications and appliances are used, it's hard to make a definite answer. 
If you keep the IP address, your DNS records will remain valid and you don't have to deal with things like TTL until the new IP is applied. (But there are also ways to work around that). Switching IPs has other benefits (like keeping both the old and new servers running at the same time without IP conflicts)

So, to give you a concise answer: I would say that there are no technical reasons within Jira that force your to either use new IPs or stick to the old ones - simply do what works best for your team doing the work they need to do.

Greetings
Philipp