Hi,
We uses Ignite 2.10 with 5 nodes, and we can see one of the nodes with the
below warning message, and the cluster becomes unresponsive at the same time.
May I know what's the possible reason for that, and how we can resolve the
issue? Thanks.
thread=grid-timeout-worker-#22%Ignite%
Thanks Stephen. Will check with them
On Wed, 8 Jun 2022, 15:18 Stephen Darlington, <
stephen.darling...@gridgain.com> wrote:
> This is a mailing list for Apache ignite users. Please contact GridGain
> for support of their software.
>
> On 8 Jun 2022, at 09:53, Surinder Mehra wrote:
>
> Hi,
> I
Hi, Surinder! Thank you for pointing out to the problem.
Seems we have a bug in subquery rewriter. I've filed a ticket for this case. [1]
As a possible workaround you could disable join rewriting by setting the system
property IGNITE_ENABLE_SUBQUERY_REWRITE_OPTIMIZATION to false.
[1]
This is a mailing list for Apache ignite users. Please contact GridGain for
support of their software.
> On 8 Jun 2022, at 09:53, Surinder Mehra wrote:
>
> Hi,
> I deployed gridgain ultimate 2.8.18 to kubernetes with mount point for work
> directory to store ignite data as per steps mentioned
Hi,
I deployed gridgain ultimate 2.8.18 to kubernetes with mount point for work
directory to store ignite data as per steps mentioned below
https://www.gridgain.com/docs/latest/installation-guide/kubernetes/amazon-eks-deployment
It works if I don't use an external mount point for the work
Hi,
Could you please provide an update on this.
On Mon, Jun 6, 2022 at 11:48 AM Zhenya Stanilovsky
wrote:
>
> Hi ! thanks for example, i hope some updates will be here in a short time.
>
>
>
>
> Hi,
> Just wondering if you had an opportunity to look into this.
>
> On Thu, Jun 2, 2022 at 2:52 PM
