No, we are using Atomicity as atomic. One of the cache we are querying data
from having 30GB data on single node & we have heap size of 24GB
Does it cause any problem?
Do we need to keep the heap more than the data we have on the cache?
Thanks
On Sat, 9 Jul, 2022, 12:47 am Stephen Darlington, <
We’d need to see more of the log to figure out what the problem is. That’s just
the end of a thread dump and not not the error itself.
> On 6 Jul 2022, at 19:12, Farhan Abdul Shakoor wrote:
>
> Hi Folks,
>
> We are running into strange issues in running queries into ignite. Here is
> our cur
Hi Folks,
We are running into strange issues in running queries into ignite. Here is
our current setup
- 8 Node ignite on 128 GB VMs deployed on Azure kubernetes
- Persistence enabled with 30GB Data region size
With following node configuration:
s and check if the query scales
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Complex-queries-tp9626p9764.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
nabble.com/Complex-queries-tp9626p9764.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
eck the execution plan [1] to make sure everything works as expected.
>
> [1] http://apacheignite.gridgain.org/docs/performance-and-debugging
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Complex-queries-tp9626p9630.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
s.70518.x6.nabble.com/Complex-queries-tp9626p9630.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
HI,
are there any recommendations (other than affinity) for complex queries
like below.
SELECT DISTINCT b.id, b.filename, a1.name
FROM a a1
JOIN b
ON b.id = a1.id
LEFT JOIN (select a.id, max(rank) latest from a group by a.id) a2
ON a2.id = a1.id
Thanks.
help required.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Building-complex-queries-to-query-ignite-Cache-tp9392p9524.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Please, see my answer in upper post.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Building-complex-queries-to-query-ignite-Cache-tp9392p9398.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
t id;
>> private TradeStatus status;
>> private String tradeType;
>> public Trade(int id, TradeStatus status, String tradeType) {
>> this.id = id;
>> this.status = status;
>> this.tradeTy
id = id;
> this.status = status;
> this.tradeType = tradeType;
> }
>
> //setter getter, equals, hashcode methods
>
> public enum TradeStatus {
> NEW, CHANGED, EXPIRED, FAILED, UNCHANGED
> }
>
>
&g
ttp://apache-ignite-users.70518.x6.nabble.com/file/n9395/ignite.png>
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Building-complex-queries-to-query-ignite-Cache-tp9392p9395.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
(int id, TradeStatus status, String tradeType) {
> this.id = id;
> this.status = status;
> this.tradeType = tradeType;
> }
>
> //setter getter, equals, hashcode methods
>
> public enum TradeStatus {
>
this.id = id;
this.status = status;
this.tradeType = tradeType;
}
//setter getter, equals, hashcode methods
public enum TradeStatus {
NEW, CHANGED, EXPIRED, FAILED, UNCHANGED
}
--
View this message in context:
http://apache-ignite
15 matches
Mail list logo
