Re: cache update from .NET client to Java cluster

[kfeerick]

cool - i thought i'd tried that but perhaps screwed it up  will have another
look



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/cache-update-from-NET-client-to-Java-cluster-tp11217p11336.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Connection not established

[Pavel Tupitsyn]

Hi,

Looks like you have mixed up Spring XML and .NET config XML.
Moreover, you don't provide any configuration file when starting Ignite
with Ignition.Start();

To work with ODBC from .NET, you have to configure ODBC in a Spring XML
file (NOT app.config) like this:



http://www.springframework.org/schema/beans";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd";>

  

  



then provide path to that file Ignition.Start("my-file.xml");

On Tue, Mar 21, 2017 at 7:41 AM, kavitha  wrote:

> Hi,
>
> My Code in app.config file.
>
> 
> 
> 
>  />
> 
>  class="org.apache.ignite.configuration.IgniteConfiguration">
>
>   
> 
>   
>
> 
> 
>
> packages.config file
>
> 
> 
>   
> 
>
> code in class file
>
> class Program
> {
> static void Main(string[] args)
> {
> IIgnite ignite = Ignition.Start();
>OdbcConnection con = new OdbcConnection("DRIVER={Apache
> Ignite};ADDRESS=localhost:10800;CACHE=MyCache");
> con.Open();
> con.Close();
> }
> }
>
> Still I got ERROR [08001] Failed to establish connection with
> the host.
>
> Please tell me how can I resolve this?
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Connection-not-established-tp11303p11331.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: cache update from .NET client to Java cluster

[Pavel Tupitsyn]

I was able to run it and reproduce the problem.
If you add "Console.WriteLine("Cache size: " + cache.GetSize());" to the
end of C# program,
you'll see that there are two entries in the cache, because keys from Java
and C# are not considered equal.

To fix the problem, override GetHashCode/Equals in C# in the same manner as
in Java:

public override bool Equals(object obj)
{
if (ReferenceEquals(null, obj)) return false;
if (ReferenceEquals(this, obj)) return true;
if (obj.GetType() != this.GetType()) return false;
return Id == ((MyClassKey) obj).Id;
}
 public override int GetHashCode()
{
return (int)(Id ^ (Id >> 32));
}


This way I get expected result in Java log:
CacheListener - UPDATED , object0 written from .NET


On Tue, Mar 21, 2017 at 7:55 AM, kfeerick <
kevin.feer...@ninemilefinancial.com> wrote:

> Here you go - hopefully you can spin this up in your favoured Java / C# IDE
> pretty easily.
>
> cache-duplicate-reproducer.zip
>  n11332/cache-duplicate-reproducer.zip>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/cache-update-from-NET-client-to-
> Java-cluster-tp11217p11332.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: cache update from .NET client to Java cluster

[kfeerick]

Here you go - hopefully you can spin this up in your favoured Java / C# IDE
pretty easily.

cache-duplicate-reproducer.zip

  



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/cache-update-from-NET-client-to-Java-cluster-tp11217p11332.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Connection not established

[kavitha]

Hi,

My Code in app.config file.



 



  
  

  
  



packages.config file



  


code in class file

class Program
{
static void Main(string[] args)
{
IIgnite ignite = Ignition.Start();
   OdbcConnection con = new OdbcConnection("DRIVER={Apache
Ignite};ADDRESS=localhost:10800;CACHE=MyCache");
con.Open();
con.Close();
}
}

Still I got ERROR [08001] Failed to establish connection with
the host.

Please tell me how can I resolve this?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Connection-not-established-tp11303p11331.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: IGNITE-4106

[Anil]

Hi Andrew,

#1 - it is very simple select query - select * from person hwere personid =
'something';
i just ran the query in for loop and noticed the results are not same.

#2 - it is stable topology. swap is configured. but this test was done when
full load is completed and some compute job going on for other cache.

Please let me know if you have any questions. thanks.

Thanks.

