how ignite distribute sql query to all nodes when use REPLICATED mode

Suppose right now the cluster has 3 nodes, and all cases are in REPLICATED mode, that means every node has full set of the data. then in this case how ignite distribute the sql query to all nodes to speed up the query? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Does ignite provide a Comparator for Sort?

I am new to Apache ignite.  I have used HAzelcast extensively and one of the features I really liked about it is the Comparator that it provides on the Cache Entries. Does Apache Ignite have one readily available? If not, is it in the works?

Re: Comparison between java 8 streams functionality and Apache Ignite

I've been thinking about this some more: I think the ignite solution is nearly perfect, *if* the reduce operation runs within every node (so that, for example, the results of ~96 threads on one google compute enginer were reduced/summarized to a single value) and then either a single final

Re: Unable to load more than 5g data through sqlline

a better option would be to drop sqlline and write your own client that reads the csv files and loads into the database. This way you can have multiple threads loading multiple files concurrently and each load you setup the parameters for the streamer including batch sizes and flush frequency.

Re: how to handle dataregion out of memmory gracefully

Thanks for this but what concerns me is if i setup several data regions and one of them happens to be a play area i guess for data scientists and they hit the memory limit of that region then the whole server goes down. in the case for a cluster all the nodes hosting that region will go down. I

Re: Comparison between java 8 streams functionality and Apache Ignite

Ahh, I see. But still, even with "map reduce" stratedgy, I *think* that there is only a SINGLE node which will do the reduction, right? As in, the reduction will NOT occur in parallel across nodes, right? (In fact, it sounds like the reduction won't even occur in parallel *within* a node, right?)

IGNITE_EXCHANGE_HISTORY_SIZE value for Ignite client

Hello, We are using Ignite 2.6.0 and we notice on our java app configured as Ignite client that the memory is increasing too much (approx 5GB). We succeeded to fix this by setting the value ofIGNITE_EXCHANGE_HISTORY_SIZE to a lower size than 1000. My question is which will be the impact if we

destroy cache holding residual metadata in memory (2.7)

i am testing code and part of my tests is adding\removing tables. In one of the tests i add a table then destroy it and add it again but with an additional column. When i try load the table i am getting a data type mismatch and it is referring to the previous version of the table in the work

Re: Unable to load more than 5g data through sqlline

Hi Debashis, Is sqlline started on the same machine? Perhaps sqlline ate all the available memory but the system decided to kill Ignite. Could you split incoming data into relatively small chunks and try it out? вт, 30 окт. 2018 г. в 23:07, debashissinha : > < >

Re: how to handle dataregion out of memmory gracefully

Hi Wayne, You can see a message written to a console during Ignite startup with a calculated amount of memory required for a server. It looks as follows: Nodes started on local machine require more than 80% of physical RAM what can lead to significant slowdown due to swapping (please decrease

spring XML configuration to connect ignite database using org.apache.ignite.IgniteJdbcThinDriver

spring XML configuration to connect ignite database using org.apache.ignite.IgniteJdbcThinDriver -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 1 server - many Clients scenario failing

I think the "10.20.228.11:47100" is not a public IP -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Comparison between java 8 streams functionality and Apache Ignite

Hello! String::length will be run on all nodes, but Integer::intValue will be run locally. If you want it to be smarter than that, you could use MapReduce & ForkJoin: https://apacheignite.readme.io/docs/compute-tasks Regards, -- Ilya Kasnacheev вт, 30 окт. 2018 г. в 22:02, gsaxena888 : >

Re: 1 server - many Clients scenario failing

Hello! Oct 31, 2018 10:05:14 AM org.apache.ignite.logger.java.JavaLogger warning WARNING: Connect timed out (consider increasing 'failureDetectionTimeout' configuration property) [addr=/10.20.228.11:47100, failureDetectionTimeout=1] Are you sure that port 47100 is not filtered in client ->

Re: how to do i hibernate configuration for Apache ignite database

https://apacheignite-mix.readme.io/docs/hibernate-l2-cache Above given link is about hibernat-l2-cahe. My hibernate configuration is using ignite database as given below

1 server - many Clients scenario failing

Hey everyone I'm trying to implement such scenario below : One Node running on a VPS , Server Mode , Persistance Enabled Several Nodes running on other VPSs , Client Mode I will be using this for Bucket4j Rate Limiting implementation . We will use bucket4j for limiting the workload of some

Re: how to do i hibernate configuration for Apache ignite database

Hi! Are there any information missing in the documentation ? https://apacheignite-mix.readme.io/docs/hibernate-l2-cache Mikael Den 2018-10-31 kl. 06:24, skrev Malashree: how to do hibernate configuration using ignite database. -- Sent from: