[
https://issues.apache.org/jira/browse/IGNITE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533693#comment-14533693
]
Konstantin Boudnik commented on IGNITE-811:
-------------------------------------------
Ok, I have some good initial progress with this. I have all the files to build
the OSv image with the latest 1.1.0 RC and I can really run the node inside of
the OSv instance. Two issues I see right now:
- an exception is thrown
{noformat}
Created instance: ignite-osv
OSv v0.20
eth0: 192.168.122.15
Failed to load handler: org.apache.ignite.logger.java.JavaLoggerFileHandler
java.lang.ClassNotFoundException:
org.apache.ignite.logger.java.JavaLoggerFileHandler
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at
io.osv.jul.LogManagerWrapper.reconfigureRootHandlers(LogManagerWrapper.java:59)
at
io.osv.jul.LogManagerWrapper$LogManagerInitializer$2.intercept(LogManagerWrapper.java:117)
at
$java.util.logging.Logger$$EnhancerByCGLIB$$8403bfce.getHandlers(<generated>)
at
org.apache.ignite.logger.java.JavaLogger.findHandler(JavaLogger.java:375)
at
org.apache.ignite.logger.java.JavaLogger.configure(JavaLogger.java:214)
at org.apache.ignite.logger.java.JavaLogger.<init>(JavaLogger.java:155)
at org.apache.ignite.logger.java.JavaLogger.<init>(JavaLogger.java:111)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.initLogger(IgnitionEx.java:1991)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.initializeConfiguration(IgnitionEx.java:1691)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1493)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1467)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:993)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:920)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:833)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:737)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:691)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:531)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:501)
at org.apache.ignite.Ignition.start(Ignition.java:332)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at io.osv.ContextIsolator.runMain(ContextIsolator.java:233)
at io.osv.ContextIsolator.access$400(ContextIsolator.java:32)
at io.osv.ContextIsolator$3.run(ContextIsolator.java:118)
[00:45:17] __________ ________________
[00:45:17] / _/ ___/ |/ / _/_ __/ __/
[00:45:17] _/ // (7 7 // / / / / _/
[00:45:17] /___/\___/_/|_/___/ /_/ /___/
[00:45:17]
[00:45:17] ver. 1.1.0-incubating#20150507-sha1:dfeceafa
[00:45:17] 2015 Copyright(C) Apache Software Foundation
[00:45:17]
[00:45:17] Quiet mode.
[00:45:17] ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or
"-v" to ignite.{sh|bat}
[00:45:17]
[00:45:17] Configured plugins:
[00:45:17] ^-- None
[00:45:17]
pthread_setcancelstate() stubbed
[00:45:23] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[00:45:23]
[00:45:23] Ignite node started OK (id=eb67a343)
[00:45:23] Topology snapshot [ver=1, nodes=1, CPUs=2, heap=1.0GB]
{noformat}
which doesn't affect the startup of the node, evidently. Still is pretty weird
as the class is a part of the ignite-core.jar
- two nodes running on two OSv containers don't auto-discover each other but it
might be caused by some funny stuff in my network routing configuration. I will
dig more into this.
If anyone has any suggestions about the exception part - I'd be pretty happy to
hear them. Thanks!
> 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
(v6.3.4#6332)
