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.

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

ISSUE-304: allow running search reindexing fully with cronjob #305

Closed
wants to merge 1 commit into from

Conversation

KylixSerg
Copy link
Contributor

Allow running elastic search reindexing fully from the cronjob process, this will mitigate potential issues with the server being affected when issues happen there, example OOMs, or issues on the search server side.

What this PR does / why we need it :

Fixes #

Type of change :

  • Bug fix
  • Improvement
  • New feature
  • Documentation

Checklist:

  • I have read the CONTRIBUTING document.
  • Chart Version bumped
  • Variables are documented in the README.md
  • Title of the PR starts with chart name
  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • All new and existing tests passed.

Reviewers

Allow running elastic search reindexing fully from the cronjob process,
this will mitigate potential issues with the server being affected when issues
happen there, example OOMs, or issues on the search server side.
@harshach
Copy link
Contributor

@karanh37 @mohityadav766 please review

@akash-jain-10
Copy link
Collaborator

Hello @KylixSerg . These CronJobs are intended to automate post-upgrade steps as outlined in the documentation here. We do not intend this functionality to be used on a scheduled basis. If you require this feature, you can schedule the Search Indexing Runs from the OpenMetadata UI.

Additionally, if you are consistently experiencing Out-of-Memory (OOM) errors on the Server, please consider configuring the OpenMetadata Java heap options as per the documentation here. Therefore, we will be closing this Pull Request as it is not planned. Thank you for your attention to this matter. Feel free to contact us via Slack for further assistance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants