incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron McCurry (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (BLUR-433) Block Cache creating process fragmentation
Date Mon, 15 Jun 2015 13:42:00 GMT

     [ https://issues.apache.org/jira/browse/BLUR-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aaron McCurry closed BLUR-433.
------------------------------
    Resolution: Fixed

https://git-wip-us.apache.org/repos/asf?p=incubator-blur.git;a=commit;h=90625d0235dd4d60a812be9fedfc12e0be1d817b

> Block Cache creating process fragmentation
> ------------------------------------------
>
>                 Key: BLUR-433
>                 URL: https://issues.apache.org/jira/browse/BLUR-433
>             Project: Apache Blur
>          Issue Type: Bug
>          Components: Blur
>    Affects Versions: 0.2.4
>         Environment: Linux
>            Reporter: Aaron McCurry
>            Assignee: Aaron McCurry
>            Priority: Blocker
>             Fix For: 0.2.4
>
>
> During the life of a shard process if there is a lot of loading and unloading from the
block cache due to tables coming and going as well as a lot of data updates fragmentation
can occur in the process.  The issue seems to be when the UnsafeCacheValue allocates many
small chunks of memory and later releases them when the cache reuse queue over flows.  The
end result is that the shard process grows much larger than the off heap cache and heap combined.
 If the shard process is aggressively configured for the server it's on it can use too much
memory and Linux will end up killing the process once the server is in jeopardy.  This normally
ends with a cascading failure of an entire shard cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message