You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/09/27 09:20:00 UTC
[jira] [Commented] (IGNITE-8845) GridUnsafe.allocateMemory throws
OutOfMemoryError which isn't handled
[ https://issues.apache.org/jira/browse/IGNITE-8845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630032#comment-16630032 ]
Vladimir Ozerov commented on IGNITE-8845:
-----------------------------------------
Moved to 2.8 due to inactivity. Please feel free to move back if you will be able to complete the ticket by AI 2.7 code freeze date, September 30, 2018.
> GridUnsafe.allocateMemory throws OutOfMemoryError which isn't handled
> ---------------------------------------------------------------------
>
> Key: IGNITE-8845
> URL: https://issues.apache.org/jira/browse/IGNITE-8845
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 2.5
> Reporter: Mikhail Cherkasov
> Priority: Major
> Fix For: 2.8
>
> Attachments: Main.java
>
>
> If there's no more native memory then Unsafe.allocateMemor throws java.lang.OutOfMemoryError. Errors - is type of exception after which you can't restore application and you need to close it and restart. I think in this case we can handle it and throw IgniteOOM instead.
>
> Reproducer is attached, it throws the following exception:
>
> Exception in thread "main" java.lang.OutOfMemoryError
> at sun.misc.Unsafe.allocateMemory(Native Method)
> at org.apache.ignite.internal.util.GridUnsafe.allocateMemory(GridUnsafe.java:1068)
> at org.apache.ignite.internal.mem.unsafe.UnsafeMemoryProvider.nextRegion(UnsafeMemoryProvider.java:80)
> at org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.addSegment(PageMemoryNoStoreImpl.java:612)
> at org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.allocatePage(PageMemoryNoStoreImpl.java:287)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)