Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Design: Clustering #64

Open
fxprunayre opened this issue Nov 14, 2024 · 0 comments
Open

Design: Clustering #64

fxprunayre opened this issue Nov 14, 2024 · 0 comments
Labels
migration Migration proposal

Comments

@fxprunayre
Copy link
Member

Take into consideration how we could at some point cluster the application (or part of the app eg. harvester) and avoid issues we have with the current application (see https://github.com/geonetwork/docker-geonetwork/tree/main/4.4.5#clustering-experimental)

Known limitations in GN4

Harvester / Scheduler needs to be refreshed when the database harvester configuration is modified (the harvesting node refresh the schedule every 2 minutes as a stopgap solution) To take into consideration in the task orchestration.
Settings / When saving application settings, some modules need to be updated:log file,DOI configuration,proxy configuration (use Java environment variable instead of database configuration) To check.
Thesaurus / Local thesaurus modified in one node are not updated on others. Moving the thesaurus in the database will solve the issue

Dependencies

Questions

Actions

  • [ ]

Related work
@fxprunayre fxprunayre added the migration Migration proposal label Nov 14, 2024
@fxprunayre fxprunayre moved this to Todo in GeoNetwork 5 Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
migration Migration proposal
Projects
GeoNetwork 5
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fxprunayre