On 20 March 2017 at 21:07, Andrey Mashenkov 
wrote:

> Hi Anil,
>
> 1. Would you please share sql query text?
>
> 2. Is it happening on unstable topology or during rebalancing? Or may be
> eviction\expire policy or swap is configured?
>
> On Mon, Mar 20, 2017 at 5:41 PM, Anil  wrote:
>
>> Yes. i am using partition cache only with no joins :)
>>
>> how about #2 ?
>>
>> On 20 March 2017 at 19:20, Andrey Mashenkov 
>> wrote:
>>
>>> Hi Anil,
>>>
>>> I should although mention that Replicated caches can participate in same
>>> query with partitioned caches regardless a degree of parallelizm.
>>> This limitation relates to partitioned caches only.
>>>
>>> On Mon, Mar 20, 2017 at 3:54 PM, Andrey Mashenkov <
>>> andrey.mashen...@gmail.com> wrote:
>>>
 Hi Anil,

 It is ok. Doc says *"If a query contains JOINs, then all the
 participating caches must have the same degree of parallelism.".*
 Possibly, it is easy to fix but there can be unobvious limitations, so
 we need a time to make a POC.
 I believe, it will be fixed in future releases.

 On Mon, Mar 20, 2017 at 1:11 PM, Anil  wrote:

> Hi Andrey,
>
> I see few more issues with IGNITE-4826
>
> 1. queryParallelism should be used for all caches for which queries
> are used other it throws following exception.
>
> Caused by: java.sql.SQLException: Failed to query Ignite.
> at org.apache.ignite.internal.jdb
> c2.JdbcStatement.executeQuery(JdbcStatement.java:131)
> at org.apache.ignite.internal.jdb
> c2.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:76)
> at org.apache.commons.dbcp2.Deleg
> atingPreparedStatement.executeQuery(DelegatingPreparedStatem
> ent.java:83)
> at org.apache.commons.dbcp2.Deleg
> atingPreparedStatement.executeQuery(DelegatingPreparedStatem
> ent.java:83)
>
> Caused by: javax.cache.CacheException: class
> org.apache.ignite.IgniteException: Using indexes with different
> parallelism levels in same query is forbidden.
> at org.apache.ignite.internal.pro
> cessors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:760)
> at org.apache.ignite.internal.jdb
> c2.JdbcQueryTask.call(JdbcQueryTask.java:161)
> at org.apache.ignite.internal.jdb
> c2.JdbcStatement.executeQuery(JdbcStatement.java:116)
> ... 13 more
> 2. query is not returning same result if it is hit number of times.
>
> please let me know if these are known issues.
>
> Thanks
>



 --
 Best regards,
 Andrey V. Mashenkov

>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Andrey V. Mashenkov
>>>
>>
>>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>

Re: ignite messaging disconnection behaviour

[kfeerick]

Hi Dmitry,
Thanks for the suggestion. It does not seem to make a difference and the
calling thread still seems to block before an exception gets thrown from the
TcpCommunicationSpi

It appears you can tweak how quickly the exception gets throws by adjusting
the failureDetectionTimeout on the cache configuration however this is not
that desirable as we run across a variety of network topologies and don't
want to tune this value for all our cache instances. We really do want to
fire and forget if someone is listening, great. If they're not no problem
either.

I've written a quick example to demonstrate the behaviour - appreciate if
you could take a look and advise

Cheers
messaging-reproducer.zip

  





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-messaging-disconnection-behaviour-tp11218p11329.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

NullPointerException when using IGFS

[Joe Wang]

Hi!

I'm running into this stack when trying to read through IGFS to an
underlying HDFS instance:

