Hosting
Problem
Projectrak's information is not correctly replicated between nodes in Data Center installations.
Solution
This is a problem that we have identified with our biggest Customers. After many talks with Atlassian, they suggested our Customer upgrade Jira to the 8.12.0 version or above which includes the Long Term Support Release. This LTS release will include document-based index replication on a point to point basis, meaning instead of replicating index changes via the DB (and having to rebuild the index for each of those) it should be able to add relevant changes to the index as part of a document which can then be successfully added to the index of other nodes without taking a toll on the re-index times or other processes that might be taking a toll on the instance performance. You can find more information about this right here.
Related articles
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | com.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@140ea |
|---|
| showSpace | false |
|---|
| sort | modified |
|---|
| reverse | true |
|---|
| type | page |
|---|
| cql | label in ( "datacenter" , "performance" , "nodes" , "data-center" , "projectrak" , "reindex" ) and type = "page" and space = "SKB" |
|---|
| labels | projectrak nodes data-center datacenter reindex performance |
|---|
|
...
