Exception being thrown when setting Active to true in Ignite 2.1 with Persitence enabled

[Raymond Wilson]

I’m testing out a first piece of code to use the Ignite persistence layer
in the C# client.



I have added a persistence layer aspect to the configuration for the grid,
like this:



cfg.PersistentStoreConfiguration = new
PersistentStoreConfiguration()

{

PersistentStorePath =
PersistentCacheStoreLocation

};



I then declare, instantiate and activate the grid:



IIgnite Grid = Ignition.Start(cfg);

Grid.SetActive(true);



However, the SetActive line throws this exception:



ERROR 2017-08-02 13:54:04,994 54667ms CacheComputeServer
GridCacheNode - Exception: Apache.Ignite.Core.Common.IgniteException:
Failed to deserialize object with given class loader:
sun.misc.Launcher$AppClassLoader@c387f44 --->
Apache.Ignite.Core.Common.JavaException: class
org.apache.ignite.IgniteException: Failed to deserialize object with given
class loader: sun.misc.Launcher$AppClassLoader@c387f44

at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)

at
org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3427)

at
org.apache.ignite.internal.processors.platform.cluster.PlatformClusterGroup.processInLongOutLong(PlatformClusterGroup.java:401)

at
org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inLongOutLong(PlatformTargetProxyImpl.java:53)

Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
deserialize object with given class loader:
sun.misc.Launcher$AppClassLoader@c387f44

at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:129)

at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:94)

at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:541)

at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheConfigurations(FilePageStoreManager.java:501)

at
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.changeGlobalState(GridClusterStateProcessor.java:453)

at
org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3424)

... 2 more

Caused by: java.lang.IllegalArgumentException: Ignite instance 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:1328)

at
org.apache.ignite.internal.binary.GridBinaryMarshaller.threadLocalContext(GridBinaryMarshaller.java:392)

at
org.apache.ignite.internal.binary.BinaryObjectImpl.readExternal(BinaryObjectImpl.java:694)

at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1849)

at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1806)

at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1353)

at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2018)

at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1942)

at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1808)

at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1353)

at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2018)

at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1942)

at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1808)

at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1353)

at
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2018)

at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1942)

at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1808)

at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1353)

at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:373)

at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:121)

... 7 more



   --- End of inner exception stack trace ---

   at Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.Error(Void*
target, Int32 errType, SByte* errClsChars, Int32 errClsCharsLen, SByte*
errMsgChars, Int32 errMsgCharsLen, SByte* stackTraceChars, Int32
stackTraceCharsLen, Void* errData, Int32 errDataLen)

   at
Apache.Ignite.Core.Impl.Unmanaged.IgniteJniNativeMethods.TargetInLongOutLong(Void*
ctx, Void* target, Int32 opType, Int64 val)

   at
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedUtils.TargetInLongOutLong(IUnmanagedTarget

RE: Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

[Raymond Wilson]

Hi Mikhail,



Thanks for the clarifications.



Yes, I knew setting active was only required when using the persistence
layer, which is the topic of the question J



I was interested if there were best practices or approaches for determining
when the grid had fully initialized. I realise this is somewhat application
specific, but was looking for an established pattern before I invented one
myself.



In my case I have an affinity function that responds to topology changes
which intrinsically would know when it had a ‘quorum’. Is this a typical
place for setting active to true.



Thanks,

Raymond.



*From:* Mikhail Cherkasov [mailto:mcherka...@gridgain.com]
*Sent:* Tuesday, August 1, 2017 11:59 PM
*To:* user@ignite.apache.org
*Subject:* Re: Best practise for setting Ignite.Active to true when using
persistence layer in Ignite 2.1



Hi Raymond,



Ignite cluster is inactive on startup only if persistence is enabled. This
is done to avoid unnecessary partition exchanges between nodes,

for example, if you have 3 nodes and 1 backup enabled and you start only 2
of 3 nodes, then they will treat the third node as dead and start process

of restoring data from backup and rebalance data to spread them among 2
nodes, when you add the missed third node back the process will be repeated.



So we start cluster as in active. When all nodes are started and ready, so
no cluster topology changes aren't expected, you should activate cluster.



Also when you turn off cluster, some nodes can still accept request for
data update and other nodes won't see it, so understand which node has the
latest

data we need to start all nodes first and only then activate cluster.



Thanks,

Mikhail.



On Tue, Aug 1, 2017 at 5:05 AM, Raymond Wilson 
wrote:

Hi,



I am experimenting with a POC looking into using the Ignite persistence
layer.



One aspect of this is setting the grid to be ‘Active’ after all cache grid
nodes have instantiated.



In practical terms, what is the best practice for ensuring the cluster is
running and in a good state to be set to active? What is the downside of
setting active to true before all grid nodes are running?



Thanks,

Raymond.







-- 

Thanks,

Mikhail.

RE: Accessing array elements within items cached in Ignite without deserialising the entire item

[Raymond Wilson]

Hi Pavel,



Thanks for the clarifications. I certainly appreciate that cross platform
protocols constrain what can be done…



Thanks for pointing out IBinaryRawReader.



Regarding random access into arrays, is this something that is on the books
for a future version?

Thanks,

Raymond.



*From:* Pavel Tupitsyn [mailto:ptupit...@apache.org]
*Sent:* Tuesday, August 1, 2017 11:31 PM
*To:* user@ignite.apache.org
*Subject:* Re: Accessing array elements within items cached in Ignite
without deserialising the entire item



Hi Raymond,



First of all, BinaryObject is a cross-platform concept, it exists in C#,
C++, Java.

>From C# point of view there are some inconsistencies (like nullable Guid,
or non-generic collections),

but these things are dictated by the existing protocol, so we can't change
them.

In most cases you can just use WriteObject<>/ReadObject<> methods to avoid
these inconsistencies.



1. You can implement array pooling yourself using IBinaryRawReader methods.

   For example, byte array is written like rawWriter.WriteByte(arr.Length);
for (...) rawWriter.WriteByte(arr[i]);

   I think an extension method would be easy to write.



2. See above, use WriteObject<>/ReadObject<> to avoid dealing with nullables



3. Random array access is not possible with current API.



Thanks,

Pavel



On Tue, Aug 1, 2017 at 2:46 AM, Raymond Wilson 
wrote:

Hi,



I’ve been looking at IBinarizable and IBinarySerializer with regards to
controlling object serialization (using the Ignite.Net client).



A couple of questions:



1.   Some of the APIs in IBinarizable allow for a factory methods to
control construction of collection and dictionary elements, but not for
array elements (which could allow for performance optimization through
array pooling).

2.   GUID and DateTime elements are nullable (and there is no
non-nullable variant for these types). Apart from being inconsistent with
all the other types supported in the API, nullability in .Net carries a
performance penalty. Curious as to why these types are defined like this?

3.   I see it is possible to read arrays of elements. But I see no way
to read a particular element within an array without deserialising the
entire array. Is it possible to do something like  byte ReadByte(string
fieldname, uint index); ?



Thanks,

Raymond.

Re: Amazon AMI not available in a specific region

[raksja]

Thanks for quick turn around that helped.
Also do you know/any one how to install ignite in EMR worker nodes?
Looks like there's no straight forward way.

Any help or suggestions?

On Tue, Aug 1, 2017, 5:33 AM Nikolai Tikhonov [via Apache Ignite Users] <
ml+s70518n15854...@n6.nabble.com> wrote:

> Hi,
>
> I've copied AMI to Oregon. ami-f07f9b88 is image id.
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-ignite-users.70518.x6.nabble.com/Amazon-AMI-not-available-in-a-specific-region-tp15838p15854.html
> To unsubscribe from Amazon AMI not available in a specific region, click
> here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Amazon-AMI-not-available-in-a-specific-region-tp15838p15871.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Can not deserialize ignite cache expired event's oldValue

[ezhuravlev]

Hi,

You've got instance of BinaryObject, not instance of
com.coupang.ignite.fds.model.DiscountCouponOrderItem.

To get instance of this class you need to deserialise BinaryObject value by
invoking oldVal.deserialize()

Evgenii



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Can-not-deserialize-ignite-cache-expired-event-s-oldValue-tp15848p15870.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Off-Heap and Eviction policy questions

[Yasser]

I am developing a datagrid using Ignite 2.1 to store a large size table
(~25G).
I will be using 8 nodes with 12G RAM.
I am currently developing in my local machine and trying to understand the
cache load mechanism, printed metrics and eviction policy.

Based on the below metrics, the heap size keeps increasing. I thought the
default is off-heap and expected the Non heap memory to increase.
I haven't used setOnheapCacheEnabled in code, so that shouldnt be enabled.
*Metrics for local node (to disable set 'metricsLogFrequency' to 0)*
*^-- Node [id=782e9494, name=somegrid, uptime=00:09:30:317]*
*^-- H/N/C [hosts=1, nodes=1, CPUs=4]*
*^-- CPU [cur=1.7%, avg=1.43%, GC=0%]*
*^-- PageMemory [pages=2250]*
*^-- Heap [used=4921MB, free=19.9%, comm=6144MB]*
*^-- Non heap [used=76MB, free=-1%, comm=78MB]*
*^-- Public thread pool [active=0, idle=0, qSize=0]*
*^-- System thread pool [active=0, idle=6, qSize=0]*
*^-- Outbound messages queue [size=0]*

1) Am I missing something about off-heap vs on-heap or is my interpretation
on the printed metrics incorrect?
2) Another question is about Eviction policy during initial data load -
Since I am running in my local machine(to test code before pushing to
multiple servers), I dont have RAM capacity to load all of the data.
I ran the application in local to see if eviction policy would kick-in
during initial data load, but I received java.lang.OutOfMemoryError: Java
heap space error.
Shouldn't eviction process remove data from page when 80% is reached?
Is eviction policy monitor not started at loadCache or is there an issue
with my configuration (given below)?

Code snippet-- The undisclosed section is just trivial part of the settings

