ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaliy Shopov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-811) Bundle Ignite node with OSv microkernel
Date Thu, 23 Jul 2015 10:17:04 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638607#comment-14638607

Vitaliy Shopov commented on IGNITE-811:

Check your current class loader: {{getClass().getClassLoader().getClass()}}. Vanilla Ignite
node use: {{class sun.misc.Launcher$AppClassLoader}} on launch.

I am ran in the same issue launching Ignite node under SBT console where is using: {{class
sbt.classpath.ClasspathUtilities$$anon$1}} as class loader.

> Bundle Ignite node with OSv microkernel
> ---------------------------------------
>                 Key: IGNITE-811
>                 URL: https://issues.apache.org/jira/browse/IGNITE-811
>             Project: Ignite
>          Issue Type: New Feature
>          Components: general
>    Affects Versions: sprint-2
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
> I'd like to experiment with bundling Ignite nodes with [OSv|http://osv.io/].
> The advantages of using OSv are multi fold, here are just some of them:
> # significant network stack performance improvements. Compared to the traditional TCP/IP
stack you can see 150% better performance on your app. network IO
> # full isolation (unlike Docker)
> # no kernel overhead, caused by context switching
> # state-full transition of an application from one OSv instance to another
> and many others.

This message was sent by Atlassian JIRA

View raw message