Please describe the problem you'd like to be solved
Currently it is possible to use 1 Elasticsearch server for multiple Dashboard, but then you run in to the problem that they can see each others Archival Storage.
Describe the solution you'd like to see implemented
Elasticsearch index based on Dashboard UUID, this way resources can be better allocated for Archivematica.
Describe alternatives you've considered
Run multiple instances of Elasticsearch on different ports
Additional context
For Artefactual use:
Before you close this issue, you must check off the following:
[ ] All pull requests related to this issue are properly linked
[ ] All pull requests related to this issue have been merged
[ ] A testing plan for this issue has been implemented and passed (testing plan information should be included in the issue body or comments)
[ ] Documentation regarding this issue has been written and merged
[ ] Details about this issue have been added to the release notes
jraddaoui
commented
4 years ago
Please describe the problem you'd like to be solved Currently it is possible to use 1 Elasticsearch server for multiple Dashboard, but then you run in to the problem that they can see each others Archival Storage.
Describe the solution you'd like to see implemented Elasticsearch index based on Dashboard UUID, this way resources can be better allocated for Archivematica.
Describe alternatives you've considered Run multiple instances of Elasticsearch on different ports
Additional context
For Artefactual use:
Before you close this issue, you must check off the following: