Re: Ignite on FreeBSD 11 and OpenJDK

2017-04-18 Thread Kamil Misuth
Hi Denis, that is great. Thank you for the link! I hope Ignite 2.0 or some later version will eventually work on FreeBSD with OpenJDK. Kamil On 2017-04-19 00:53, Denis Magda wrote: Hi Kamil, The documentation for the new off-heap page memory is being prepared and will become public right

Re: Ignite on FreeBSD 11 and OpenJDK

2017-04-18 Thread Denis Magda
Hi Kamil, The documentation for the new off-heap page memory is being prepared and will become public right after 2.0 release. You can track the progress here: https://issues.apache.org/jira/browse/IGNITE-4961 — Denis > On Apr 18, 2017, at 3:47 PM, Kamil Misuth wrote: > >

Re: Ignite on FreeBSD 11 and OpenJDK

2017-04-18 Thread Kamil Misuth
Replying, to my own question. Indeed, it seems to be the case that for Ignite 2.0, everything will be off heap. Denis Magda just (23 hours ago) updated the relevant wiki page. https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=67638199=10=8 Sounds cool to me :).

Re: Ignite on FreeBSD 11 and OpenJDK

2017-04-18 Thread Kamil Misuth
Sure, Andrey. In mean time, a fact-checking question: I haven't really gone through the new memory policy functionality in depth, but it does seem that for Ignite 2.0 your aim is to move data off heap implicitly for all caches (and possibly backup the off heap region by memory mapped

Re: Ignite on FreeBSD 11 and OpenJDK

2017-04-13 Thread Andrey Gura
Kamil, thanks a lot for your help. As I told before I need some time for problem analyse. After it I'll create JIRA ticket and share link to it in this thread. Thank you again! On Wed, Apr 12, 2017 at 11:56 PM, Kamil Misuth wrote: > Hi Andrey, > > I've built ignite-3477-master

Re: Ignite on FreeBSD 11 and OpenJDK

2017-04-12 Thread Kamil Misuth
Hi Andrey, I've built ignite-3477-master (commit hash 5839f481b7) today. Apart from the fact that some other Configuration APIs changed, CacheMemoryMode disapeared. I guess this is related to

Re: Ignite on FreeBSD 11 and OpenJDK

2017-04-11 Thread Kamil Misuth
Sure thing. I will check out ignite-3477-master as soon as I have some time tomorrow. Kamil On 04/11/2017 05:48 PM, Andrey Gura wrote: Thanks for provided information. I need additional time for problem investigation. You can also try code from ignite-3477-master branch. This branch

Re: Ignite on FreeBSD 11 and OpenJDK

2017-04-11 Thread Andrey Gura
Thanks for provided information. I need additional time for problem investigation. You can also try code from ignite-3477-master branch. This branch contains many memory related fixes but it isn't stable yet. On Mon, Apr 10, 2017 at 11:37 PM, kimec.ethome.sk wrote: > Hi Andrey,

Re: Ignite on FreeBSD 11 and OpenJDK

2017-04-10 Thread kimec.ethome.sk
Hi Andrey, sorry, I've got ahead of my self. I am on FreeBSD 11.0-RELEASE-p1 amd64 With OpenJDK Runtime Environment 1.8.0_121-b13 Oracle Corporation OpenJDK 64-Bit Server VM 25.121-b13 hw.model: Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz hw.machine_arch: amd64 hw.ncpu: 8 hw.physmem: 8251813888

Re: Ignite on FreeBSD 11 and OpenJDK

2017-04-10 Thread Andrey Gura
Hi, could you please share core dump file? If not, it would be helpful to know what is CPU architecture on this server. On Mon, Apr 10, 2017 at 2:53 AM, Kamil Misuth wrote: > Greetings, > > OpenJDK (7 and 8) HotSpot JVM SIGSEGVs on FreeBSD 11 as soon as node joins a > topology

Ignite on FreeBSD 11 and OpenJDK

2017-04-09 Thread Kamil Misuth
Greetings, OpenJDK (7 and 8) HotSpot JVM SIGSEGVs on FreeBSD 11 as soon as node joins a topology and starts to communicate via DirectNioClientWorker. The root cause is DirectByteBufferStreamImpl (both versions) which uses GridUnsafe.getXXX/putXXX(Object object, offset, value) methods to