[
https://issues.apache.org/jira/browse/ASTERIXDB-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190696#comment-15190696
]
ASF subversion and git services commented on ASTERIXDB-1338:
------------------------------------------------------------
Commit 6f7efb6d12efb865ae1d081679d50842f0498bd6 in incubator-asterixdb's branch
refs/heads/master from [~mhubail]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-asterixdb.git;h=6f7efb6 ]
ASTERIXDB-1338: Prevent Metadata Datasets Eviction
- Exclude metadata datasets from eviction policy.
- Fix updating used memory when a dataset is closed.
Change-Id: I56734bfe0eb7d166786cacb8d76f12f8d1a21798
Reviewed-on: https://asterix-gerrit.ics.uci.edu/707
Tested-by: Jenkins <[email protected]>
Reviewed-by: abdullah alamoudi <[email protected]>
> Metadata Datasets are Evicted on Low Memory
> -------------------------------------------
>
> Key: ASTERIXDB-1338
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1338
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Murtadha Hubail
> Assignee: Murtadha Hubail
> Priority: Critical
>
> When many datasets are created and we need to evict unused ones from memory
> to allocate their space for the newly created ones, metadata datasets are
> selected as candidates for eviction. Once they are evicted, the system
> becomes unusable. This is because of of the special treatment of metadata
> indexes since they are registered only once during metadata bootstrap.
> To reproduce the issue, just create many datasets and insert a record in them
> to force their memory to be allocated. Eventually, the metadata datasets will
> be evicted and the instance will be unusable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
