how to use 3 party file system

hi,i want to use 3 party file system like HDFS underneath Ignite. now dose Ignite support 3 party file system？ -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Runtime failure on bounds

Hi Team, We are receiving Runtime failure on bounds even after updating it to 2.6 version. We used to receive Failed to get page IO instance (page content is corrupted) from 2.3, 2.4 and 2.5, now in 2.6 it is changed to Item not found: 1. Till now we are in test environments but we are

Re: Affinity calls in stream receiver

We switched to CONTINUOUS mode based on the assumption that SHARED mode had regressed in a way that allowed it to create many class loaders, and eventually run out of Metaspace. CONTINUOUS mode failed much sooner, and we were able to reproduce that failure and identify bugs in the code. The

Logging in C++

Hi, I'm continuing to work on a distributed closure in C++, and this time I'm wondering how you can do a remote logging. Thanks, F.D.

Re: Thin client doesn't support Expiry Policies.

Thanks for the reply. Really appreciated. Based on our usage, it seems not practical to have different pre-configured expiry policy for each cache on server node. Because that means each time when we create a cache with new expiry policy then we need to update our server node. Do you know if

Re: Apache Ignite Bianry Cache store Sql Read Through Feature

Hi, I think that the best way to handle this scenario is to update the underlying database through Ignite. Other approaches have obvious drawbacks (at least one): there is always a time interval between calling cache.get() and executing SQL query, so it cannot be guaranteed that you will see the

Re: Ignite graceful shutdown

Hi Sam, > is there a chance that stop method call would block long time or > hang depending on what jobs are running? > Would it be safe to wrap a wait timeout & call stop(null, false) again if > taking too long? In the vast majority of use cases, it will not be a problem I think, because

Re: Thin client doesn't support Expiry Policies.

You should call IIgniteClient.GetCache(cacheName) to get specific cache. You can get multiple caches using single client. Best Regards, Igor On Tue, Jul 17, 2018 at 7:51 PM ysc751206 wrote: > Yes, I know we can specify many caches with different expiryPolicyFactory > on > server node, but on

Re: Thin client doesn't support Expiry Policies.

Yes, I know we can specify many caches with different expiryPolicyFactory on server node, but on thin client side, there is no way to specify which cache you want to use. All we have are host and port. Do you mean we need to use different host or port for each cache having different

Re: Running Server Node in UNIX

Hello, please try the following: java -cp /opt/lib/*:/path-to-your-working-directory-where-class-files-are-stored/ com.cache.init.ServerNodeCodeStartup I think that these links will be very helpful for you:

Re: Possible starvation in striped pool

We are using the TreeMap for all the putAll operations. We also tried streamer API to create the automatic batches. Still the issue is same. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Running Server Node in UNIX

Running below command in UNIX and getting error.it runs fine in windows in eclipse..any help on this? 1. java -cp /opt/lib/*.jar:/opt/com/test/cache/*.*:/opt/com/test/config/*.* ServerNodeCodeStartup Error: Could not find or load main class ServerNodeCodeStartup 2. java -cp

Re: Running Server Node in UNIX

is any help on this? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Port Assigned? Work on specific Node?

Hello! I still don't understand /why/ you want to implement the scenario that you have described. Can you please describe which real-life problem you are solving? Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Possible starvation in striped pool

Hello same issue occurred when trying to put object in cache using cache.put method.after changing put to putAsync issue was solved. I have read about when you using putAll methode pass sorted collection to it so it avoid deadlock. So is it true? On Tue, Jul 17, 2018, 8:22 PM ilya.kasnacheev

Re: Spring application context resource is not injected

Hello! Can you please upload the project to github so that we could take a look? Please include relevant Spark configs. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: spark ignite - how to set ignite client jvm memory options?

Hello! Can you please copy the message that gives you worries? Also please share spark's config. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Possible starvation in striped pool

Hello! I have noticed that you are using putAll in your code. Apache Ignite is susceptible to deadlocks in the same fashion as regular multi-threaded code: i.e., if you take multiple locks (as putAll does, on partitions for its keys), you can get deadlock unless you maintain sequence of locks,

Re: Port Assigned? Work on specific Node?

There is no cache configuration in these xml file, but assume that in cluster1 configuration there is cache configuration which mode is REPLICATED and operation is TRANSACTIONAL -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Port Assigned? Work on specific Node?

Hey here is the full scenario, I hope it will be clear: I have 2 clusters Each cluster has own different cache, let's say in cluster 1, there is cache named "cluster1cache". (We can assume that no cache in cluster 2) And I want to copy these cache to cluster2, but when copying occurs, client

Re: Thin client doesn't support Expiry Policies.

You should configure server nodes, not clients for that, if you use C# servers, so see IgniteConfigurationSection.xsd for that. Using it you can specify cache name and expiryPolicyFactory for any cache. Best Regards, Igor On Mon, Jul 16, 2018 at 10:37 PM ysc751206 wrote: > Does that mean we