[jira] [Closed] (IGNITE-3963) FlinkIgniteSinkSelfTest fails with exception IllegalArgumentException
[
https://issues.apache.org/jira/browse/IGNITE-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra closed IGNITE-3963.
-
> FlinkIgniteSinkSelfTest fails with exception IllegalArgumentException
> -
>
> Key: IGNITE-3963
> URL: https://issues.apache.org/jira/browse/IGNITE-3963
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Trivial
> Fix For: 1.8
>
>
> FlinkIgniteSinkSelfTest fails with exception IllegalArgumentException.
> {code}
> [21:30:31,387][INFO ][main][root] >>> Stopping test class:
> FlinkIgniteSinkSelfTest <<<
> org.apache.flink.runtime.client.JobExecutionException: Job execution failed.
> at
> org.apache.flink.runtime.jobmanager.JobManager$$anonfun$handleMessage$1$$anonfun$applyOrElse$7.apply$mcV$sp(JobManager.scala:714)
> at
> org.apache.flink.runtime.jobmanager.JobManager$$anonfun$handleMessage$1$$anonfun$applyOrElse$7.apply(JobManager.scala:660)
> at
> org.apache.flink.runtime.jobmanager.JobManager$$anonfun$handleMessage$1$$anonfun$applyOrElse$7.apply(JobManager.scala:660)
> at
> scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)
> at
> scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24)
> at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:41)
> at
> akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:401)
> at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
> at
> scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.pollAndExecAll(ForkJoinPool.java:1253)
> at
> scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1346)
> at
> scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
> at
> scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
> Caused by: org.apache.flink.streaming.runtime.tasks.StreamTaskException:
> Cannot instantiate user function.
> at
> org.apache.flink.streaming.api.graph.StreamConfig.getStreamOperator(StreamConfig.java:209)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:186)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:559)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Ignite grid name thread local
> must be set or this method should be accessed under
> org.apache.ignite.thread.IgniteThread
> at
> org.apache.ignite.internal.IgnitionEx.localIgnite(IgnitionEx.java:1296)
> at
> org.apache.ignite.internal.GridLoggerProxy.readResolve(GridLoggerProxy.java:207)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1148)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1810)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> at
> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000)
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> at
> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000)
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
> at
> org.apache.flink.util.InstantiationUtil.deserializeObject(InstantiationUtil.java:290)
> at
> org.apache.flink.util.InstantiationUtil.readObjectFromConfig(InstantiationUtil.java:248)
> at
> org.apache.flink.streaming.api.graph.StreamConfig.getStreamOperator(StreamConfig.java:194)
> ... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3963) FlinkIgniteSinkSelfTest fails with exception IllegalArgumentException
[
https://issues.apache.org/jira/browse/IGNITE-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1965#comment-1965
]
Saikat Maitra commented on IGNITE-3963:
---
[~agura]
Thank you Andrey. I have merged the changes in master branch.
Regards
Saikat
> FlinkIgniteSinkSelfTest fails with exception IllegalArgumentException
> -
>
> Key: IGNITE-3963
> URL: https://issues.apache.org/jira/browse/IGNITE-3963
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Trivial
> Fix For: 1.8
>
>
> FlinkIgniteSinkSelfTest fails with exception IllegalArgumentException.
> {code}
> [21:30:31,387][INFO ][main][root] >>> Stopping test class:
> FlinkIgniteSinkSelfTest <<<
> org.apache.flink.runtime.client.JobExecutionException: Job execution failed.
> at
> org.apache.flink.runtime.jobmanager.JobManager$$anonfun$handleMessage$1$$anonfun$applyOrElse$7.apply$mcV$sp(JobManager.scala:714)
> at
> org.apache.flink.runtime.jobmanager.JobManager$$anonfun$handleMessage$1$$anonfun$applyOrElse$7.apply(JobManager.scala:660)
> at
> org.apache.flink.runtime.jobmanager.JobManager$$anonfun$handleMessage$1$$anonfun$applyOrElse$7.apply(JobManager.scala:660)
> at
> scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)
> at
> scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24)
> at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:41)
> at
> akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:401)
> at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
> at
> scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.pollAndExecAll(ForkJoinPool.java:1253)
> at
> scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1346)
> at
> scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
> at
> scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
> Caused by: org.apache.flink.streaming.runtime.tasks.StreamTaskException:
> Cannot instantiate user function.
> at
> org.apache.flink.streaming.api.graph.StreamConfig.getStreamOperator(StreamConfig.java:209)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:186)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:559)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Ignite grid name thread local
> must be set or this method should be accessed under
> org.apache.ignite.thread.IgniteThread
> at
> org.apache.ignite.internal.IgnitionEx.localIgnite(IgnitionEx.java:1296)
> at
> org.apache.ignite.internal.GridLoggerProxy.readResolve(GridLoggerProxy.java:207)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1148)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1810)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> at
> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000)
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> at
> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000)
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
> at
> org.apache.flink.util.InstantiationUtil.deserializeObject(InstantiationUtil.java:290)
> at
> org.apache.flink.util.InstantiationUtil.readObjectFromConfig(InstantiationUtil.java:248)
> at
> org.apache.flink.streaming.api.graph.StreamConfig.getStreamOperator(StreamConfig.java:194)
> ... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3963) FlinkIgniteSinkSelfTest fails with exception IllegalArgumentException
[
https://issues.apache.org/jira/browse/IGNITE-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1931#comment-1931
]
ASF GitHub Bot commented on IGNITE-3963:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/1112
> FlinkIgniteSinkSelfTest fails with exception IllegalArgumentException
> -
>
> Key: IGNITE-3963
> URL: https://issues.apache.org/jira/browse/IGNITE-3963
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Trivial
> Fix For: 1.8
>
>
> FlinkIgniteSinkSelfTest fails with exception IllegalArgumentException.
> {code}
> [21:30:31,387][INFO ][main][root] >>> Stopping test class:
> FlinkIgniteSinkSelfTest <<<
> org.apache.flink.runtime.client.JobExecutionException: Job execution failed.
> at
> org.apache.flink.runtime.jobmanager.JobManager$$anonfun$handleMessage$1$$anonfun$applyOrElse$7.apply$mcV$sp(JobManager.scala:714)
> at
> org.apache.flink.runtime.jobmanager.JobManager$$anonfun$handleMessage$1$$anonfun$applyOrElse$7.apply(JobManager.scala:660)
> at
> org.apache.flink.runtime.jobmanager.JobManager$$anonfun$handleMessage$1$$anonfun$applyOrElse$7.apply(JobManager.scala:660)
> at
> scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)
> at
> scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24)
> at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:41)
> at
> akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:401)
> at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
> at
> scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.pollAndExecAll(ForkJoinPool.java:1253)
> at
> scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1346)
> at
> scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
> at
> scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
> Caused by: org.apache.flink.streaming.runtime.tasks.StreamTaskException:
> Cannot instantiate user function.
> at
> org.apache.flink.streaming.api.graph.StreamConfig.getStreamOperator(StreamConfig.java:209)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:186)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:559)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Ignite grid name thread local
> must be set or this method should be accessed under
> org.apache.ignite.thread.IgniteThread
> at
> org.apache.ignite.internal.IgnitionEx.localIgnite(IgnitionEx.java:1296)
> at
> org.apache.ignite.internal.GridLoggerProxy.readResolve(GridLoggerProxy.java:207)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1148)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1810)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> at
> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000)
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> at
> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000)
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
> at
> org.apache.flink.util.InstantiationUtil.deserializeObject(InstantiationUtil.java:290)
> at
> org.apache.flink.util.InstantiationUtil.readObjectFromConfig(InstantiationUtil.java:248)
> at
> org.apache.flink.streaming.api.graph.StreamConfig.getStreamOperator(StreamConfig.java:194)
> ... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2355) Hadoop client should be able to failover in case of server crash.
[
https://issues.apache.org/jira/browse/IGNITE-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554712#comment-15554712
]
Taras Ledkov edited comment on IGNITE-2355 at 10/7/16 4:27 PM:
---
Probably configuration properties, according with HDFS HA & Cloudera map-reduce
HA:
{code}
mapred.job.tracker
ignite0
ignite.servers.ignite0
srv0,srv1
ignite.server-addr.ignite0.srv0
:
ignite.server-addr.ignite0.srv1
:
...
{code}
was (Author: tledkov-gridgain):
Probably configuration properties, according with HDFS HA & Cloudera map-reduce
HA:
{code}
mapred.job.tracker
ignite0
ignite.servers.ignite0
srv0,srv1
ignite.server-addr.ignite0.srv0
:
ignite.server-addr.ignite0.srv1
:
...
{code}
> Hadoop client should be able to failover in case of server crash.
> -
>
> Key: IGNITE-2355
> URL: https://issues.apache.org/jira/browse/IGNITE-2355
> Project: Ignite
> Issue Type: Sub-task
> Components: hadoop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Critical
> Labels: roadmap
> Fix For: 2.0
>
>
> Currently we explicitly specify a single IP address of Ignite server for map
> reduce.
> If it goes down, no jobs can be submitted anymore.
> Looks like we should give user ability to specify multiple addresses, and
> failover between them. Our thin client (which underlies Hadoop client) is
> already able to accept multiple addresses.
> Look at Hadoop HA first to get an ideas on how to configure multiple
> addresses.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-4034) Get rid of specialized methods in platform targets
[ https://issues.apache.org/jira/browse/IGNITE-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1506#comment-1506 ] Pavel Tupitsyn edited comment on IGNITE-4034 at 10/7/16 4:16 PM: - Done: Cache, Compute, Queries, Streamer, Messaging, Cluster (including Ignite C++) Remaining: Transactions, Events, Services, Atomics was (Author: ptupitsyn): Done: Cache, Compute, Queries, Streamer, Messaging, Cluster Remaining: Transactions, Events, Services, Atomics > Get rid of specialized methods in platform targets > -- > > Key: IGNITE-4034 > URL: https://issues.apache.org/jira/browse/IGNITE-4034 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > Most .NET -> Java calls go through common PlatformTarget InOut* methods. But > some simple operations have dedicated JNI calls, like PlatformCache.clear(). > Refactor these operations to use common methods to unify the logic and allow > interface separation in IGNITE-4027. > This will also reduce the amount of C++ code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4034) Get rid of specialized methods in platform targets
[ https://issues.apache.org/jira/browse/IGNITE-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1506#comment-1506 ] Pavel Tupitsyn commented on IGNITE-4034: Done: Cache, Compute, Queries, Streamer, Messaging, Cluster Remaining: Transactions, Events, Services, Atomics > Get rid of specialized methods in platform targets > -- > > Key: IGNITE-4034 > URL: https://issues.apache.org/jira/browse/IGNITE-4034 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > Most .NET -> Java calls go through common PlatformTarget InOut* methods. But > some simple operations have dedicated JNI calls, like PlatformCache.clear(). > Refactor these operations to use common methods to unify the logic and allow > interface separation in IGNITE-4027. > This will also reduce the amount of C++ code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4045) .NET: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn reassigned IGNITE-4045:
--
Assignee: (was: Pavel Tupitsyn)
> .NET: Support DML API
> -
>
> Key: IGNITE-4045
> URL: https://issues.apache.org/jira/browse/IGNITE-4045
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Reporter: Denis Magda
> Labels: roadmap
> Fix For: 1.9
>
>
> Ignite's Java component will provide support for DML soon (IGNITE-2294). At
> she same time DML will be supported at the level of ODBC and JDBC drivers.
> As the next step we should include the similar functionality into Ignite.NET
> by doing the following:
> - Implement DML API;
> - Enhance {{QueryExample.cs}} by doing INSERTs instead of cache.puts and
> adding UPDATE and DELETE operation examples.
> - Add documentation to Ignite.NET readme.io covering the feature. Most like
> most of the content can be take from the general documentation when this
> ticket IGNITE-4018 is ready.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[
https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1275#comment-1275
]
Dmitriy Govorukhin commented on IGNITE-2079:
I see, thanks for review, in future i will try do not make mistakes in
Codestyle.
> GridCacheIoManager eats exception trail if it falls into the directed case
> --
>
> Key: IGNITE-2079
> URL: https://issues.apache.org/jira/browse/IGNITE-2079
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Dmitriy Govorukhin
> Labels: ignite-3424
> Fix For: 1.8
>
> Attachments: IgniteCacheP2pUnmarshallingContinuousQueryErrorTest.java
>
>
> During a recent test I have run into an issue where a storage disabled client
> of a Fabric that has services deployed for which the client does not have the
> fabric in the class path failed with the following exception:
> com.company.fabric.HelloWorldTest STANDARD_ERROR
> Nov 08, 2015 6:15:20 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to process message
> [senderId=30775397-457a-400f-a6c9-077c9e762d61, messageType=class
> o.a.i.i.processors.cache.query.GridCacheQueryResponse]
> class org.apache.ignite.IgniteCheckedException: Failed to send response to
> node. Unsupported direct type [message=GridCacheQueryResponse [finished=true,
> reqId=5, err=null, fields=false, metadata=null]]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:546)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:272)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:77)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1078)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2302)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:992)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:106)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:961)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> This unfortunately gives me 0 information to work on to resolve the issue, as
> the original unmarshalling exception (from the JdkMarshaller) was eaten as
> this is the code for the default process failed message:
> default:
> throw new IgniteCheckedException("Failed to send response to node.
> Unsupported direct type [message="
> + msg + "]");
> }
> you should also include the original stack from msg.getError() in the newly
> thrown IgniteCheckedException
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[
https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1192#comment-1192
]
Anton Vinogradov edited comment on IGNITE-2079 at 10/7/16 2:18 PM:
---
Dmitriy,
I've checked and refactored your changes (Codestyle fixed and Test refactored)
Please review my changes.
was (Author: avinogradov):
Dmitry,
I've checked and refactored your changes (Codestyle fixed and Test refactored)
Please review my changes.
> GridCacheIoManager eats exception trail if it falls into the directed case
> --
>
> Key: IGNITE-2079
> URL: https://issues.apache.org/jira/browse/IGNITE-2079
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Dmitriy Govorukhin
> Labels: ignite-3424
> Fix For: 1.8
>
> Attachments: IgniteCacheP2pUnmarshallingContinuousQueryErrorTest.java
>
>
> During a recent test I have run into an issue where a storage disabled client
> of a Fabric that has services deployed for which the client does not have the
> fabric in the class path failed with the following exception:
> com.company.fabric.HelloWorldTest STANDARD_ERROR
> Nov 08, 2015 6:15:20 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to process message
> [senderId=30775397-457a-400f-a6c9-077c9e762d61, messageType=class
> o.a.i.i.processors.cache.query.GridCacheQueryResponse]
> class org.apache.ignite.IgniteCheckedException: Failed to send response to
> node. Unsupported direct type [message=GridCacheQueryResponse [finished=true,
> reqId=5, err=null, fields=false, metadata=null]]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:546)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:272)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:77)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1078)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2302)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:992)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:106)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:961)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> This unfortunately gives me 0 information to work on to resolve the issue, as
> the original unmarshalling exception (from the JdkMarshaller) was eaten as
> this is the code for the default process failed message:
> default:
> throw new IgniteCheckedException("Failed to send response to node.
> Unsupported direct type [message="
> + msg + "]");
> }
> you should also include the original stack from msg.getError() in the newly
> thrown IgniteCheckedException
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[
https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1192#comment-1192
]
Anton Vinogradov commented on IGNITE-2079:
--
Dmitry,
I've checked and refactored your changes (Codestyle fixed and Test refactored)
Please review my changes.
> GridCacheIoManager eats exception trail if it falls into the directed case
> --
>
> Key: IGNITE-2079
> URL: https://issues.apache.org/jira/browse/IGNITE-2079
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Dmitriy Govorukhin
> Labels: ignite-3424
> Fix For: 1.8
>
> Attachments: IgniteCacheP2pUnmarshallingContinuousQueryErrorTest.java
>
>
> During a recent test I have run into an issue where a storage disabled client
> of a Fabric that has services deployed for which the client does not have the
> fabric in the class path failed with the following exception:
> com.company.fabric.HelloWorldTest STANDARD_ERROR
> Nov 08, 2015 6:15:20 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to process message
> [senderId=30775397-457a-400f-a6c9-077c9e762d61, messageType=class
> o.a.i.i.processors.cache.query.GridCacheQueryResponse]
> class org.apache.ignite.IgniteCheckedException: Failed to send response to
> node. Unsupported direct type [message=GridCacheQueryResponse [finished=true,
> reqId=5, err=null, fields=false, metadata=null]]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:546)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:272)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:77)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1078)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2302)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:992)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:106)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:961)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> This unfortunately gives me 0 information to work on to resolve the issue, as
> the original unmarshalling exception (from the JdkMarshaller) was eaten as
> this is the code for the default process failed message:
> default:
> throw new IgniteCheckedException("Failed to send response to node.
> Unsupported direct type [message="
> + msg + "]");
> }
> you should also include the original stack from msg.getError() in the newly
> thrown IgniteCheckedException
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2079) GridCacheIoManager eats exception trail if it falls into the directed case
[
https://issues.apache.org/jira/browse/IGNITE-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1186#comment-1186
]
Dmitriy Govorukhin commented on IGNITE-2079:
[~avinogradov] Hi Anton, could you please review my changes.
> GridCacheIoManager eats exception trail if it falls into the directed case
> --
>
> Key: IGNITE-2079
> URL: https://issues.apache.org/jira/browse/IGNITE-2079
> Project: Ignite
> Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Dmitriy Govorukhin
> Labels: ignite-3424
> Fix For: 1.8
>
> Attachments: IgniteCacheP2pUnmarshallingContinuousQueryErrorTest.java
>
>
> During a recent test I have run into an issue where a storage disabled client
> of a Fabric that has services deployed for which the client does not have the
> fabric in the class path failed with the following exception:
> com.company.fabric.HelloWorldTest STANDARD_ERROR
> Nov 08, 2015 6:15:20 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Failed to process message
> [senderId=30775397-457a-400f-a6c9-077c9e762d61, messageType=class
> o.a.i.i.processors.cache.query.GridCacheQueryResponse]
> class org.apache.ignite.IgniteCheckedException: Failed to send response to
> node. Unsupported direct type [message=GridCacheQueryResponse [finished=true,
> reqId=5, err=null, fields=false, metadata=null]]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processFailedMessage(GridCacheIoManager.java:546)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:272)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:77)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1078)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2302)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:992)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:106)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:961)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> This unfortunately gives me 0 information to work on to resolve the issue, as
> the original unmarshalling exception (from the JdkMarshaller) was eaten as
> this is the code for the default process failed message:
> default:
> throw new IgniteCheckedException("Failed to send response to node.
> Unsupported direct type [message="
> + msg + "]");
> }
> you should also include the original stack from msg.getError() in the newly
> thrown IgniteCheckedException
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4047) CQ skips events if autoUnsubscribe flag was set to false
[
https://issues.apache.org/jira/browse/IGNITE-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Tikhonov updated IGNITE-4047:
-
Attachment: IGNITE_4047_Test.patch
> CQ skips events if autoUnsubscribe flag was set to false
>
>
> Key: IGNITE-4047
> URL: https://issues.apache.org/jira/browse/IGNITE-4047
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.7
>Reporter: Nikolay Tikhonov
> Attachments: IGNITE_4047_Test.patch
>
>
> CQ skips events after topology change, if {{autoUnsubscribe}} flag was set to
> {{false}}. Test attached.
> See
> http://apache-ignite-users.70518.x6.nabble.com/CacheContinuousQuery-did-not-work-after-the-second-server-node-joinned-into-the-topology-td8011.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4047) CQ skips events if autoUnsubscribe flag was set to false
Nikolay Tikhonov created IGNITE-4047:
Summary: CQ skips events if autoUnsubscribe flag was set to false
Key: IGNITE-4047
URL: https://issues.apache.org/jira/browse/IGNITE-4047
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 1.7
Reporter: Nikolay Tikhonov
CQ skips events after topology change, if {{autoUnsubscribe}} flag was set to
{{false}}. Test attached.
See
http://apache-ignite-users.70518.x6.nabble.com/CacheContinuousQuery-did-not-work-after-the-second-server-node-joinned-into-the-topology-td8011.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2355) Hadoop client should be able to failover in case of server crash.
[
https://issues.apache.org/jira/browse/IGNITE-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554712#comment-15554712
]
Taras Ledkov edited comment on IGNITE-2355 at 10/7/16 12:01 PM:
Probably configuration properties, according with HDFS HA & Cloudera map-reduce
HA:
{code}
mapred.job.tracker
ignite0
ignite.servers.ignite0
srv0,srv1
ignite.server-addr.ignite0.srv0
:
ignite.server-addr.ignite0.srv1
:
...
{code}
was (Author: tledkov-gridgain):
Probably configuration properties, according with HDFS HA & Cloudera map-reduce
HA:
{code}
mapred.job.tracker
ignite0
ignite.servers.ignite0
srv0,srv1
ignite.server-addr.ignite0.srv0
:
ignite.server-addr.ignite0.srv1
:
...
{code}
> Hadoop client should be able to failover in case of server crash.
> -
>
> Key: IGNITE-2355
> URL: https://issues.apache.org/jira/browse/IGNITE-2355
> Project: Ignite
> Issue Type: Sub-task
> Components: hadoop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Critical
> Labels: roadmap
> Fix For: 2.0
>
>
> Currently we explicitly specify a single IP address of Ignite server for map
> reduce.
> If it goes down, no jobs can be submitted anymore.
> Looks like we should give user ability to specify multiple addresses, and
> failover between them. Our thin client (which underlies Hadoop client) is
> already able to accept multiple addresses.
> Look at Hadoop HA first to get an ideas on how to configure multiple
> addresses.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2355) Hadoop client should be able to failover in case of server crash.
[
https://issues.apache.org/jira/browse/IGNITE-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554712#comment-15554712
]
Taras Ledkov edited comment on IGNITE-2355 at 10/7/16 12:01 PM:
Probably configuration properties, according with HDFS HA & Cloudera map-reduce
HA:
{code}
mapred.job.tracker
ignite0
ignite.servers.ignite0
srv0,srv1
ignite.server-addr.ignite0.srv0
:
ignite.server-addr.ignite0.srv1
:
...
{code}
was (Author: tledkov-gridgain):
Probably configuration properties:
{code}
ignite.clusters
ig0,ig1
ignite.cluster.servers.ig0
srv0,srv1
ignite.cluster.server-addr.ig0.srv0
:
ignite.cluster.server-addr.ig0.srv1
:
...
{code}
> Hadoop client should be able to failover in case of server crash.
> -
>
> Key: IGNITE-2355
> URL: https://issues.apache.org/jira/browse/IGNITE-2355
> Project: Ignite
> Issue Type: Sub-task
> Components: hadoop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Critical
> Labels: roadmap
> Fix For: 2.0
>
>
> Currently we explicitly specify a single IP address of Ignite server for map
> reduce.
> If it goes down, no jobs can be submitted anymore.
> Looks like we should give user ability to specify multiple addresses, and
> failover between them. Our thin client (which underlies Hadoop client) is
> already able to accept multiple addresses.
> Look at Hadoop HA first to get an ideas on how to configure multiple
> addresses.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2355) Hadoop client should be able to failover in case of server crash.
[
https://issues.apache.org/jira/browse/IGNITE-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554712#comment-15554712
]
Taras Ledkov commented on IGNITE-2355:
--
Probably configuration properties:
{code}
ignite.clusters
ig0,ig1
ignite.cluster.servers.ig0
srv0,srv1
ignite.cluster.server-addr.ig0.srv0
:
ignite.cluster.server-addr.ig0.srv1
:
...
{code}
> Hadoop client should be able to failover in case of server crash.
> -
>
> Key: IGNITE-2355
> URL: https://issues.apache.org/jira/browse/IGNITE-2355
> Project: Ignite
> Issue Type: Sub-task
> Components: hadoop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Critical
> Labels: roadmap
> Fix For: 2.0
>
>
> Currently we explicitly specify a single IP address of Ignite server for map
> reduce.
> If it goes down, no jobs can be submitted anymore.
> Looks like we should give user ability to specify multiple addresses, and
> failover between them. Our thin client (which underlies Hadoop client) is
> already able to accept multiple addresses.
> Look at Hadoop HA first to get an ideas on how to configure multiple
> addresses.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3963) FlinkIgniteSinkSelfTest fails with exception IllegalArgumentException
[
https://issues.apache.org/jira/browse/IGNITE-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554688#comment-15554688
]
Andrey Gura commented on IGNITE-3963:
-
{quote}Thank you for reviewing the PR and sharing your feedback. I have
modified the PR as per comments.{quote}
Thanks for contribution! Looks good for me. Could you please merge it to master
branch.
{quote}Yes, the fields cacheName, igniteCfgFile and stopped are static as we
have used static inner class SinkContext. IgniteSink supports streaming data
from flink clusters to single cache but if required I can modify it to work
with multiple caches.{quote}
I think it could be made in separate task.
> FlinkIgniteSinkSelfTest fails with exception IllegalArgumentException
> -
>
> Key: IGNITE-3963
> URL: https://issues.apache.org/jira/browse/IGNITE-3963
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Saikat Maitra
>Assignee: Saikat Maitra
>Priority: Trivial
> Fix For: 1.8
>
>
> FlinkIgniteSinkSelfTest fails with exception IllegalArgumentException.
> {code}
> [21:30:31,387][INFO ][main][root] >>> Stopping test class:
> FlinkIgniteSinkSelfTest <<<
> org.apache.flink.runtime.client.JobExecutionException: Job execution failed.
> at
> org.apache.flink.runtime.jobmanager.JobManager$$anonfun$handleMessage$1$$anonfun$applyOrElse$7.apply$mcV$sp(JobManager.scala:714)
> at
> org.apache.flink.runtime.jobmanager.JobManager$$anonfun$handleMessage$1$$anonfun$applyOrElse$7.apply(JobManager.scala:660)
> at
> org.apache.flink.runtime.jobmanager.JobManager$$anonfun$handleMessage$1$$anonfun$applyOrElse$7.apply(JobManager.scala:660)
> at
> scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)
> at
> scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24)
> at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:41)
> at
> akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:401)
> at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
> at
> scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.pollAndExecAll(ForkJoinPool.java:1253)
> at
> scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1346)
> at
> scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
> at
> scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
> Caused by: org.apache.flink.streaming.runtime.tasks.StreamTaskException:
> Cannot instantiate user function.
> at
> org.apache.flink.streaming.api.graph.StreamConfig.getStreamOperator(StreamConfig.java:209)
> at
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:186)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:559)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: Ignite grid name thread local
> must be set or this method should be accessed under
> org.apache.ignite.thread.IgniteThread
> at
> org.apache.ignite.internal.IgnitionEx.localIgnite(IgnitionEx.java:1296)
> at
> org.apache.ignite.internal.GridLoggerProxy.readResolve(GridLoggerProxy.java:207)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1148)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1810)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> at
> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000)
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> at
> java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2000)
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1924)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1801)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
> at
> org.apache.flink.util.InstantiationUtil.deserializeObject(InstantiationUtil.java:290)
> at
>
[jira] [Assigned] (IGNITE-2355) Hadoop client should be able to failover in case of server crash.
[ https://issues.apache.org/jira/browse/IGNITE-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reassigned IGNITE-2355: Assignee: Taras Ledkov > Hadoop client should be able to failover in case of server crash. > - > > Key: IGNITE-2355 > URL: https://issues.apache.org/jira/browse/IGNITE-2355 > Project: Ignite > Issue Type: Sub-task > Components: hadoop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Critical > Labels: roadmap > Fix For: 2.0 > > > Currently we explicitly specify a single IP address of Ignite server for map > reduce. > If it goes down, no jobs can be submitted anymore. > Looks like we should give user ability to specify multiple addresses, and > failover between them. Our thin client (which underlies Hadoop client) is > already able to accept multiple addresses. > Look at Hadoop HA first to get an ideas on how to configure multiple > addresses. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3862) GridServiceProxy invocation never times out
[
https://issues.apache.org/jira/browse/IGNITE-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Karachentsev reassigned IGNITE-3862:
---
Assignee: Dmitry Karachentsev
> GridServiceProxy invocation never times out
> ---
>
> Key: IGNITE-3862
> URL: https://issues.apache.org/jira/browse/IGNITE-3862
> Project: Ignite
> Issue Type: Bug
> Components: managed services
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Dmitry Karachentsev
>Priority: Critical
> Fix For: 1.8
>
>
> {{GridServiceProxy}} uses compute for remote invocation. In some cases an
> exception on server side can cause the closure execution never finish. For
> example, this happens when the exception is thrown during the serialization
> of the result.
> Need to add additional {{IgniteServices.serviceProxy(..)}} method that will
> additionally allow to specify custom timeout.
> This timeout should limit the number of retries (there is an infinite loop
> now) and also be passed to {{callAsyncNoFailover}} to avoid hangs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-3985) Web Console: Refactor test database init in backend tests.
[ https://issues.apache.org/jira/browse/IGNITE-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov closed IGNITE-3985. -- Assignee: (was: Andrey Novikov) > Web Console: Refactor test database init in backend tests. > -- > > Key: IGNITE-3985 > URL: https://issues.apache.org/jira/browse/IGNITE-3985 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 1.8 >Reporter: Andrey Novikov >Priority: Minor > Fix For: 1.8 > > > Need simplify database init before test. As example may be used > modules/web-console/backend/test/unit/AuthService.test.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1924) Incomplete marshaller cache rebalancing causes Grid hangs
[ https://issues.apache.org/jira/browse/IGNITE-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554526#comment-15554526 ] Semen Boikov commented on IGNITE-1924: -- Looks good now, just move tests you added in IgniteCacheFailoverTestSuiteSsl in IgniteSpiCommunicationSelfTestSuite. > Incomplete marshaller cache rebalancing causes Grid hangs > - > > Key: IGNITE-1924 > URL: https://issues.apache.org/jira/browse/IGNITE-1924 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Priority: Critical > Labels: Muted_test > Fix For: 1.8 > > > End of the log. > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,947][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=108bffdb-1c1e-49aa-9525-b434784fa001, partitionsCount=7, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,962][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=20660c29-91a1-4279-9dc1-88d192bc6002, partitionsCount=6, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,962][INFO > ][exchange-worker-#220584%tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Starting rebalancing > [cache=ignite-marshaller-sys-cache, mode=SYNC, > fromNode=00b3a75a-074d-46a5-a158-3956c0ec4000, partitionsCount=7, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], updateSeq=1] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,963][INFO > ][ignite-#220587%marshaller-cache-tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Completed rebalancing > [cache=ignite-marshaller-sys-cache, > fromNode=00b3a75a-074d-46a5-a158-3956c0ec4000, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], time=21 ms] > [11:49:32] : [org.apache.ignite:ignite-core] [11:49:32,963][INFO > ][ignite-#220586%marshaller-cache-tcp.IgniteCacheSslStartStopSelfTest3%][GridDhtPartitionDemander] > Completed rebalancing > [cache=ignite-marshaller-sys-cache, > fromNode=108bffdb-1c1e-49aa-9525-b434784fa001, > topology=AffinityTopologyVersion [topVer=594, minorTopVer=0], time=21 ms] > Hang on: > [11:51:56] : [org.apache.ignite:ignite-core] Thread > [name="ignite-#220562%sys-tcp.IgniteCacheSslStartStopSelfTest3%", id=287517, > state=WAITING, blockCnt=0, waitCnt=3] > [11:51:56] : [org.apache.ignite:ignite-core] Lock > [object=o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$RebalanceFuture@b402f89, > ownerName=null, ownerId=-1] > [11:51:56] : [org.apache.ignite:ignite-core] at > sun.misc.Unsafe.park(Native Method) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994) > [11:51:56] : [org.apache.ignite:ignite-core] at > java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.waitForCacheRebalancing(GridDhtPartitionDemander.java:265) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander.access$400(GridDhtPartitionDemander.java:85) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$3.call(GridDhtPartitionDemander.java:323) > [11:51:56] : [org.apache.ignite:ignite-core] at > o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionDemander$3.call(GridDhtPartitionDemander.java:320) >
[jira] [Updated] (IGNITE-4045) .NET: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-4045:
---
Summary: .NET: Support DML API (was: .Net: Support DML API)
> .NET: Support DML API
> -
>
> Key: IGNITE-4045
> URL: https://issues.apache.org/jira/browse/IGNITE-4045
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Labels: roadmap
> Fix For: 1.9
>
>
> Ignite's Java component will provide support for DML soon (IGNITE-2294). At
> she same time DML will be supported at the level of ODBC and JDBC drivers.
> As the next step we should include the similar functionality into Ignite.NET
> by doing the following:
> - Implement DML API;
> - Enhance {{QueryExample.cs}} by doing INSERTs instead of cache.puts and
> adding UPDATE and DELETE operation examples.
> - Add documentation to Ignite.NET readme.io covering the feature. Most like
> most of the content can be take from the general documentation when this
> ticket IGNITE-4018 is ready.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4045) .Net: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4045:
Labels: roadmap (was: )
> .Net: Support DML API
> -
>
> Key: IGNITE-4045
> URL: https://issues.apache.org/jira/browse/IGNITE-4045
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Labels: roadmap
> Fix For: 1.9
>
>
> Ignite's Java component will provide support for DML soon (IGNITE-2294). At
> she same time DML will be supported at the level of ODBC and JDBC drivers.
> As the next step we should include the similar functionality into Ignite.NET
> by doing the following:
> - Implement DML API;
> - Enhance {{QueryExample.cs}} by doing INSERTs instead of cache.puts and
> adding UPDATE and DELETE operation examples.
> - Add documentation to Ignite.NET readme.io covering the feature. Most like
> most of the content can be take from the general documentation when this
> ticket IGNITE-4018 is ready.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3303) Apache Flink Integration - Flink source to run a continuous query against one or multiple caches
[ https://issues.apache.org/jira/browse/IGNITE-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554281#comment-15554281 ] Anton Vinogradov commented on IGNITE-3303: -- Hi, it is java version "1.8.0_91" Java(TM) SE Runtime Environment (build 1.8.0_91-b15) Java HotSpot(TM) 64-Bit Server VM (build 25.91-b15, mixed mode) > Apache Flink Integration - Flink source to run a continuous query against one > or multiple caches > > > Key: IGNITE-3303 > URL: https://issues.apache.org/jira/browse/IGNITE-3303 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Saikat Maitra >Assignee: Saikat Maitra > Attachments: Screen Shot 2016-10-07 at 12.44.47 AM.png, > testFlinkIgniteSourceWithLargeBatch.log > > > Apache Flink integration > +++ *Ignite as a bidirectional Connector* +++ > As a Flink source => run a continuous query against one or multiple > caches [4]. > Related discussion : > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4046) C++: Support DML API
[
https://issues.apache.org/jira/browse/IGNITE-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4046:
Labels: roadmap (was: )
> C++: Support DML API
>
>
> Key: IGNITE-4046
> URL: https://issues.apache.org/jira/browse/IGNITE-4046
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Labels: roadmap
> Fix For: 1.9
>
>
> Ignite's Java component will provide support for DML soon (IGNITE-2294). At
> she same time DML will be supported at the level of ODBC and JDBC drivers.
> As the next step we should include the similar functionality into Ignite.C++
> by doing the following:
> - Implement DML API;
> - Enhance {{query_example.cpp}} by doing INSERTs instead of cache.puts and
> adding UPDATE and DELETE operation examples.
> - Add documentation to Ignite.C++ readme.io covering the feature. Most like
> most of the content can be take from the general documentation when this
> ticket IGNITE-4018 is ready.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