java.lang.NullPointerException
at
org.apache.ignite.internal.processors.hadoop.impl.igfs.HadoopIgfsInputStream$FetchBufferPart.flatten(HadoopIgfsInputStream.java:458)
at
org.apache.ignite.internal.processors.hadoop.impl.igfs.HadoopIgfsInputStream$DoubleFetchBuffer.flatten(HadoopIgfsInputStream.java:511)
at
org.apache.ignite.internal.processors.hadoop.impl.igfs.HadoopIgfsInputStream.read(HadoopIgfsInputStream.java:177)
at java.io.DataInputStream.read(DataInputStream.java:100)

and I'm just wondering what the expected behavior of IGFS was. I'm standing
up an ignite cluster (with empty caches), configuring the secondary
filesystem to be an HDFS endpoint, and then trying to read a file from
IGFS. Was IGFS designed to handle this scenario?

Thanks!

Joe

Re: REST service command LOG

[javastuff....@gmail.com]

Created minor ticket IGNITE-4845




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/REST-service-command-LOG-tp10148p11325.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Apache Ignite with log4J2 KafkaAppender - class not found

[lieven]

Just found out that Apache Ignite is using log4j2 version 2.3, while the
actual version for log4J2 is 2.8.
In the version 2.3 there is no support for KafkaAppender. I can reproduce
the issue in a separate Java program. 



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-with-log4J2-KafkaAppender-class-not-found-tp11296p11324.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

unsubscribe

[Landon Kuhn]

Re: Pessimistic TXN did not release lock on a key, all subsequent txns failed

[bintisepaha]

Andrey, would you be able to look at the attached errors and advice please?

Thanks,
Binti



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Pessimistic-TXN-did-not-release-lock-on-a-key-all-subsequent-txns-failed-tp10536p11322.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: IGNITE-4106

[Andrey Mashenkov]

Hi Anil,

1. Would you please share sql query text?

2. Is it happening on unstable topology or during rebalancing? Or may be
eviction\expire policy or swap is configured?

On Mon, Mar 20, 2017 at 5:41 PM, Anil  wrote:

> Yes. i am using partition cache only with no joins :)
>
> how about #2 ?
>
> On 20 March 2017 at 19:20, Andrey Mashenkov 
> wrote:
>
>> Hi Anil,
>>
>> I should although mention that Replicated caches can participate in same
>> query with partitioned caches regardless a degree of parallelizm.
>> This limitation relates to partitioned caches only.
>>
>> On Mon, Mar 20, 2017 at 3:54 PM, Andrey Mashenkov <
>> andrey.mashen...@gmail.com> wrote:
>>
>>> Hi Anil,
>>>
>>> It is ok. Doc says *"If a query contains JOINs, then all the
>>> participating caches must have the same degree of parallelism.".*
>>> Possibly, it is easy to fix but there can be unobvious limitations, so
>>> we need a time to make a POC.
>>> I believe, it will be fixed in future releases.
>>>
>>> On Mon, Mar 20, 2017 at 1:11 PM, Anil  wrote:
>>>
 Hi Andrey,

 I see few more issues with IGNITE-4826

 1. queryParallelism should be used for all caches for which queries are
 used other it throws following exception.

 Caused by: java.sql.SQLException: Failed to query Ignite.
 at org.apache.ignite.internal.jdbc2.JdbcStatement.executeQuery(
 JdbcStatement.java:131)
 at org.apache.ignite.internal.jdbc2.JdbcPreparedStatement.execu
 teQuery(JdbcPreparedStatement.java:76)
 at org.apache.commons.dbcp2.DelegatingPreparedStatement.execute
 Query(DelegatingPreparedStatement.java:83)
 at org.apache.commons.dbcp2.DelegatingPreparedStatement.execute
 Query(DelegatingPreparedStatement.java:83)

 Caused by: javax.cache.CacheException: class
 org.apache.ignite.IgniteException: Using indexes with different
 parallelism levels in same query is forbidden.
 at org.apache.ignite.internal.processors.cache.IgniteCacheProxy
 .query(IgniteCacheProxy.java:760)
 at org.apache.ignite.internal.jdbc2.JdbcQueryTask.call(JdbcQuer
 yTask.java:161)
 at org.apache.ignite.internal.jdbc2.JdbcStatement.executeQuery(
 JdbcStatement.java:116)
 ... 13 more
 2. query is not returning same result if it is hit number of times.

 please let me know if these are known issues.

 Thanks

>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Andrey V. Mashenkov
>>>
>>
>>
>>
>> --
>> Best regards,
>> Andrey V. Mashenkov
>>
>
>


-- 
Best regards,
Andrey V. Mashenkov

Re: IGNITE-4106

[Anil]

Yes. i am using partition cache only with no joins :)

how about #2 ?

On 20 March 2017 at 19:20, Andrey Mashenkov 
wrote:

> Hi Anil,
>
> I should although mention that Replicated caches can participate in same
> query with partitioned caches regardless a degree of parallelizm.
> This limitation relates to partitioned caches only.
>
> On Mon, Mar 20, 2017 at 3:54 PM, Andrey Mashenkov <
> andrey.mashen...@gmail.com> wrote:
>
>> Hi Anil,
>>
>> It is ok. Doc says *"If a query contains JOINs, then all the
>> participating caches must have the same degree of parallelism.".*
>> Possibly, it is easy to fix but there can be unobvious limitations, so we
>> need a time to make a POC.
>> I believe, it will be fixed in future releases.
>>
>> On Mon, Mar 20, 2017 at 1:11 PM, Anil  wrote:
>>
>>> Hi Andrey,
>>>
>>> I see few more issues with IGNITE-4826
>>>
>>> 1. queryParallelism should be used for all caches for which queries are
>>> used other it throws following exception.
>>>
>>> Caused by: java.sql.SQLException: Failed to query Ignite.
>>> at org.apache.ignite.internal.jdbc2.JdbcStatement.executeQuery(
>>> JdbcStatement.java:131)
>>> at org.apache.ignite.internal.jdbc2.JdbcPreparedStatement.execu
>>> teQuery(JdbcPreparedStatement.java:76)
>>> at org.apache.commons.dbcp2.DelegatingPreparedStatement.execute
>>> Query(DelegatingPreparedStatement.java:83)
>>> at org.apache.commons.dbcp2.DelegatingPreparedStatement.execute
>>> Query(DelegatingPreparedStatement.java:83)
>>>
>>> Caused by: javax.cache.CacheException: class
>>> org.apache.ignite.IgniteException: Using indexes with different
>>> parallelism levels in same query is forbidden.
>>> at org.apache.ignite.internal.processors.cache.IgniteCacheProxy
>>> .query(IgniteCacheProxy.java:760)
>>> at org.apache.ignite.internal.jdbc2.JdbcQueryTask.call(JdbcQuer
>>> yTask.java:161)
>>> at org.apache.ignite.internal.jdbc2.JdbcStatement.executeQuery(
>>> JdbcStatement.java:116)
>>> ... 13 more
>>> 2. query is not returning same result if it is hit number of times.
>>>
>>> please let me know if these are known issues.
>>>
>>> Thanks
>>>
>>
>>
>>
>> --
>> Best regards,
>> Andrey V. Mashenkov
>>
>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>

Re: IGNITE-4106

[Andrey Mashenkov]

Hi Anil,

I should although mention that Replicated caches can participate in same
query with partitioned caches regardless a degree of parallelizm.
This limitation relates to partitioned caches only.

On Mon, Mar 20, 2017 at 3:54 PM, Andrey Mashenkov <
andrey.mashen...@gmail.com> wrote:

> Hi Anil,
>
> It is ok. Doc says *"If a query contains JOINs, then all the
> participating caches must have the same degree of parallelism.".*
> Possibly, it is easy to fix but there can be unobvious limitations, so we
> need a time to make a POC.
> I believe, it will be fixed in future releases.
>
> On Mon, Mar 20, 2017 at 1:11 PM, Anil  wrote:
>
>> Hi Andrey,
>>
>> I see few more issues with IGNITE-4826
>>
>> 1. queryParallelism should be used for all caches for which queries are
>> used other it throws following exception.
>>
>> Caused by: java.sql.SQLException: Failed to query Ignite.
>> at org.apache.ignite.internal.jdbc2.JdbcStatement.executeQuery(
>> JdbcStatement.java:131)
>> at org.apache.ignite.internal.jdbc2.JdbcPreparedStatement.execu
>> teQuery(JdbcPreparedStatement.java:76)
>> at org.apache.commons.dbcp2.DelegatingPreparedStatement.execute
>> Query(DelegatingPreparedStatement.java:83)
>> at org.apache.commons.dbcp2.DelegatingPreparedStatement.execute
>> Query(DelegatingPreparedStatement.java:83)
>>
>> Caused by: javax.cache.CacheException: class
>> org.apache.ignite.IgniteException: Using indexes with different
>> parallelism levels in same query is forbidden.
>> at org.apache.ignite.internal.processors.cache.IgniteCacheProxy
>> .query(IgniteCacheProxy.java:760)
>> at org.apache.ignite.internal.jdbc2.JdbcQueryTask.call(JdbcQuer
>> yTask.java:161)
>> at org.apache.ignite.internal.jdbc2.JdbcStatement.executeQuery(
>> JdbcStatement.java:116)
>> ... 13 more
>> 2. query is not returning same result if it is hit number of times.
>>
>> please let me know if these are known issues.
>>
>> Thanks
>>
>
>
>
> --
> Best regards,
> Andrey V. Mashenkov
>



-- 
Best regards,
Andrey V. Mashenkov

Re: IGNITE-4106

[Andrey Mashenkov]

Hi Anil,

It is ok. Doc says *"If a query contains JOINs, then all the participating
caches must have the same degree of parallelism.".*
Possibly, it is easy to fix but there can be unobvious limitations, so we
need a time to make a POC.
I believe, it will be fixed in future releases.

On Mon, Mar 20, 2017 at 1:11 PM, Anil  wrote:

> Hi Andrey,
>
> I see few more issues with IGNITE-4826
>
> 1. queryParallelism should be used for all caches for which queries are
> used other it throws following exception.
>
> Caused by: java.sql.SQLException: Failed to query Ignite.
> at org.apache.ignite.internal.jdbc2.JdbcStatement.
> executeQuery(JdbcStatement.java:131)
> at org.apache.ignite.internal.jdbc2.JdbcPreparedStatement.
> executeQuery(JdbcPreparedStatement.java:76)
> at org.apache.commons.dbcp2.DelegatingPreparedStatement.
> executeQuery(DelegatingPreparedStatement.java:83)
> at org.apache.commons.dbcp2.DelegatingPreparedStatement.
> executeQuery(DelegatingPreparedStatement.java:83)
>
> Caused by: javax.cache.CacheException: class 
> org.apache.ignite.IgniteException:
> Using indexes with different parallelism levels in same query is forbidden.
> at org.apache.ignite.internal.processors.cache.
> IgniteCacheProxy.query(IgniteCacheProxy.java:760)
> at org.apache.ignite.internal.jdbc2.JdbcQueryTask.call(
> JdbcQueryTask.java:161)
> at org.apache.ignite.internal.jdbc2.JdbcStatement.
> executeQuery(JdbcStatement.java:116)
> ... 13 more
> 2. query is not returning same result if it is hit number of times.
>
> please let me know if these are known issues.
>
> Thanks
>



-- 
Best regards,
Andrey V. Mashenkov

Re: IGNITE-4106

[Anil]

Hi Andrey,

I see few more issues with IGNITE-4826

1. queryParallelism should be used for all caches for which queries are
used other it throws following exception.

Caused by: java.sql.SQLException: Failed to query Ignite.
at
org.apache.ignite.internal.jdbc2.JdbcStatement.executeQuery(JdbcStatement.java:131)
at
org.apache.ignite.internal.jdbc2.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:76)
at
org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:83)
at
org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:83)

