[jira] [Commented] (IGNITE-1526) IBM JDK is not fully supported by the platfrom
[
https://issues.apache.org/jira/browse/IGNITE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909400#comment-14909400
]
Denis Magda commented on IGNITE-1526:
-
Val,
Yes, according to the Java docs it will fix all unpredictable
{{InvalidClassExceptions}} caused by missing {{serialVerisionUID}} and we
should be able to use JdkMarshaller across JDKs from different vendors, at
least until we face with something else :)
> IBM JDK is not fully supported by the platfrom
> --
>
> Key: IGNITE-1526
> URL: https://issues.apache.org/jira/browse/IGNITE-1526
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Andrey Gura
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> There are several issue related to IBM JDK.
> 1) It's not possible to compile the platform using IBM JDK ver 1.7;
> 2) Besides of the fact that two IBM nodes can connect to each other some
> functionality still doesn't work. As an example
> {{CacheClientPortablePutGetExample}} fails with the following stack trace
> {noformat}
> [14:38:56,930][ERROR][grid-nio-worker-0-#26%null%][TcpCommunicationSpi]
> Caught unhandled exception in NIO worker thread (restart the node).
> class org.apache.ignite.IgniteException: Invalid field type: 0
> at
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readRemovedField(PortableDirectMessageReader.java:670)
> at
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readFieldHeader(PortableDirectMessageReader.java:520)
> at
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readMessage(PortableDirectMessageReader.java:339)
> at
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:248)
> at
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:76)
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:103)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> at
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:122)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2078)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:172)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:858)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1397)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1339)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1223)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:801)
> {noformat}
> 3) Oracle JVM based server node fails to connect to IBM server node producing
> the stack trace below. Tested with JDK and Portable marshallers.
> {noformat}
> [13:47:33,935][SEVERE][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Failed
> to
> unmarshal discovery data for component: 0
> class org.apache.ignite.IgniteCheckedException: Failed to deserialize object
> wit
> h given class loader: sun.misc.Launcher$AppClassLoader@56092666
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshalle
> r.java:105)
> at
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMar
> shaller.java:68)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDis
> coverySpi.java:1697)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essNodeAddedMessage(ServerImpl.java:3258)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essMessage(ServerImpl.java:1993)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.b
> ody(ServerImpl.java:5206)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> Caused by: java.io.InvalidClassException:
> org.apache.ignite.internal.util.lang.G
> ridFunc$38; local class incompatible: stream classdesc serialVersionUID =
> -55433
> 49853748590486, local class serialVersionUID = -5664060422647374863
> at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:617)
>
[jira] [Commented] (IGNITE-1526) IBM JDK is not fully supported by the platfrom
[
https://issues.apache.org/jira/browse/IGNITE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909374#comment-14909374
]
Valentin Kulichenko commented on IGNITE-1526:
-
Denis,
Are you saying that setting {{serialVersionUID}} for all serializable classes
will fix the issue? If so, this is definitely *much* easier than switching to
portable marshaller everywhere. And it's always a good idea to get rid of
anonymous serializable classes anyway :)
Our {{ClassesGenerator}} class that generates {{classnames.properties}} file
checks each serializable class for {{serialVersionUID}}, but now it skips
anonymous classes (see {{!cls.getSimpleName().isEmpty()}} on line 213).
Removing this {{if}} will show the list of classes that need to be reworked.
> IBM JDK is not fully supported by the platfrom
> --
>
> Key: IGNITE-1526
> URL: https://issues.apache.org/jira/browse/IGNITE-1526
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Andrey Gura
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> There are several issue related to IBM JDK.
> 1) It's not possible to compile the platform using IBM JDK ver 1.7;
> 2) Besides of the fact that two IBM nodes can connect to each other some
> functionality still doesn't work. As an example
> {{CacheClientPortablePutGetExample}} fails with the following stack trace
> {noformat}
> [14:38:56,930][ERROR][grid-nio-worker-0-#26%null%][TcpCommunicationSpi]
> Caught unhandled exception in NIO worker thread (restart the node).
> class org.apache.ignite.IgniteException: Invalid field type: 0
> at
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readRemovedField(PortableDirectMessageReader.java:670)
> at
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readFieldHeader(PortableDirectMessageReader.java:520)
> at
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readMessage(PortableDirectMessageReader.java:339)
> at
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:248)
> at
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:76)
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:103)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> at
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:122)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2078)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:172)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:858)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1397)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1339)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1223)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:801)
> {noformat}
> 3) Oracle JVM based server node fails to connect to IBM server node producing
> the stack trace below. Tested with JDK and Portable marshallers.
> {noformat}
> [13:47:33,935][SEVERE][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Failed
> to
> unmarshal discovery data for component: 0
> class org.apache.ignite.IgniteCheckedException: Failed to deserialize object
> wit
> h given class loader: sun.misc.Launcher$AppClassLoader@56092666
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshalle
> r.java:105)
> at
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMar
> shaller.java:68)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDis
> coverySpi.java:1697)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essNodeAddedMessage(ServerImpl.java:3258)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essMessage(ServerImpl.java:1993)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.b
> ody(ServerImpl.java:5206)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiT
[jira] [Updated] (IGNITE-1526) IBM JDK is not fully supported by the platfrom
[
https://issues.apache.org/jira/browse/IGNITE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-1526:
Assignee: Andrey Gura (was: Denis Magda)
> IBM JDK is not fully supported by the platfrom
> --
>
> Key: IGNITE-1526
> URL: https://issues.apache.org/jira/browse/IGNITE-1526
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Andrey Gura
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> There are several issue related to IBM JDK.
> 1) It's not possible to compile the platform using IBM JDK ver 1.7;
> 2) Besides of the fact that two IBM nodes can connect to each other some
> functionality still doesn't work. As an example
> {{CacheClientPortablePutGetExample}} fails with the following stack trace
> {noformat}
> [14:38:56,930][ERROR][grid-nio-worker-0-#26%null%][TcpCommunicationSpi]
> Caught unhandled exception in NIO worker thread (restart the node).
> class org.apache.ignite.IgniteException: Invalid field type: 0
> at
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readRemovedField(PortableDirectMessageReader.java:670)
> at
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readFieldHeader(PortableDirectMessageReader.java:520)
> at
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readMessage(PortableDirectMessageReader.java:339)
> at
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:248)
> at
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:76)
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:103)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> at
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:122)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2078)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:172)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:858)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1397)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1339)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1223)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:801)
> {noformat}
> 3) Oracle JVM based server node fails to connect to IBM server node producing
> the stack trace below. Tested with JDK and Portable marshallers.
> {noformat}
> [13:47:33,935][SEVERE][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Failed
> to
> unmarshal discovery data for component: 0
> class org.apache.ignite.IgniteCheckedException: Failed to deserialize object
> wit
> h given class loader: sun.misc.Launcher$AppClassLoader@56092666
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshalle
> r.java:105)
> at
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMar
> shaller.java:68)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDis
> coverySpi.java:1697)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essNodeAddedMessage(ServerImpl.java:3258)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essMessage(ServerImpl.java:1993)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.b
> ody(ServerImpl.java:5206)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> Caused by: java.io.InvalidClassException:
> org.apache.ignite.internal.util.lang.G
> ridFunc$38; local class incompatible: stream classdesc serialVersionUID =
> -55433
> 49853748590486, local class serialVersionUID = -5664060422647374863
> at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:617)
> at
> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:162
> 2)
> at
> java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1
> 771)
>
[jira] [Commented] (IGNITE-1526) IBM JDK is not fully supported by the platfrom
[
https://issues.apache.org/jira/browse/IGNITE-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909356#comment-14909356
]
Denis Magda commented on IGNITE-1526:
-
Andrey,
As another quick solution we can try to implement.
Look up all our system anonymous classes that are transferred between nodes and
convert them to inner classes setting {{serialVersionUID}} to 0. Probably the
number of this classes is not significant and we can keep using JdkMarshaller
in core components.
The user will use PortableMarshaller not loosing ability to utilize anonymous
classes in the code that transfers these classes across a cluster (compute
engine, event listeners, etc.)
In addition, if this solution works we need to switch to JdkMarshaller in
PortableMarshaller's internal logic (see,
{{PortableClassDescriptor.initUseOptimizedMarshallerFlag}}).
> IBM JDK is not fully supported by the platfrom
> --
>
> Key: IGNITE-1526
> URL: https://issues.apache.org/jira/browse/IGNITE-1526
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: ignite-1.5
>
>
> There are several issue related to IBM JDK.
> 1) It's not possible to compile the platform using IBM JDK ver 1.7;
> 2) Besides of the fact that two IBM nodes can connect to each other some
> functionality still doesn't work. As an example
> {{CacheClientPortablePutGetExample}} fails with the following stack trace
> {noformat}
> [14:38:56,930][ERROR][grid-nio-worker-0-#26%null%][TcpCommunicationSpi]
> Caught unhandled exception in NIO worker thread (restart the node).
> class org.apache.ignite.IgniteException: Invalid field type: 0
> at
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readRemovedField(PortableDirectMessageReader.java:670)
> at
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readFieldHeader(PortableDirectMessageReader.java:520)
> at
> org.gridgain.grid.internal.communication.PortableDirectMessageReader.readMessage(PortableDirectMessageReader.java:339)
> at
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:248)
> at
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:76)
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:103)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> at
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:122)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:107)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:2078)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:172)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:858)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeys(GridNioServer.java:1397)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1339)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1223)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:801)
> {noformat}
> 3) Oracle JVM based server node fails to connect to IBM server node producing
> the stack trace below. Tested with JDK and Portable marshallers.
> {noformat}
> [13:47:33,935][SEVERE][tcp-disco-msg-worker-#2%null][TcpDiscoverySpi] Failed
> to
> unmarshal discovery data for component: 0
> class org.apache.ignite.IgniteCheckedException: Failed to deserialize object
> wit
> h given class loader: sun.misc.Launcher$AppClassLoader@56092666
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshalle
> r.java:105)
> at
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMar
> shaller.java:68)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDis
> coverySpi.java:1697)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essNodeAddedMessage(ServerImpl.java:3258)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.proc
> essMessage(ServerImpl.java:1993)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.b
> ody(Se
[jira] [Assigned] (IGNITE-1555) Combine ignite-hadoop and ignite-spark into signle ignite-accelerator assembly.
[ https://issues.apache.org/jira/browse/IGNITE-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik reassigned IGNITE-1555: -- Assignee: Konstantin Boudnik > Combine ignite-hadoop and ignite-spark into signle ignite-accelerator > assembly. > --- > > Key: IGNITE-1555 > URL: https://issues.apache.org/jira/browse/IGNITE-1555 > Project: Ignite > Issue Type: New Feature > Components: hadoop >Affects Versions: ignite-1.4 >Reporter: Konstantin Boudnik >Assignee: Konstantin Boudnik > Fix For: ignite-1.5 > > Attachments: IGNITE-1555.patch, IGNITE-1555.patch > > > Let's combine all nice things that Ignite provides for Hadoop and Spark into > single assembly called ignite-accelerator. This will be advantageous for > downstream integrators like Bigtop, where all bits can be packaged together, > tested, and deployed with proper configurations and permissions to avoid > interoperability issues. A typical is when spark-shell starts an Ignite node > which crashes because user 'spark' isn't allowed to write into Ignite's > work-dir, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1555) Combine ignite-hadoop and ignite-spark into signle ignite-accelerator assembly.
[ https://issues.apache.org/jira/browse/IGNITE-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated IGNITE-1555: --- Attachment: IGNITE-1555.patch Also, updated the top-level README file > Combine ignite-hadoop and ignite-spark into signle ignite-accelerator > assembly. > --- > > Key: IGNITE-1555 > URL: https://issues.apache.org/jira/browse/IGNITE-1555 > Project: Ignite > Issue Type: New Feature > Components: hadoop >Affects Versions: ignite-1.4 >Reporter: Konstantin Boudnik > Fix For: ignite-1.5 > > Attachments: IGNITE-1555.patch, IGNITE-1555.patch > > > Let's combine all nice things that Ignite provides for Hadoop and Spark into > single assembly called ignite-accelerator. This will be advantageous for > downstream integrators like Bigtop, where all bits can be packaged together, > tested, and deployed with proper configurations and permissions to avoid > interoperability issues. A typical is when spark-shell starts an Ignite node > which crashes because user 'spark' isn't allowed to write into Ignite's > work-dir, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1555) Combine ignite-hadoop and ignite-spark into signle ignite-accelerator assembly.
[ https://issues.apache.org/jira/browse/IGNITE-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Boudnik updated IGNITE-1555: --- Attachment: IGNITE-1555.patch Here's the working illustration of what I'm suggesting. I will wait with the commit as I want to hear people thoughts on this. Thanks! > Combine ignite-hadoop and ignite-spark into signle ignite-accelerator > assembly. > --- > > Key: IGNITE-1555 > URL: https://issues.apache.org/jira/browse/IGNITE-1555 > Project: Ignite > Issue Type: New Feature > Components: hadoop >Affects Versions: ignite-1.4 >Reporter: Konstantin Boudnik > Fix For: ignite-1.5 > > Attachments: IGNITE-1555.patch > > > Let's combine all nice things that Ignite provides for Hadoop and Spark into > single assembly called ignite-accelerator. This will be advantageous for > downstream integrators like Bigtop, where all bits can be packaged together, > tested, and deployed with proper configurations and permissions to avoid > interoperability issues. A typical is when spark-shell starts an Ignite node > which crashes because user 'spark' isn't allowed to write into Ignite's > work-dir, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1555) Combine ignite-hadoop and ignite-spark into signle ignite-accelerator assembly.
Konstantin Boudnik created IGNITE-1555: -- Summary: Combine ignite-hadoop and ignite-spark into signle ignite-accelerator assembly. Key: IGNITE-1555 URL: https://issues.apache.org/jira/browse/IGNITE-1555 Project: Ignite Issue Type: New Feature Components: hadoop Affects Versions: ignite-1.4 Reporter: Konstantin Boudnik Fix For: ignite-1.5 Let's combine all nice things that Ignite provides for Hadoop and Spark into single assembly called ignite-accelerator. This will be advantageous for downstream integrators like Bigtop, where all bits can be packaged together, tested, and deployed with proper configurations and permissions to avoid interoperability issues. A typical is when spark-shell starts an Ignite node which crashes because user 'spark' isn't allowed to write into Ignite's work-dir, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1554) igniterouter scripts are not working
[
https://issues.apache.org/jira/browse/IGNITE-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909187#comment-14909187
]
Raúl Kripalani commented on IGNITE-1554:
Fixed in ignite-1.4.1 but missing the fix version in JIRA.
> igniterouter scripts are not working
>
>
> Key: IGNITE-1554
> URL: https://issues.apache.org/jira/browse/IGNITE-1554
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
> Fix For: ignite-1.5
>
>
> Executing the {{igniterouter}} script fails with:
> {code}
> Error: Could not find or load main class
> org.apache.ignite.client.router.impl.GridRouterCommandLineStartup
> {code}
> Since a refactoring in commit b88a1012e9031b760193179463ce852032c2e334.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-1554) igniterouter scripts are not working
[
https://issues.apache.org/jira/browse/IGNITE-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raúl Kripalani resolved IGNITE-1554.
Resolution: Fixed
> igniterouter scripts are not working
>
>
> Key: IGNITE-1554
> URL: https://issues.apache.org/jira/browse/IGNITE-1554
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
> Fix For: ignite-1.5
>
>
> Executing the {{igniterouter}} script fails with:
> {code}
> Error: Could not find or load main class
> org.apache.ignite.client.router.impl.GridRouterCommandLineStartup
> {code}
> Since a refactoring in commit b88a1012e9031b760193179463ce852032c2e334.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1554) igniterouter scripts are not working
Raúl Kripalani created IGNITE-1554:
--
Summary: igniterouter scripts are not working
Key: IGNITE-1554
URL: https://issues.apache.org/jira/browse/IGNITE-1554
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: ignite-1.4
Reporter: Raúl Kripalani
Assignee: Raúl Kripalani
Fix For: ignite-1.5
Executing the {{igniterouter}} script fails with:
{code}
Error: Could not find or load main class
org.apache.ignite.client.router.impl.GridRouterCommandLineStartup
{code}
Since a refactoring in commit b88a1012e9031b760193179463ce852032c2e334.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-815) Reactive Streams Compatibility
[ https://issues.apache.org/jira/browse/IGNITE-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909181#comment-14909181 ] Raúl Kripalani commented on IGNITE-815: --- Community shared their ideas on a mailing list discussion: http://apache-ignite-developers.2346864.n4.nabble.com/Brainstorming-about-Reactive-Streams-td3346.html. [~lalitj] is this something you'd like to help us with? We can work together if you'd like. I didn't see negative feedback around using RxJava 1.0 + Reactive Streams adapter for now, to later switch to RxJava 2.0 with native RS support. So let's go in this direction. > Reactive Streams Compatibility > -- > > Key: IGNITE-815 > URL: https://issues.apache.org/jira/browse/IGNITE-815 > Project: Ignite > Issue Type: New Feature >Reporter: Suminda Dharmasena > > http://www.reactive-streams.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
