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

Catalog references still leak memory #566

Closed
novoj opened this issue May 15, 2024 · 0 comments · Fixed by #567
Closed

Catalog references still leak memory #566

novoj opened this issue May 15, 2024 · 0 comments · Fixed by #567
Assignees
@novoj
Labels
bug Something isn't working
Milestone
Beta

Comments

@novoj
Copy link
Collaborator

novoj commented May 15, 2024

Previous issue made behaviour better but we still leak memory. We revealed to other places:

  • io.evitadb.index.EntityIndex#schemaAccessor contains hidden relation to catalog and not all indexes are reinstantiated with new catalog version
  • Undertow router registers mappings twice and on catalog rename only part of those are really removed
@novoj novoj added the bug Something isn't working label May 15, 2024
@novoj novoj added this to the Beta milestone May 15, 2024
@novoj novoj self-assigned this May 15, 2024
novoj added a commit that referenced this issue May 15, 2024
@novoj
fix(#566): Catalog references still leak memory
eab25c4 
This commit eliminates need for `io.evitadb.index.EntityIndex#schemaAccessor` that causes memory leaks.
novoj added a commit that referenced this issue May 15, 2024
@novoj
fix(#566): Catalog references still leak memory
00a1e62 
This commit corrects catalog handling in CatalogIndex.
lukashornych added a commit that referenced this issue May 15, 2024
@lukashornych
fix(#566): fix HTTP handlers not being entirely removed when catalog …
e62051c 
…was deleted, causing memory leak
@novoj novoj linked a pull request May 15, 2024 that will close this issue
fix(#566): catalog references still leak memory #567
Merged
novoj added a commit that referenced this issue May 15, 2024
@novoj
Merge pull request #567 from FgForrest/566-catalog-references-still-l…
2a9f019 
…eak-memory

fix(#566): catalog references still leak memory
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@novoj novoj

Labels
bug Something isn't working
Projects
None yet
Milestone
Beta
Development

Successfully merging a pull request may close this issue.

fix(#566): catalog references still leak memory FgForrest/evitaDB
1 participant
@novoj