Caused by: javax.cache.CacheException: class
org.apache.ignite.IgniteException: Using indexes with different parallelism
levels in same query is forbidden.
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:760)
at
org.apache.ignite.internal.jdbc2.JdbcQueryTask.call(JdbcQueryTask.java:161)
at
org.apache.ignite.internal.jdbc2.JdbcStatement.executeQuery(JdbcStatement.java:116)
... 13 more
2. query is not returning same result if it is hit number of times.

please let me know if these are known issues.

Thanks

Error: Cannot open include file:'noost/test/unit_test.hpp'

[kavitha]

Hi,
I tried to build Ignite.sln. But I got Cannot open include
file:'noost/test/unit_test.hpp' error.

 





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Error-Cannot-open-include-file-noost-test-unit-test-hpp-tp11315.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Apache Ignite with log4J2 KafkaAppender - class not found

[Lieven Merckx]

Is that log4j (1) Kafka Appender compatible with log4j2 ? To my
understanding there are completely differently developed. I could be wrong.

On Mon, Mar 20, 2017 at 9:30 AM, dkarachentsev 
wrote:

> Hi,
>
> I suppose you need kafka log4j appender [1] in classpath.
>
> [1] https://mvnrepository.com/artifact/org.apache.kafka/
> kafka-log4j-appender
>
> -Dmitry.
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Apache-Ignite-with-log4J2-
> KafkaAppender-class-not-found-tp11296p11307.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Client got stucked on get operation

[Alper Tekinalp]

Hi all.


We have 3 ignite servers. Server 1 works as standalone. Server 2 and 3
connects eachother as server but connects server 1 as client. In a point of
the time server 3 got stucked at:

  at sun.misc.Unsafe.park(Native Method)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
  at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
  at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
  at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
  at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:161)
  at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:119)
  at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.get0(GridDhtAtomicCache.java:488)
  at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4665)
  at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1388)
  at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:1121)
  at sun.reflect.GeneratedMethodAccessor634.invoke(Unknown Source)
  at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:606)
  at
com.evam.cache.client.CachePassthroughInvocationHandler.invokeInternal(CachePassthroughInvocationHandler.java:99)
  at
com.evam.cache.client.CachePassthroughInvocationHandler.invoke(CachePassthroughInvocationHandler.java:78)
  at com.sun.proxy.$Proxy56.get(Unknown Source)

when getting record from server 1. Long after that server 2 also got
stucked at the same trace and also server 2 and server 3 disconnects from
each other.

We investigated gc logs and there is not an unusual behaviour. One things
is server 1 logs errors as follows when server 2 and server 3 disconnects:

