Ignite Service Grid - how to have control over service execution in cluster?

Hi, Suppose I have three server nodes and using ignite in standalone manner. I have configured a service for loading my data into cache in all nodes, but expects only one of them to actually deploy the service as a cluster singleton. 1. How do I tell my service to execute its execute method only

IO implications of ScanQuery

I have a potential work flow where I may need to find a set of elements in a cache where the values are not be small (1-100Kb say), and where the numbers of elements in the cache may be large (many millions). Each key contains fields the scan query could use to select the entries I want.

RE: Ignite Query Slow

Thank you..Tried @QuerySQLFields...but column name not appeared same as database table(i.e underscore("_") is missing in ignite). Hence I have added index to qryEntity and noticed that Query takes about 7 seconds (i.e select * from customercache.customer) for against ignite cache data of 200,000

Avoiding Docker Bridge network when using S3 discovery

When we use S3 discovery and Ignite containers running under ECS using host networking, the S3 bucket end up with 172.17.0.1#47500 along with the other server addresses. Then on cluster startup we must wait for the network timeout.Is there a way to avoid having this address pushed to the S3

Re: SQL Engine

Thx… moved to dev list. Regards, Igor > On Oct 17, 2018, at 6:10 PM, aealexsandrov wrote: > > Hi Igor, > > I think that optimizationd for Ignite better to discuss it on the Apache > Ignite Developer list: > > http://apache-ignite-developers.2346864.n4.nabble.com/ > > BR, > Andrei > > >

Re: SQL Engine

Hi Igor, I think that optimizationd for Ignite better to discuss it on the Apache Ignite Developer list: http://apache-ignite-developers.2346864.n4.nabble.com/ BR, Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

SQL Engine

Hello, Seems that SQL engine always deserialize whole objects instead of using just SQL enabled fields (annotated with @QuerySqlField). This may have a huge impact on Ignite heap usage and GC overhead as well. For example, we have a cache holding big objects but with only two sql query fields

Re: Query execution too long even after providing index

How much data do you have? What is the amount of heap and offheap memory? Can you share the reproducer with the community? Evgenii -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ./control.sh --baseline doesn't list nodes on a linux machines

>By the way - I wonder what is the right way to reset an Ignite instance to the initial state (the one I have when Ignite is just installed)? You should delete work and db directories. >I could not activate the new cluster. When control.sh --baseline tried to connect to the cluster it hung

Re: On-heap cache

Hello! Cache API calls work with smaller overhead with On-Heap caching enabled, but for SQL there would not likely much difference. Regards, -- Ilya Kasnacheev ср, 17 окт. 2018 г. в 16:54, Prasad Bhalerao : > What is the advantage of using on-heap cache? > > I compared the sql execution time

On-heap cache

What is the advantage of using on-heap cache? I compared the sql execution time of on-heap cache and off-heap cache and found that there is not much difference in execution time. Thanks, Prasad

Re: odbc caches - cannot browse

The issue is fixed and is in master already. You can wait for Ignite 2.7 release or check that the issue is resolved with nightly release [1] [1] - https://ci.ignite.apache.org/project.html?projectId=Releases_NightlyRelease Best Regards, Igor On Tue, Oct 16, 2018 at 10:42 AM wt wrote: >

RE: IGNITE-8386 question (composite pKeys)

Yep, just create a separate index. (I saw in your other messages that you’re already trying that) Stan From: eugene miretsky Sent: 18 сентября 2018 г. 17:56 To: user@ignite.apache.org Subject: Re: IGNITE-8386 question (composite pKeys) So how should we work around it now? Just create a new

Re: Writing binary [] to ignite via memcache binary protocol

Hi Michael, The troubles could be related to Python library. It seems in Python 2.7 there is no such thing as "byte array". And value passed to the client is string in this case. I checked that Ignite recognizes bytes array type and stores in as byte array internally. I did following experiment

Re: Failed to process selector key error

Hello! I have seen this problem under heavy workloads and my recommendation will be to increase socketWriteTimeout: Regards, -- Ilya Kasnacheev ср, 17 окт. 2018 г. в 11:52, the_palakkaran : > > Hi, > > While

Re: Ignite Select Query Performance

Hi, We can try to check can your configuration be improved but first of all could you please provide some details: 1)How many data nodes you used. 2)Data node configuration 3)Cache configuration or DML Create Table command for your cache (table) BR, Andrei -- Sent from:

