where to get the document about Ignite architecture or technical advantage?

Hi, everyone I only find some document aboute Ignite function, but I want to know how to implement those functions. Where can I get the architecture document? So, I have some deeper problem to be explained. For example, 1, The sql query of Ignite is implemented with

Re: Execute SQL on Ignite cache of BinaryObjects

Hi, I responded on SO: http://stackoverflow.com/questions/40019506/execute-sql-on-ignite-cache-of-binaryobjects -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Execute-SQL-on-Ignite-cache-of-BinaryObjects-tp8269p8281.html Sent from the Apache Ignite Users

Re: Couchbase as persistent store

Hi, Can you provide a small project that will reproduce the issue? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Couchbase-as-persistent-store-tp7476p8280.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Random SSL unsupported record version

Hi, Looks like there is an issue with SSL support when long keys are used. I'm investigating it right now. How long are the keys you're using? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Random-SSL-unsupported-record-version-tp8236p8278.html Sent from

Re: sample code for customised Partition logic

Hi, What exactly are you trying to achieve? Modifying the affinity function can be a challenging task and is generally needed only for very rare specific use cases. -Val -- View this message in context:

Re: randomEntry() deprecated

Hi, You can also use SQL queries for indexed search: https://apacheignite.readme.io/docs/sql-queries -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/randomEntry-deprecated-tp8274p8276.html Sent from the Apache Ignite Users mailing list archive at

Re: randomEntry() deprecated

Nevermind -- localEntries() is better anyway. But if anyone knows of a better way to iterate over unknown cache entries, please advise. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/randomEntry-deprecated-tp8274p8275.html Sent from the Apache Ignite Users

randomEntry() deprecated

Since this method of IgniteCache interface is deprecated, does anyone know how to get an Entry without knowing any of the keys in the cache? For example, if an external process (maybe via Nifi) is writing directly to a cache, how does a separate application read from the cache without

Re: Killing a node under load stalls the grid with ignite 1.7

Hi Binti, Hi, This is look like a lock GridCacheWriteBehindStore and GridCachePartitionExchangeManager. Could you give work an example of this? If not I try to reproduce it tomorrow -- View this message in context:

RE: Evicted entry appears in Write-behind cache

Hi Vladislav, Please see the below cache configuration. LruEvictionPolicy evictionPolicy = new LruEvictionPolicy<>(getIntProperty(envConfig, CACHE_SIZE, 1)); cacheConfiguration

Re: Network Segmentation configuarion

Hi Yitzhak, You can configure specific timeout in discovery SPI or increase common timeout IgniteConfiguration#setFailureDetectionTimeout. But long timeout lead to stop grid on time the timeout If you want to handle segmentation event: ignite.events().localListen(new IgnitePredicate() {

sample code for customised Partition logic

Dear All, I can not find sample code for how customise partition... and I could almost finish it by myself. however, the most wired thing is it work occasionally !!?? most of time it doesn't work my code is:[ public class UCSRendezvousAffinityFunction extends RendezvousAffinityFunction {

Execute SQL on Ignite cache of BinaryObjects

I am creating a cache of BinaryObject from spark a dataframe and then I want to perform SQL on that ignite cache. Here is my code where bank is the dataframe which contains three fields (id,name and age): / val ic = new IgniteContext(sc, () => new IgniteConfiguration()) val cacheConfig =

Re: Near cache

Hi, Please clarify, are you enable the event (EVT_CACHE_OBJECT_REMOVED) in config? I guess, all node will be get EVT_CACHE_OBJECT_REMOVED in that case. ... On Tue, Oct 11, 2016 at 8:56 PM, javastuff@gmail.com <

Re: Couchbase as persistent store

any clue guys? thanks, -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Couchbase-as-persistent-store-tp7476p8267.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite - FileNotFoundException

I guess 64K-128K must be enough. On 13.10.2016 13:04, Anil wrote: What is the recommended file descriptor limit for ignite data load ? Thanks. On 13 October 2016 at 15:16, Taras Ledkov > wrote: Please check the file descriptors OS

Re: How to get the load status of the Ignite cluster

Hi, You can look at the code[1] and get computation of all metrics. The task use public API, but in particular information about thread pools available through MBeans *org.apache:clsLdr=764c12b6,group=Thread Pools,name=GridExecutionExecutor* [1]:

Re: CacheContinuousQuery did not work after the second servernodejoinned into the topology.

Hi Lin, In your case autoUnsubsribe flag should be set to false. Could you describe how change performance after you enable cache events? Thanks, Nikolay On Mon, Oct 10, 2016 at 6:59 AM, Lin wrote: > Hi Nikolay, > > I have a requirement on CQ to implement some functions like

Re: Ignite - FileNotFoundException

What is the recommended file descriptor limit for ignite data load ? Thanks. On 13 October 2016 at 15:16, Taras Ledkov wrote: > Please check the file descriptors OS limits. > > > On 13.10.2016 12:36, Anil wrote: > >> >> When loading huge data into ignite - i see the

Re: Ignite - FileNotFoundException

Please check the file descriptors OS limits. On 13.10.2016 12:36, Anil wrote: When loading huge data into ignite - i see the following exception.. my configuration include off heap as 0 and swap storage to true. org.apache.ignite.logger.java.JavaLogger error SEVERE: Failed to process

Network Segmentation configuarion

While I didn't configure any network segmentation properties (SegmentationResolvers, SegmentationResolveAttempts, SegmentCheckFrequency etc.) node is been shutdown from time to time: WARN : [discovery.tcp.TcpDiscoverySpi] Date=2016/10/13/07/42/52/009|Node is out of topology (probably, due to