We are running a 4 node Jira DC, and we would like to re-direct all REST traffic to a specific server. We use Apache as a load balancer. We have tried using "RewriteEngine" but I keep getting 401, it works when we try rest calls that don't required login.
Does anyone have any real world example of how to do this?
Thanks in advance.
After a long time researching and trying, I was able to re-route the REST traffic as per our standards.
This is what we did:
This is not the best solution but it does the job.
Hope this can help other people too.
No answer but have the same scenario and also looking to see if this has ever been succesfully done. I would hope someone has successfully done this with Apache given it's a Load Balancer called out in Atlassian documentation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
If the reason for such approach is to make sure rest traffic does not affect other users (UI) operations, I would suggest trying another approach and use rate limiting (for rest): https://confluence.atlassian.com/adminjiraserver/improving-instance-stability-with-rate-limiting-983794911.html
If the rest traffic is not read-only each operation will still affect all other nodes (and user actions on those nodes) so the separation will not be really effective.
mac
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a question for your load-balancer software, not really an Atlassian thing - all they have on it is https://confluence.atlassian.com/enterprise/traffic-distribution-with-atlassian-data-center-895912660.html
I've successfully followed the instructions in there, but it wasn't an F5 as you suggest you're using.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, yes but I was wondering if anyone has successfully done it with Apache.
We are not using F5 firewalls, we use linux servers with apache 2.4 installed in them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, right, well that is in the docs!
You can skip the web-sockets bit for Jira
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, I saw that and we have configured that way for Confluence.
The configuration example that I am asking for, is for Jira datacenter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is pretty much the same, you can dump the synchrony parts out and change the urls.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
OK, we already have apache configured to work with Jira Datacenter, what I am asking here is for help on traffic shapping.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.