Re: Ignite transactions

Hi, Andrey tx.start() — thread1 cache1.put|get  — thread1 cache2.put|get  — thread1 tx.commit — thread1 log operation  i didn`t see the problem here    >Thanks Pavel! >  >* According to business logic, I must transactionally change the values in 2 >caches; in the course of my actions, I must log

Re: Another replicated cache oddity

  >Hi,   Hi, this really looks like very strange  First of all you need to check consistency of your data : [1]   > Some time ago an element (E) was added to this cache (among many others) And some time it will be all ok there ? Are you sure that this element was properly touched ?  What king of

Re: Ignite query taking too long time with IN operator

r all fields if yes how that will solve >this problem? >  >Thanks, >Charlin   >On Wed, 31 May 2023 at 13:38, Zhenya Stanilovsky via user < >user@ignite.apache.org > wrote: >>Hi, seems you need to build index over this field. >> >> >> >>  >>

Re: Ignite query taking too long time with IN operator

Charlin   >On Wed, 31 May 2023 at 13:38, Zhenya Stanilovsky via user < >user@ignite.apache.org > wrote: >>Hi, seems you need to build index over this field. >> >> >> >>  >>>Hi All, >>>I am having two nodes cluster grid and  cache model

Re: Ignite query taking too long time with IN operator

Hi, seems you need to build index over this field.   >Hi All, >I am having two nodes cluster grid and  cache model, which has 2126239 records >and Ignite query with IN operator taking too long sometimes 17 - 18 seconds >and another time around 40 seconds. >  >Expected result : 3 to 4

Re: pyignite - performance issue

Hi, plz append ignite and py client versions.   >Hi, >I made a speed comparison of retrieving data from Apache Ignite using several >methods. All records are in one table, I did not use any WHERE condition, only >a SELECT * FROM TABLE XYZ LIMIT 2. >Test results are: >Apache Ignite >* Apache

Re: How to handle missed indexes and affinity keys?

res.total_cnt_orders_with_sku >FROM ProductFeatures >WHERE ProductFeatures.product_sku = 52864 >; > >And the result:  > >SELECT >__Z0.PRODUCT_SKU AS __C0_0, >__Z0.TOTAL_CNT_ORDERS_WITH_SKU AS __C0_1 >FROM PUBLIC.PRODUCTFEATURES __Z0 >/* PUBLIC.PRODUCTFEATURES.__SCAN_ *

Re: How to handle missed indexes and affinity keys?

Hi Roza, when did you observe such a problem after restart ? and your caches with persistence mode ?   >Hi Maksim! >  >The problem is that simple SELECT query runs in ~20min - this index does not >work. >  >More over, other (not corrupted) tables with affinity key == primary key have >index b

Re[4]: What is data-streamer-stripe threasd?

It`s up to you, if it not annoying you leave it as it is and fill otherwise )   >Nah, it's fine just wanted to make sure what it was. Unless you think I should >log at least an issue? >    >On Wed, Sep 14, 2022 at 3:13 AM Zhenya Stanilovsky via user < >user@ignite.ap

Re[2]: What is data-streamer-stripe threasd?

ool size for data >streamer to 1. >  >But it will still look blocked?   >On Mon., Sep. 12, 2022, 8:59 a.m. Zhenya Stanilovsky via user, < >user@ignite.apache.org > wrote: >>John, seems all you can here is just to set this pool size into «1» , «0» —  >>tends to er

Re: What is data-streamer-stripe threasd?

John, seems all you can here is just to set this pool size into «1» , «0» —  tends to error.   https://ignite.apache.org/docs/latest/data-streaming#configuring-data-streamer-thread-pool-size   1 thread will still be frozen in such a case.    >  >>  >>>Hi I'm profiling my application through YourKi

Re[8]: Checkpointing threads

limits on checkpointing.    >On Mon, 12 Sept 2022, 11:32 Zhenya Stanilovsky via user, < >user@ignite.apache.org > wrote: >> >> >> >>  >>>We have observed one interesting issue with checkpointing. We are using 64G >>>RAM 12 CPU with 3K iops/128mbps SSDs.

Re[6]: Checkpointing threads

micAbstractUpdateRequest [onRes=false, >nearNodeId=null, nearFutId=0, flags=, Message closure [msg=GridIoMessage >[plc=2, topic=TOPIC_CACHE, topicOrd=8, ordered=false, timeout=0, >skipOnTimeout=false, msg=GridNearAtomicSingleUpdateRequest >[key=BinaryObjectImpl [arr= true, ctx=false, start=0]

Re[4]: Checkpointing threads

check point  >threads themselves utilise async I/O tasks and interleave I/O activities on >that basis then there may not be an opportunity for performance improvement, >but I am not an expert in the Ignite code base :) >  >Raymond. >    >On Wed, Sep 7, 2022 at 7:51 PM Zhenya Sta

Re[2]: Checkpointing threads

+-+under+the+hood    >Thanks Zhenya.  >  >Is there any logging or metrics that would indicate if there was value >increasing the size of this pool? >  >  >On Fri, 2 Sep 2022 at 8:20 PM, Zhenya Stanilovsky via user < >user@ignite.apache.org > wrote: >>Hi 

Re: Checkpointing threads

Hi  Raymond   checkpoint threads is responsible for dumping modified pages, so you may consider it as io bound only operation and pool size is amount of disc writing  workers. I think that default is enough and no need for raising it, but it also up to you.   >Hi, >  >I am looking at our configu