Re: Failed to process selector key error

Hi, Your client was disconnected from the server. It could be because of different reasons: 1. Network problems on your client. 2. Very long GC pause on the server side. I guess that you face first because you note that possible you had the network problems. In this case, the server will not

Re: Ignite complains for low heap memory

Thanks! It works. On Wed, Oct 17, 2018 at 4:46 PM Stanislav Lukyanov wrote: > Put your -X* options before -jar. That’s how java command line works. > > > > Stan > > > > *From: *Lokesh Sharma > *Sent: *17 октября 2018 г. 14:08 > *To: *user@ignite.apache.org > *Subject: *Re: Ignite complains for

RE: Ignite complains for low heap memory

Put your -X* options before -jar. That’s how java command line works. Stan From: Lokesh Sharma Sent: 17 октября 2018 г. 14:08 To: user@ignite.apache.org Subject: Re: Ignite complains for low heap memory I get the same output in the logs when I run the application with Xms set to 2 GB. I ran

Re: Ignite complains for low heap memory

I get the same output in the logs when I run the application with Xms set to 2 GB. I ran this command: java -jar target/cm.jar -Xms2024m -Xmx4024m On Wed, Oct 17, 2018 at 4:26 PM aealexsandrov wrote: > Hi, > > The heap metrics that you see in topology message shows the max heap value > that

Re: Ignite complains for low heap memory

Hi, The heap metrics that you see in topology message shows the max heap value that your cluster can use: Math.max(m.getHeapMemoryInitialized(), m.getHeapMemoryMaximum() Initial heap size (-Xms ) is different from the maximum (-Xmx). Your JVM will be started with Xms amount of memory and will

Re: What happens if Server node in a client-server gets down?

Hello! 1. In this case client will not be able to reconnect, I am afraid. You should specify several addresses there. 2. No, but the client will not be able to reconnect to a new server node until you restart. It will still be able to communicate with any new servers or clients, provided that it

Re: Ignite complains for low heap memory

*Typo Correction: The later heap size is 2.6 GB not 2 GB. On Wed, Oct 17, 2018 at 3:53 PM Lokesh Sharma wrote: > When Ignite boots up, it initially complains that only "188 MB is > available": > > 2018-10-17 15:44:12.295 WARN 15129 --- [pub-#22%cm%] >>

Ignite complains for low heap memory

When Ignite boots up, it initially complains that only "188 MB is available": 2018-10-17 15:44:12.295 WARN 15129 --- [pub-#22%cm%] > o.apache.ignite.internal.GridDiagnostic : Initial heap size is 188MB > (should be no less than 512MB, use -Xms512m -Xmx512m). > [15:44:12] Initial heap size

Re: Blog post "Introduction to the Apache(R) Ignite™ community structure"

[For discussion] It's interesting to know more about possible conflicts: when a few persons are involved in contribution as a commiters, for example, and they have different opinions about next steps in roadmap implementation or about certain feature. How to measure correctly their weights? One of

Re: Ignite Service Grid - Anomalous behavior

Without it, you can't just understand, which data you should upload to each node. ср, 17 окт. 2018 г. в 12:03, Evgenii Zhuravlev : > Yes, in case if you use not partition-aware CacheStore > > Evgenii > > вт, 16 окт. 2018 г. в 22:36, the_palakkaran : > >> Does it mean all data will be loaded on

Re: Ignite Service Grid - Anomalous behavior

Yes, in case if you use not partition-aware CacheStore Evgenii вт, 16 окт. 2018 г. в 22:36, the_palakkaran : > Does it mean all data will be loaded on all servers and then it will > partition amongst them ? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

Re: Heap size

Sometimes, for blobs and images with size around 100-1000 mbs I'm using G1 with increased heap region size via -XX:G1HeapRegionSize Also, if you have nodes with 8-24 cores, try to use CMS, it gives small second GC pause during "remark" phase when you don't change the graph of objects very often

Failed to process selector key error

Hi, While loading data using streamer, I have the below exception. Why do i get this error? >From another thread, there was a hint that it causes due to network lags. Even if this error occurs, data loading gets complete without any problem.

Re: Writing binary [] to ignite via memcache binary protocol

Hi Michael, Answering one of your questions. > Does ignite internally have a way to store the data type when cache entry is stored? Yes, internally Ignite maintains data types for stored keys and values. Could you confirm that for real memcached your example works as expected? I will try