CacheConfiguration cacheConfiguration = new
CacheConfiguration<>();
cacheConfiguration.setName(CACHE_NAME)
.setCacheMode(CacheMode.PARTITIONED)
.setMemoryPolicyName(DEFAULT_MEMORY_POLICY)

.setCacheStoreFactory(FactoryBuilder.factoryOf(dataLoader));

MemoryPolicyConfiguration memoryPolicyConfiguration = new
MemoryPolicyConfiguration()
.setName(DEFAULT_MEMORY_POLICY)
.setInitialSize(STARTUP_OFFHEAP_MEMORY_SIZE) //3G
.setPageEvictionMode(DataPageEvictionMode.RANDOM_2_LRU);

MemoryConfiguration memCfg = new MemoryConfiguration()
.setDefaultMemoryPolicyName(DEFAULT_MEMORY_POLICY)
.setMemoryPolicies(memoryPolicyConfiguration);
public class DataLoader extends CacheStoreAdapter
implements Serializable {

@Autowired
private transient JdbcTemplate jdbcTemplate;

@Value("${load.all.query}") //select key, vaue from table
private String loadAllQuery;

@Value("${store.one.query}")
private String storeOneQuery;

 .

@Override
public void loadCache(IgniteBiInClosure closure,
Object... args) {
log.info("In loadcache");
jdbcTemplate.query(loadAllQuery, (rs, rownNum) -> {
closure.apply(rs.getString(1), rs.getString(2));
return null;
});
}
}

Thanks,
Yasser

Re: Cache Groups and PARTITIONED/REPLICATED

[slava.koptilin]

Hi Juan,

> the returned set is always null. As soon as an empty configuration is
> passed, the set seems to work again. Is this the intended behavior?
Yes, this is the intended behavior. Ignite#set() method returns a named set
from cache and create one if it has not been created yet and
CollectionConfiguration is not null [1].

>Should from 2.1.0 onwards caches/sets with different requirements be stored
in different cache groups?
Yes, distributed Sets/Queues within the same group must have the same cache
mode, affinity function and so on.

Thanks!



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Cache-Groups-and-PARTITIONED-REPLICATED-tp15853p15867.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Is Apache Ignite can host in Winform(.Net)?

[ptupitsyn]

Hi Eric,

Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
the reply.

You code works fine, can you re-check it?
I've copied it directly into an empty console application and it runs
without errors.