[ERROR] 2017-03-18 22:01:21.881 [sys-stripe-82-#83%cache-server%] msg -
Received message without registered handler (will ignore)
[msg=GridNearSingleGetRequest [futId=1490866022968, key=BinaryObjectImpl
[arr= true, ctx=false, start=0], partId=199, flags=1,
topVer=AffinityTopologyVersion [topVer=33, minorTopVer=455],
subjId=53293ebb-f01b-40b6-a060-bec4209e9c8a, taskNameHash=0, createTtl=0,
accessTtl=-1], node=53293ebb-f01b-40b6-a060-bec4209e9c8a,
locTopVer=AffinityTopologyVersion [topVer=33, minorTopVer=2937],
msgTopVer=AffinityTopologyVersion [topVer=33, minorTopVer=455],
cacheDesc=null]
Registered listeners:


Where should we look for the main cause of the problem? What can cause such
a behaviour? There seems nothing wrong on server 1 logs etc.

We use ignite 1.8.3.

-- 
Alper Tekinalp

Software Developer
Evam Streaming Analytics

Atatürk Mah. Turgut Özal Bulv.
Gardenya 5 Plaza K:6 Ataşehir
34758 İSTANBUL

Tel:  +90 216 455 01 53 Fax: +90 216 455 01 54
www.evam.com.tr

Re: Distributed callables: passing data and getting back results

[dkarachentsev]

Hi,

If your tasks use the same data, then REPLICATED cache will be the best
decision. But if you need for every compute task put new data to cache, it
will slowdown processing, because entries must be distributed, copied and
synchronized.

The same rule is applicable for compute results: if you need to reuse them,
then add to cache.

-Dmitry.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Distributed-callables-passing-data-and-getting-back-results-tp11224p11312.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: ignite messaging disconnection behaviour

[dkarachentsev]

Hi Kevin,

You may use IgniteMessaging in async mode:
IgniteMessaging msg = ignite.message().withAsync();
msg.sendOrdered("my-topic", objectToSend, 1);

In that case you'll not wait for sending message and reconnections in if
there was a failure.

-Dmitry.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-messaging-disconnection-behaviour-tp11218p11311.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Connection not established

[Igor Sapego]

This means exactly what it says - driver can't establish connection to the
node.

Most probably, you have not enabled OdbcProcessor for your node. You can
see documentation [1] to learn how to enable it.

[1] -
https://apacheignite.readme.io/docs/odbc-driver#section-cluster-configuration

On Mon, Mar 20, 2017 at 8:12 AM, kavitha  wrote:

> Hi,
>
> I tried to establish connection. But following error message displayed.
>
> My Code:
>
> class Program
> {
> static void Main(string[] args)
> {
> IIgnite ignite = Ignition.Start();
> OdbcConnection con = new OdbcConnection("DRIVER={Apache
> Ignite};ADDRESS= localhost:10800;CACHE=MyCache;");
> con.Open();
> }
> }
>
> Error:
> An unhandled exception of type 'System.Data.Odbc.OdbcException' occurred
> in
> System.Data.dll
>
> Additional information: ERROR [08001] Failed to establish connection with
> the host.
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Connection-not-established-tp11303.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Can I let Ignite to do rebalance at a particular time?

[ght230]

what is the difference between
"CacheConfiguration.setRebalanceMode(CacheRebalanceMode.NONE)"  and
"CacheConfiguration.setRebalanceDelay(-1)"? 

I think both of them need to start rebalance manually by calling
IgniteCache.rebalance().

BTW, At the particular time, Can I know whether it need to do rebalance or
not? Because I just want to do rebalance if necessary.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Can-I-let-Ignite-to-do-rebalance-at-a-particular-time-tp11301p11309.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: REST API authentication

[dkarachentsev]

Hi Ivan,

REST API is based on Jetty server, so you need to configure SSL connector
and certificates. Please refer [1, 2] for details.

[1] https://apacheignite.readme.io/docs/rest-api#general-configuration
[2] https://wiki.eclipse.org/Jetty/Howto/Configure_SSL

-Dmitry.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/REST-API-authentication-tp11299p11308.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Apache Ignite with log4J2 KafkaAppender - class not found

[dkarachentsev]

Hi,

I suppose you need kafka log4j appender [1] in classpath.

[1] https://mvnrepository.com/artifact/org.apache.kafka/kafka-log4j-appender

-Dmitry.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-with-log4J2-KafkaAppender-class-not-found-tp11296p11307.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: cache update from .NET client to Java cluster

[Pavel Tupitsyn]

Please send a reproducer. Probably I still misunderstand the question.

On Mon, Mar 20, 2017 at 10:00 AM, kfeerick <
kevin.feer...@ninemilefinancial.com> wrote:

> That's not the behaviour I am seeing. I can send through a reproduce if
> required.
>
> Thanks,
> kevin
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/cache-update-from-NET-client-to-
> Java-cluster-tp11217p11305.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: cache update from .NET client to Java cluster

[kfeerick]

That's not the behaviour I am seeing. I can send through a reproduce if
required.

Thanks,
kevin



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/cache-update-from-NET-client-to-Java-cluster-tp11217p11305.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.