Running BitBucket Server - Not Data Center.
1. Because the bundled ElasticSearch will not be updated to address Log4j, are there any instructions how to switch from the Bundled version to a standalone install?
2. Can the ElasticSearch install be installed on the same server as there is no mirroring/cluster in BitBucket Server?
3. How can we disable the bundled ElasticSearch after the migration?
Thanks in advance for any guidance.
@Moshe A Hi!
1. Please, take a look that ticket about log4j
https://jira.atlassian.com/browse/BSERV-13093
1.1. Regarding bundled version, as I see for the server release is impossible.
But what if you make a backup of indexes and schemas and evaluate local haproxy which will point to the external one?
2. I think you can make trick based on the haproxy
3. how about pointing on another port?
Cheers,
Gonchik
ElasticSearch is not mentioned in the bug fix. It is mentioned in the security notice, but no guidance is provided for us server users. An unofficial hack isn't what I'm expecting, but an official response from Atlassian.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.