I have also seen your question on StackOverflow
(https://stackoverflow.com/questions/45411142/can-apache-ignite-net-be-used-in-winforms),
and in the screenshot that you attached
(https://i.stack.imgur.com/ZlgNU.png) there "config" variable is not used.
ConfigManager.GetCustomConfig() call is used instead. This is suspicious,
make sure you use correct configuration.

Thanks,
Pavel




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Is-Apache-Ignite-can-host-in-Winform-Net-tp15846p15866.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: c++ ignite: cache.ContainsKey(key object) method returns false even when key is present

[Igor Sapego]

Hello,

Which version are you on?
Also, please share your configuration. Does the same
behaviour persists if you do it using Java API?

> Also I would like to know if there is any way in c++ to obtain the key
> object  using QueryFieldsCursor

You should use SQL query like "select _key, ... from YourType" and then
just retrieve key as any other column.

Best Regards,
Igor

On Tue, Aug 1, 2017 at 5:55 PM, kotamrajuyashasvi <
kotamrajuyasha...@gmail.com> wrote:

> I am running c++ ignite client, with cassandra as persistent store. The
> cache
> has custom object as key. The key class is mapped in c++ and Java Pojo
> using
> BinaryType object. I also implemented hashcode and equals in java pojo.
> When
> I use cache.Get(key object) in c++ client I am able to retrieve the row .
> The issue is that after I loadCache in c++ and all entries are loaded(
> which
> I could tell from cache size and also when I query I'm able to retrieve all
> rows), If I call cache.ContainsKey(key object), its returning false. But If
> i call cache.Get(key object) and then call  cache.ContainsKey then its
> returning true.
>
> Also after cache.Get(key object) in c++ client, cache size is increasing by
> one even though all entries are fully loaded.But once I call cache.Get
> after
> that how many times I call the cache.Get(key object) again and again even
> with same key fields(key class variables representing the primary key) but
> new key objects.. the size is remaining same its not increasing. So overall
> the problem is that after loadCache in c++, even though a valid key object
> is given its not able to find it in cache and loading again. But after that
> it is able to identify that the key is loaded.
>
> Also I would like to know if there is any way in c++ to obtain the key
> object  using QueryFieldsCursor
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/c-ignite-cache-ContainsKey-key-object-
> method-returns-false-even-when-key-is-present-tp15862.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[afedotov]

Hi Ankit,

Sorry I was busy a bit lately. I'll proceed with the investigation and give
you an update.

Kind regards,
Alex.

On Tue, Aug 1, 2017 at 5:31 PM, Ankit Singhai [via Apache Ignite Users] <
ml+s70518n15860...@n6.nabble.com> wrote:

> Please check folks
>
> On 31-Jul-2017 13:33, "Ankit Singhai [via Apache Ignite Users]" <[hidden
> email] > wrote:
>
>> Hi Alex / Folks,
>> PFA zip containing:-
>> 1. Server log
>> 2. Grid Config
>> 3. Java class to initialise all caches
>> 4. Cache CoException_In_Ignite.zip
>> nfig
>>
>> 5. Few POJOs
>>
>> Please try to replicate at your end and we are stuck at this issue.
>>
>> Regards,
>> Ankit Singhai
>>
>> --
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org
>> -h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMon
>> itorStateException-Attemptet-tp15684p15810.html
>> To start a new topic under Apache Ignite Users, email [hidden email]
>> 
>> To unsubscribe from Apache Ignite Users, click here.
>> NAML
>> 
>>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Caused-by-
> org-h2-jdbc-JdbcSQLException-General-error-java-lang-
> IllegalMonitorStateException-Attemptet-tp15684p15860.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p15864.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Unable to start 2.1 with durable memory

[slava.koptilin]

Hi,

Unfortunately, I cannot reproduce the issue. Could you please provide info
about what command you are using to start Ignite?

Anyway, I see that you are trying to use example-persistent-store.xml which
is refer to org.apache.ignite.examples.model.Organization
Thus, you have to build ignite-examples-{version}.jar and copy it to
{ignite-release}/libs/ directory.

After that you can start Ignite using the following simple script:
#!/bin/bash
export IGNITE_HOME=/projects/binaries/apache-ignite-fabric-2.1.0-bin
cd /projects/binaries/apache-ignite-fabric-2.1.0-bin
./ignite.sh -v
/projects/binaries/apache-ignite-fabric-2.1.0-bin/examples/config/persistentstore/example-persistent-store.xml

Thanks!



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Unable-to-start-2-1-with-durable-memory-tp15841p15863.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

c++ ignite: cache.ContainsKey(key object) method returns false even when key is present

[kotamrajuyashasvi]

I am running c++ ignite client, with cassandra as persistent store. The cache
has custom object as key. The key class is mapped in c++ and Java Pojo using
BinaryType object. I also implemented hashcode and equals in java pojo. When
I use cache.Get(key object) in c++ client I am able to retrieve the row .
The issue is that after I loadCache in c++ and all entries are loaded( which
I could tell from cache size and also when I query I'm able to retrieve all
rows), If I call cache.ContainsKey(key object), its returning false. But If
i call cache.Get(key object) and then call  cache.ContainsKey then its
returning true. 

Also after cache.Get(key object) in c++ client, cache size is increasing by
one even though all entries are fully loaded.But once I call cache.Get after
that how many times I call the cache.Get(key object) again and again even
with same key fields(key class variables representing the primary key) but
new key objects.. the size is remaining same its not increasing. So overall
the problem is that after loadCache in c++, even though a valid key object
is given its not able to find it in cache and loading again. But after that
it is able to identify that the key is loaded.

Also I would like to know if there is any way in c++ to obtain the key
object  using QueryFieldsCursor



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/c-ignite-cache-ContainsKey-key-object-method-returns-false-even-when-key-is-present-tp15862.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: [ANNOUNCE] Apache Ignite 2.1.0 Released

[slava.koptilin]

Hi,

What command did you use in order to build Apache Ignite from the source?
Did you follow the build instructions in the DEVNOTES.txt?

Could you please try the following command?
mvn clean install -Pall-java,all-scala,licenses -DskipTests

Thanks!




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ANNOUNCE-Apache-Ignite-2-1-0-Released-tp15750p15861.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalMonitorStateException: Attempted to release write lock while not holding it

[Ankit Singhai]

Please check folks

On 31-Jul-2017 13:33, "Ankit Singhai [via Apache Ignite Users]" <
ml+s70518n1581...@n6.nabble.com> wrote:

> Hi Alex / Folks,
> PFA zip containing:-
> 1. Server log
> 2. Grid Config
> 3. Java class to initialise all caches
> 4. Cache CoException_In_Ignite.zip
> nfig
>
> 5. Few POJOs
>
> Please try to replicate at your end and we are stuck at this issue.
>
> Regards,
> Ankit Singhai
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Caused-by-
> org-h2-jdbc-JdbcSQLException-General-error-java-lang-
> IllegalMonitorStateException-Attemptet-tp15684p15810.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1...@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-java-lang-IllegalMonitorStateException-Attemptet-tp15684p15860.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: using user defined object as key in ignite c++ client

[kotamrajuyashasvi]

Thanks for the response. I am able to use object as key now



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/using-user-defined-object-as-key-in-ignite-c-client-tp15727p15859.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Remote node ID is not as expected - New Node not coming up

[Gracelin Priya]

Hello,

Can anyone help me to debug?

I had a four node cluster up and running. Brought down all the nodes and tried 
starting it again. One of the node is not coming up and not joining the 
cluster. It is throwing the below error. What is the reason for below error?. 
Verified that IP configuration is fine.


Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
connect to address [addr=/0:0:0:0:0:0:0:1%lo:47100, err=Remote node ID is not 
as expected [expected=fc2bcbe5-2a4b-406b-b60d-69a445f52fd9, 
rcvd=fad95ab3-d45f-484d-bf24-e5ffad660ec8]]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3175)
... 16 more
Caused by: class org.apache.ignite.IgniteCheckedException: Remote node ID 
is not as expected [expected=fc2bcbe5-2a4b-406b-b60d-69a445f52fd9, 
rcvd=fad95ab3-d45f-484d-bf24-e5ffad660ec8]
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeHandshake(TcpCommunicationSpi.java:3304)
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3046)
... 16 more

Regards,
Priya

How to manage sequence with legacy database having auto increment id

[Taud Anas]

Hi,
I need to cache a legacy database having with auto increment key and already 
containing records. 
When I try to insert a new record I have this error: 
Caused by: class org.apache.ignite.IgniteCheckedException: Key is missing from 
query
    at 
org.apache.ignite.internal.processors.query.h2.dml.UpdatePlanBuilder.createSupplier(UpdatePlanBuilder.java:330)
    at 
org.apache.ignite.internal.processors.query.h2.dml.UpdatePlanBuilder.planForInsert(UpdatePlanBuilder.java:195)
    at 
org.apache.ignite.internal.processors.query.h2.dml.UpdatePlanBuilder.planForStatement(UpdatePlanBuilder.java:81)
    at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.getPlanForStatement(DmlStatementsProcessor.java:412)
    at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFields(DmlStatementsProcessor.java:140)
    at 
org.apache.ignite.internal.processors.query.h2.DmlStatementsProcessor.updateSqlFieldsTwoStep(DmlStatementsProcessor.java:198)
    at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryTwoStep(IgniteH2Indexing.java:1659)


My legacy table CUSTOMER:
    id                                 BIGINT            NOT NULL 
AUTO_INCREMENT    
    ,login                             VARCHAR(50)        NOT NULL
    ,email                            VARCHAR(100)    NOT NULL
    ,firstname                        VARCHAR(100)     
    ,lastname                        VARCHAR(100)
    ,phone                            VARCHAR(50)
    ,age                            INTEGER
    ,creation_date             TIMESTAMP        NOT NULL 
    ,update_date             TIMESTAMP        NOT NULL 
    ,PRIMARY KEY (id)
My ignite client:
public static void main(String[] args) {
    Ignition.setClientMode(true);

    try (Ignite ignite = Ignition.start("myconf.xml")) {

    try (IgniteCache cache = 
ignite.getOrCreateCache("customerCache")) {

    // Load cache with data from the database.
        System.out.println(" Load cache customerCache ...");
    cache.loadCache(null);
       
       // Ecriture de nouveaux Customer
       Customer customer=new Customer();
       for (int index=0;index<10;index++)  {
               customer.setLogin("login"+index);
               customer.setEmail("login"+index+"@test.com");
               customer.setAge(22);
               System.out.println(" write "+customer);
               cache.query(new SqlFieldsQuery("INSERT INTO CUSTOMER 
(login,email,age) VALUES (?,?,?)")
                    .setArgs(
                        customer.getLogin()
                        ,customer.getEmail() 
                        ,customer.getAge()
                    )
                );
       }
    }
    catch (Throwable exception) {
        exception.printStackTrace();
    }
    }
    }

My ignit conf (myconf.xml):  
        
        
        
        
        
        
        
        
    
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
                    
                    
                    
                    
                    
                    
                    
                    
                    
        
        
        
        
        
        
        
How o manage sequence with legacy database having auto increment id ?

RE: Cache Groups and PARTITIONED/REPLICATED

[Juan Barani]

I realized that if a have an global AtomicConfiguration like the following:

final AtomicConfiguration atomicConfiguration = new AtomicConfiguration();
atomicConfiguration.setCacheMode(CacheMode.REPLICATED);
igniteCfg.setAtomicConfiguration(atomicConfiguration);

and I create a set with the default configuration, automatically the default 
config is partitioned, and the error appears.

Then, it seems to be either I need to configure the CollectionConfiguration 
exactly the same as the AtomicConfiguration, or place the Collection in a 
different group altogether...

Thanks,

Juan

From: Juan Barani
Sent: Tuesday, August 1, 2017 2:22 PM
To: user@ignite.apache.org
Subject: Cache Groups and PARTITIONED/REPLICATED

Hi!

While trying the execute the very first snippet that creates a set in the 
documentation:

https://apacheignite.readme.io/docs/queue-and-set#overview


Ignite ignite = Ignition.ignite();



IgniteSet set = ignite.set(

"setName", // Set name.

null   // Collection configuration.

);

the returned set is always null. As soon as an empty configuration is passed, 
the set seems to work again. Is this the intended behavior? I guess either the 
code or the documentation is outdated, can it be?

Also, since updating from 2.0.0 to 2.1.0 we are getting the following error 
message, apparently when sets are configured to be replicated and internal 
caches (for atomics) are configured otherwise:

class org.apache.ignite.IgniteException: Cache mode mismatch for caches related 
to the same group [groupName=default-ds-group, 
existingCache=ignite-sys-atomic-cache@default-ds-group, 
existingCacheMode=PARTITIONED, 
startingCache=datastructures_ATOMIC_REPLICATED_0@default-ds-group, 
startingCacheMode=REPLICATED]

Should from 2.1.0 onwards caches/sets with different requirements be stored in 
different cache groups?

Thanks!

Juan

Re: Is Apache Ignite can visit through TCP, like Redis?

[slava.koptilin]

Hi Eric,

Please properly subscribe to the mailing list so that the community can 
receive email notifications for your messages. To subscribe, send empty 
email to user-subscr...@ignite.apache.org and follow simple instructions in 
the reply. 

Apache Ignite provides a rich set of APIs that can be used via a variety of
protocols like Redis, REST etc.
Ignite is partially Redis compliant, so you can connect to Ignite using your
favorite Redis client [1].

The recommended Redis clients can be found at official page [2]

[1] https://apacheignite.readme.io/docs/redis
[2] https://redis.io/clients#c

Thanks!



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Is-Apache-Ignite-can-visit-through-TCP-like-Redis-tp15847p15855.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Amazon AMI not available in a specific region

[Nikolai Tikhonov]

Hi,

I've copied AMI to Oregon. ami-f07f9b88 is image id.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Amazon-AMI-not-available-in-a-specific-region-tp15838p15854.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Cache Groups and PARTITIONED/REPLICATED

[Juan Barani]

Hi!

While trying the execute the very first snippet that creates a set in the 
documentation:

https://apacheignite.readme.io/docs/queue-and-set#overview


Ignite ignite = Ignition.ignite();



IgniteSet set = ignite.set(

"setName", // Set name.

null   // Collection configuration.

);

the returned set is always null. As soon as an empty configuration is passed, 
the set seems to work again. Is this the intended behavior? I guess either the 
code or the documentation is outdated, can it be?

Also, since updating from 2.0.0 to 2.1.0 we are getting the following error 
message, apparently when sets are configured to be replicated and internal 
caches (for atomics) are configured otherwise:

class org.apache.ignite.IgniteException: Cache mode mismatch for caches related 
to the same group [groupName=default-ds-group, 
existingCache=ignite-sys-atomic-cache@default-ds-group, 
existingCacheMode=PARTITIONED, 
startingCache=datastructures_ATOMIC_REPLICATED_0@default-ds-group, 
startingCacheMode=REPLICATED]

Should from 2.1.0 onwards caches/sets with different requirements be stored in 
different cache groups?

Thanks!

Juan

Re: Best practise for setting Ignite.Active to true when using persistence layer in Ignite 2.1

[Mikhail Cherkasov]

Hi Raymond,

Ignite cluster is inactive on startup only if persistence is enabled. This
is done to avoid unnecessary partition exchanges between nodes,
for example, if you have 3 nodes and 1 backup enabled and you start only 2
of 3 nodes, then they will treat the third node as dead and start process
of restoring data from backup and rebalance data to spread them among 2
nodes, when you add the missed third node back the process will be repeated.

So we start cluster as in active. When all nodes are started and ready, so
no cluster topology changes aren't expected, you should activate cluster.

Also when you turn off cluster, some nodes can still accept request for
data update and other nodes won't see it, so understand which node has the
latest
data we need to start all nodes first and only then activate cluster.

Thanks,
Mikhail.

On Tue, Aug 1, 2017 at 5:05 AM, Raymond Wilson 
wrote:

> Hi,
>
>
>
> I am experimenting with a POC looking into using the Ignite persistence
> layer.
>
>
>
> One aspect of this is setting the grid to be ‘Active’ after all cache grid
> nodes have instantiated.
>
>
>
> In practical terms, what is the best practice for ensuring the cluster is
> running and in a good state to be set to active? What is the downside of
> setting active to true before all grid nodes are running?
>
>
>
> Thanks,
>
> Raymond.
>
>
>



-- 
Thanks,
Mikhail.

Re: IGFS WEB UI ?

[slava.koptilin]

Hi Pradeep,

Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
the reply.

Ignite provides only native IGFS API
https://apacheignite-fs.readme.io/docs/igfs which can be used in order to
browse a content.

If you are using Ignite IGFS as Hadoop FileSystem, then you can use Hadoop
Web UI I think.

Thanks.




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/IGFS-WEB-UI-tp15834p15851.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Accessing array elements within items cached in Ignite without deserialising the entire item

[Pavel Tupitsyn]

Hi Raymond,

First of all, BinaryObject is a cross-platform concept, it exists in C#,
C++, Java.
>From C# point of view there are some inconsistencies (like nullable Guid,
or non-generic collections),
but these things are dictated by the existing protocol, so we can't change
them.
In most cases you can just use WriteObject<>/ReadObject<> methods to avoid
these inconsistencies.

1. You can implement array pooling yourself using IBinaryRawReader methods.
   For example, byte array is written like rawWriter.WriteByte(arr.Length);
for (...) rawWriter.WriteByte(arr[i]);
   I think an extension method would be easy to write.

2. See above, use WriteObject<>/ReadObject<> to avoid dealing with nullables

3. Random array access is not possible with current API.

Thanks,
Pavel

On Tue, Aug 1, 2017 at 2:46 AM, Raymond Wilson 
wrote:

> Hi,
>
>
>
> I’ve been looking at IBinarizable and IBinarySerializer with regards to
> controlling object serialization (using the Ignite.Net client).
>
>
>
> A couple of questions:
>
>
>
> 1.   Some of the APIs in IBinarizable allow for a factory methods to
> control construction of collection and dictionary elements, but not for
> array elements (which could allow for performance optimization through
> array pooling).
>
> 2.   GUID and DateTime elements are nullable (and there is no
> non-nullable variant for these types). Apart from being inconsistent with
> all the other types supported in the API, nullability in .Net carries a
> performance penalty. Curious as to why these types are defined like this?
>
> 3.   I see it is possible to read arrays of elements. But I see no
> way to read a particular element within an array without deserialising the
> entire array. Is it possible to do something like  byte ReadByte(string
> fieldname, uint index); ?
>
>
>
> Thanks,
>
> Raymond.
>
>
>

Re: Ignie 2.1: Heap memory used issue

[slava.koptilin]

Hi Bob,

I don't see any strange results.
Starting Ignite 2.0 data is always in off-heap, but Java heap is used for
operational needs of your application
and internals of Ignite itself (not as a data storage).

I think that 'Heap memory initialized', 'Heap memory committed' and 'Heap
memory maximum' correspond to your Xms, Xms options.

additional info about JVM tuning for off-heap cache can be found here
https://apacheignite.readme.io/docs/jvm-and-system-tuning#jvm-tuning-for-clusters-with-off_heap-caches

Thanks!



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignie-2-1-Heap-memory-used-issue-tp15844p15849.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Unable to start 2.1 with durable memory

[devkumar]

I have both libraries inside lib folder of ignite.
The problem occurs only when i put below configuration in my ignite
configuration.


  


I am able to start the ignite server by removing above property.





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Unable-to-start-2-1-with-durable-memory-tp15841p15845.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Ignie 2.1: Heap memory used issue

[Bob Li]

I turned onheap off in my cache definition file like:












but I checked Heap memory used by ignitevisorcmd.sh:
| Heap memory initialized | 1gb 
 
|
| Heap memory used| 296mb   
 
|
| Heap memory committed   | 990mb   
 
|
| Heap memory maximum | 990mb   
 
|
| Non-heap memory initialized | 2mb 
 
|
| Non-heap memory used| 57mb
 
|
| Non-heap memory committed   | 59mb
 
|
| Non-heap memory maximum | 1gb  

why didn't it take effect ?

 




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignie-2-1-Heap-memory-used-issue-tp15844.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Scheduler throwing NullPointerException for Ignite 2.0.0

[Dmitriy Govorukhin]

Hi ronly2008,

I applied your stacktrace on ignite-2.0.0, but code lines is does not
matched. Are you sure that you use ignite-2.0.0 (it is tag)? Can you provide
small reproducer? It can help solve problem more quickly.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Scheduler-throwing-NullPointerException-for-Ignite-2-0-0-tp13420p15843.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Unable to start 2.1 with durable memory

[Вячеслав Коптилин]

Hi,

The log you provided contatins the following exception:
 - java.lang.ClassNotFoundException:
org.apache.ignite.configuration.PersistentStoreConfiguration

It seems that Ignite libs are not not present in the CLASSPATH.
Please, be sure that '{ignite-release}/libs/',
'{ignite-release}/libs/ignite-spring' and
'{ignite-release}/libs/ignite-indexing' directories are present in your
CLASSPATH.

Thanks.

2017-08-01 9:47 GMT+03:00 devkumar :

> Hi,
> I am unable to start server with durable memory enable. I am getting the
> following error :-
>
> class org.apache.ignite.IgniteException: Failed to instantiate Spring XML
> application context (make sure all classes used in Spring configuration are
> present at CLASSPATH)
> [springUrl=file:/Users/dkumar9/Desktop/IgniteCluster/
> apache-ignite-fabric-2.1.0-bin/bin/../examples/config/
> persistentstore/example-persistent-store.xml]
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.
> java:949)
> at org.apache.ignite.Ignition.start(Ignition.java:350)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.
> main(CommandLineStartup.java:302)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> instantiate Spring XML application context (make sure all classes used in
> Spring configuration are present at CLASSPATH)
> [springUrl=file:/Users/dkumar9/Desktop/IgniteCluster/
> apache-ignite-fabric-2.1.0-bin/bin/../examples/config/
> persistentstore/example-persistent-store.xml]
> at
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.
> applicationContext(IgniteSpringHelperImpl.java:387)
> at
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.
> loadConfigurations(IgniteSpringHelperImpl.java:104)
> at
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.
> loadConfigurations(IgniteSpringHelperImpl.java:98)
> at
> org.apache.ignite.internal.IgnitionEx.loadConfigurations(
> IgnitionEx.java:668)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.
> java:869)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.
> java:778)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.
> java:648)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.
> java:617)
> at org.apache.ignite.Ignition.start(Ignition.java:347)
> ... 1 more
> Caused by: org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'ignite.cfg' defined in URL
> [file:/Users/dkumar9/Desktop/IgniteCluster/apache-ignite-
> fabric-2.1.0-bin/bin/../examples/config/persistentstore/example-
> persistent-store.xml]:
> Cannot create inner bean
> 'org.apache.ignite.configuration.PersistentStoreConfiguration#23e028a9' of
> type [org.apache.ignite.configuration.PersistentStoreConfiguration] while
> setting bean property 'persistentStoreConfiguration'; nested exception is
> org.springframework.beans.factory.CannotLoadBeanClassException: Cannot
> find
> class [org.apache.ignite.configuration.PersistentStoreConfiguration] for
> bean with name
> 'org.apache.ignite.configuration.PersistentStoreConfiguration#23e028a9'
> defined in URL
> [file:/Users/dkumar9/Desktop/IgniteCluster/apache-ignite-
> fabric-2.1.0-bin/bin/../examples/config/persistentstore/example-
> persistent-store.xml];
> nested exception is java.lang.ClassNotFoundException:
> org.apache.ignite.configuration.PersistentStoreConfiguration
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.
> resolveInnerBean(BeanDefinitionValueResolver.java:313)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.
> resolveValueIfNecessary(BeanDefinitionValueResolver.java:122)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1531)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.populateBean(AbstractAutowireCapableBeanFactory.java:1276)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFac
> tory.createBean(AbstractAutowireCapableBeanFactory.java:483)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$1.
> getObject(AbstractBeanFactory.java:306)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.
> getSingleton(DefaultSingletonBeanRegistry.java:230)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(
> AbstractBeanFactory.java:302)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(
> AbstractBeanFactory.java:197)
> at
> 

Unable to start 2.1 with durable memory

[devkumar]

Hi,
I am unable to start server with durable memory enable. I am getting the
following error :- 

class org.apache.ignite.IgniteException: Failed to instantiate Spring XML
application context (make sure all classes used in Spring configuration are
present at CLASSPATH)
[springUrl=file:/Users/dkumar9/Desktop/IgniteCluster/apache-ignite-fabric-2.1.0-bin/bin/../examples/config/persistentstore/example-persistent-store.xml]
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:949)
at org.apache.ignite.Ignition.start(Ignition.java:350)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
instantiate Spring XML application context (make sure all classes used in
Spring configuration are present at CLASSPATH)
[springUrl=file:/Users/dkumar9/Desktop/IgniteCluster/apache-ignite-fabric-2.1.0-bin/bin/../examples/config/persistentstore/example-persistent-store.xml]
at
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:387)
at
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:104)
at
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.loadConfigurations(IgniteSpringHelperImpl.java:98)
at
org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:668)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:869)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:778)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:648)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:617)
at org.apache.ignite.Ignition.start(Ignition.java:347)
... 1 more
Caused by: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'ignite.cfg' defined in URL
[file:/Users/dkumar9/Desktop/IgniteCluster/apache-ignite-fabric-2.1.0-bin/bin/../examples/config/persistentstore/example-persistent-store.xml]:
Cannot create inner bean
'org.apache.ignite.configuration.PersistentStoreConfiguration#23e028a9' of
type [org.apache.ignite.configuration.PersistentStoreConfiguration] while
setting bean property 'persistentStoreConfiguration'; nested exception is
org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find
class [org.apache.ignite.configuration.PersistentStoreConfiguration] for
bean with name
'org.apache.ignite.configuration.PersistentStoreConfiguration#23e028a9'
defined in URL
[file:/Users/dkumar9/Desktop/IgniteCluster/apache-ignite-fabric-2.1.0-bin/bin/../examples/config/persistentstore/example-persistent-store.xml];
nested exception is java.lang.ClassNotFoundException:
org.apache.ignite.configuration.PersistentStoreConfiguration
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:313)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:122)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1531)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1276)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761)
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:866)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:542)
at
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:381)
... 9 more
Caused by: org.springframework.beans.factory.CannotLoadBeanClassException:
Cannot find class
[org.apache.ignite.configuration.PersistentStoreConfiguration] for bean with
name 

Re: Setting MemoryConfiguration

[Evgenii Zhuravlev]

With the default configuration, clients don't use offheap memory. If you
will configure MemoryConfiguration and create LOCAL cache - they will use
offHeap memory

Evgenii

2017-07-31 17:55 GMT+03:00 Amit Pundir :

> Thanks but does that mean client nodes do *not* use the offHeap memory?
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Setting-MemoryConfiguration-tp15813p15829.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>