In which scenario the ignite nodes will shutdown by itself

Hi All, we notice more than one time the ignite node and cache just stop itself quietly . this is weird, no specific ERROR log print. we allocated enough memory for those cache. From the GC log we can not find any obvious abnormal as the main process still running .

RE: Activation: slow and: Ignite node crashed in the middle of checkpoint.

Hi Alex, there were no other relevant logs than what I already listed in the first email. http://www.springframework.org/schema/beans; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=" http://www.springframework.org/schema/beans

Re: Streaming test

What is this class used for? I'm a bit confused - service is usually invoked on the server, so it will obviously need all classes it works with. Am I missing something? Can you show the whole trace? -Val -- View this message in context:

Re: Streaming test

Hello Val, I now put the stream visitor code in a different model and packaged it in a different jar with dependencies. Interestingly, when I ran the program again, the server node has weird error messages. The FileConnector is a class in the client jar. Why would the service needs the

Strange problems with Ignite native Persistence when Data exceeds Memory

Hello, I am running into strange problems with Ignite Native Persistence when the data exceeds the size of the cache (memory). I have 3 nodes with 8 GB each, one cache, using 1 backup. I am using SQL queries, and the cache has 3 indexes. I am loading 9.6M objects, using IgniteDataStreamer in

Re: Failure to deserialize simple model object

Cross-posting to dev Folks, I'm confused by the issue discussed in this thread. Here is the scenario: - Start server node with a cache with POJO store configured. There is one type declared, read-through enabled. - Start client node and execute get() for a key that exists in underlying DB. -

Re: EntryProcessor and Locks

What will happen for the reads when there is a concurrent write by some other process? Will we see OptimisticTransactionException or will be get stale reads (preferred in out use case). thanks! -- View this message in context:

Re: Running Spark SQL on Spark Thrift Server with Ignite

Ravi, You can take a look at these pages: https://apacheignite-fs.readme.io/docs/ignitecontext-igniterdd https://apacheignite-fs.readme.io/docs/testing-integration-with-spark-shell -Val -- View this message in context:

Re: Query about running SQL with durable memory

Dmitry, When you execute a SQL query, there is no deserialization at all. Ignite stores data in binary format that allows to lookup fields without full deserialization. So only required fields are fetched from the objects. https://apacheignite.readme.io/docs/binary-marshaller -Val -- View

Re: Use SLF4J in Ignite

Yes, the ignite-slf4j folder is copied over [image: Inline image 1] On Mon, Aug 14, 2017 at 1:10 PM, ignite_user2016 wrote: > It looks like ignite version of slf4j is not in the classpath. > > Did you copy the ignite slf4j jars into server lib directory ? > > On Mon, Aug

Re: Use SLF4J in Ignite

It looks like ignite version of slf4j is not in the classpath. Did you copy the ignite slf4j jars into server lib directory ? On Mon, Aug 14, 2017 at 1:55 PM, waterg [via Apache Ignite Users] < ml+s70518n1617...@n6.nabble.com> wrote: > Hello there, > > I'm having following error when starting

Re: Query about running SQL with durable memory

If memory cache is empty and all 10 entries are on disk, will Ignite de-serialize all of them? Can de-serialization be avoided if the query has a filter, e.g. SELECT COUNT(*) FROM EMP WHERE SALARY > ? -- View this message in context:

Use SLF4J in Ignite

Hello there, I'm having following error when starting Ignite server node SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail s. In maven

Re: TcpDiscoveryVmIpFinder handle IP change

Hi David, JVM can cache a name service. Could you try to set *networkaddress.cache.ttl* to zero? 1. http://www.myhowto.org/java/42-understanding-host-name-resolution-and-dns-behavior-in-java 2. http://docs.oracle.com/javase/1.5.0/docs/guide/net/properties.html On Mon, Aug 14, 2017 at 10:18 AM,

Re: PeerClassLoading example using cacheLoaders

Hi, You are right, *load* method is called when there is a miss in a cache. putIfAbsent is supported by IgniteCache out of the box. I'm afraid that there is no simple way to achieve what a CacheStore offers. With any other approach, you would have to sacrifice read/write-through behavior. Kind

Re: Activation: slow and: Ignite node crashed in the middle of checkpoint.

Hi, Could you please share the logs and configuration? Actually, the activation time depends on the amount of data, network connectivity and other variables. Kind regards, Alex. On Sat, Aug 12, 2017 at 12:39 AM, Roger Fischer (CW) [via Apache Ignite Users]

Re: EntryProcessor and Locks

HI, Yes, I meant starting a transaction via igniteInstance.transactions().txStart(OPTIMISTIC, isolationLevel) and calling cache.invoke(key, entryProcessor) within its scope. Kind regards, Alex. On Mon, Aug 14, 2017 at 7:59 PM, rajivgandhi [via Apache Ignite Users] <

Re: Ignite starting by itself when using javax.cache.Caching

Hi, thanks for your help. I understand the problem now... exactly what you said it was. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-starting-by-itself-when-using-javax-cache-Caching-tp15997p16174.html Sent from the Apache Ignite Users mailing list

Unsubscribe

Re: EntryProcessor and Locks

By the way, I requested subscribe several times. The one thing with subscription is that it floods my email box with messages from other threads as well. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/EntryProcessor-and-Locks-tp16150p16172.html Sent from the

Re: EntryProcessor and Locks

Thanks. How do you use optimistic tx with Entry processor? The ConcurrencyMode and isolationMode can only be set when you start a tx. Are you saying we should call the entry processor within a tx with concurencymode Optimistic? thanks ! -- View this message in context:

Re: Apache Ignite 2.0.0 Events Issue

Hi, There is 2 issues in your code: 1) You only put 1 value in cache and you cannot be sure whether your node is primary for this particular key or not. As you use "LocalListen" you will only receive notifications for those events which are local for your node. Try putting 100 key-value pairs -

Re: EntryProcessor and Locks

Hi, Looks like you are not subscribed to the mailing list. Please make sure you are subscribed . Answering to your questions, with the PESSIMISTIC or implicit transactions EntryProcessor will cause a

Re: Centralized configuration management

Thanks Alex! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Centralized-configuration-management-tp16159p16168.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Centralized configuration management

Hi, Yes, GetOrCreateCache should do the thing in this case. Kind regards, Alex. On Mon, Aug 14, 2017 at 3:53 PM, franck102 [via Apache Ignite Users] < ml+s70518n16165...@n6.nabble.com> wrote: > Hi Alex, > > Regarding this statement: > "When you destroy or create a cache from a client node,

Re: Client requires DataSource bean configuration copy

In case someone else hits this, the issue is easily resolved by embedding cachestore and datasource facotyr beans in the cache bean, instead of using spring references: Franck -- View this message in context:

Re: Centralized configuration management

Hi Alex, Regarding this statement: "When you destroy or create a cache from a client node, there generally no need to have/propagate the configuration manually to remote nodes. *On join/restart*, a node will find out the caches configured in the cluster and all the required routines will take

Re: Calling service methods from servlets

Hi, The first approach is preferable because the second one implies an additional network round trip. Kind regards, Alex. On Mon, Aug 14, 2017 at 2:44 PM, luqmanahmad [via Apache Ignite Users] < ml+s70518n16160...@n6.nabble.com> wrote: > Hi there, > > Let say we have a node singleton service

Re: Centralized configuration management

Hi, There is no option to update the configuration of an existing cache. As well, you cannot create two caches with the same name but different configurations. So, as you've correctly suggested, to achieve this, you need first to destroy a cache and then start a new one with the updated

Re: Apache Ignite JDBC Support for SAP BOXI or Other BI tools

Hi Ravi, > 1) Do SAP BO or any other BI tool support Ignite as SQL Engine?. Yes, Apache Ignite provides integration with Tableau [1] and Pentaho [2]. As Jörn Franke mentioned above, you can use ODBC [3] or JDBC driver [4] in order to processing data using standard SQL statements. [1]

Re: Centralized configuration management

I need to be a bit more specific I guess. I need the ability to create new caches, or to update the configuration of existing caches. When updating the configuration of a cache other caches should not be affected - so a node restart is not a great option. Would this plan work: - The controller

Calling service methods from servlets

Hi there, Let say we have a node singleton service with a method called doSomething() Now if we want to call the service from a servlet we can either inject the service in the servlet directly like: MyService service = ignite.services().serviceProxy("myService", "MyService.class", false);

Centralized configuration management

Hi all, I am trying to design a controller that will be responsible for managing the cache configuration of all nodes in a cluster. Having read this in the docs: "All caches defined in Ignite Spring XML configuration on any cluster member will also be automatically created and deployed on all

Re: Failure to deserialize simple model object

My bad, here is the whole project. Franck ignite-binary-sample.zip -- View this message in context:

Re: Async messaging

Hello, I bumped into the same error. Was not clear to me that you shouldn't call the future after doing the send: IgniteMessaging message = ignite.message().withAsync(); message.send("destination", "hello world"); IgniteFuture future = message.future(); log.info("Keeps on throwing exception")

TcpDiscoveryVmIpFinder handle IP change

Hi all, Currently I am connecting to an ignite server node with TcpDiscoveryVmIpFinder, from a client node, using a domain as hostname, eg. ignite.dev, normally when there is any network issue or server issue, the client node will reconnect automatically when the network restore or ignite server