IgniteAtomicSequence

2020-10-24 Thread narges saleh
Hi All,
What is the consequence of data rebalancing across nodes as far as
IgniteAtomicSequence and the reserve on each node is concerned? For
example, if the last sequence number is 6000 in one node and the record
moves to a node whose last sequence number is 1000? Do the reserves on both
nodes get recalculated?

Are there best practices for generating and using these sequences?

Is IgniteAtomicSequence the right approach if I want to keep track of the
records on each node for a partitioned cache?

thanks.


Re: Execution of local SqlFieldsQuery on client node disallowed

2020-10-24 Thread narges saleh
Hello Ilya
Yes, it happens all the time. It seems ignite forces the "client"
establishing the jdbc connection into a client mode, even if I set
client=false.  The sample code and config are attached. The question is how
do I force JDBC connections from a server node.
thanks.

On Fri, Oct 23, 2020 at 10:31 AM Ilya Kasnacheev 
wrote:

> Hello!
>
> Does this happen every time? If so, do you have a reproducer for the issue?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пт, 23 окт. 2020 г. в 13:06, narges saleh :
>
>> Denis -- Just checked. I do specify my services to be deployed on server
>> nodes only. Why would ignite think that I am running my code on a client
>> node?
>>
>> On Fri, Oct 23, 2020 at 3:50 AM narges saleh 
>> wrote:
>>
>>> Hi Denis
>>> What would make an ignite node a client node? The code is invoked via an
>>> ignite service deployed on each node and I am not setting the client mode
>>> anywhere. The code sets the jdbc connection to local and tries to execute a
>>> sql code on the node in some interval. By the way, I didn't know one could
>>> deploy a service on client nodes. Do I need to explicitly mark a node as a
>>> server node when deploying a service?
>>> thanks
>>>
>>> On Thu, Oct 22, 2020 at 9:42 PM Denis Magda  wrote:
>>>
 The error message says you're attempting to run the query on a client
 node. If that's the case (if the service is deployed on the client node),
 then the local flag has no effect because client nodes don't keep your data
 locally but rather consume it from servers.

 -
 Denis


 On Thu, Oct 22, 2020 at 6:26 PM narges saleh 
 wrote:

> Hi All,
> I am trying to execute a sql query via a JDBC  connection on the
> service node (the query is run via a service), but I am getting *Execution
> of local SqlFieldsQuery on client node disallowed.*
> *The JDBC connection has the option local=true as I want to run the
> query on the data on the local node only.*
> *Any idea why I am getting this error?*
>
> *thanks.*
>



JDBCQuery.java
Description: Binary data




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




  







  






  
  
  
  
  



  
firstName
orgName





  














127.0.0.1:47550..47551










Ignite Client Node Stopped With Out Of Memory

2020-10-24 Thread Ravi Makwana
Hi,

We are using Apache Ignite 2.7.0 binary and servers are using Linux OS &
app servers are using Windows OS.We are using Apache Ignite .Net APIs.

Recently we have noticed that our application is stopping due to a client
node throwing Out Of Memory error which we have seen in ignite
client node log file.

App server has 32 GB RAM & We are specifying JVM Heap = 8 GB & Data Region
Min = 1 GB & Max = 10 GB.

*Exception:*

class org.apache.ignite.IgniteException: Platform
error:System.OutOfMemoryException: Insufficient memory to continue the
execution of the program.
   at System.Runtime.InteropServices.Marshal.ReAllocHGlobal(IntPtr pv,
IntPtr cb)
   at
Apache.Ignite.Core.Impl.Memory.PlatformMemoryUtils.ReallocatePooled(Int64
memPtr, Int32 cap)
   at
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.MemoryReallocate(Int64
memPtr, Int64 cap, Int64 unused, Void* arg)
   at
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.InLongLongLongObjectOutLong(Int32
type, Int64 val1, Int64 val2, Int64 val3, IntPtr arg)
at
org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.loggerLog(PlatformProcessorImpl.java:404)
at
org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:460)
at
org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:512)
at
org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
at
org.apache.ignite.internal.processors.platform.callback.PlatformCallbackUtils.inLongLongLongObjectOutLong(Native
Method)
at
org.apache.ignite.internal.processors.platform.callback.PlatformCallbackGateway.memoryReallocate(PlatformCallbackGateway.java:840)
at
org.apache.ignite.internal.processors.platform.memory.PlatformExternalMemory.reallocate(PlatformExternalMemory.java:48)
at
org.apache.ignite.internal.processors.platform.memory.PlatformOutputStreamImpl.ensureCapacity(PlatformOutputStreamImpl.java:305)
at
org.apache.ignite.internal.processors.platform.memory.PlatformOutputStreamImpl.unsafeEnsure(PlatformOutputStreamImpl.java:222)
at
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteBinaryObject(BinaryWriterExImpl.java:962)
at
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:744)
at
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:223)
at
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:164)
at
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:151)
at
org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectDetached(BinaryWriterExImpl.java:1506)
at
org.apache.ignite.internal.processors.platform.cache.query.PlatformQueryCursor.write(PlatformQueryCursor.java:43)
at
org.apache.ignite.internal.processors.platform.cache.query.PlatformQueryCursor.write(PlatformQueryCursor.java:28)
at
org.apache.ignite.internal.processors.platform.cache.query.PlatformAbstractQueryCursor.processOutStream(PlatformAbstractQueryCursor.java:85)
at
org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.outStream(PlatformTargetProxyImpl.java:93)

Can please suggest what is the root cause for the above issue?

Thanks & Regards,