Hi Raymond
It does block writes until the checkpoint is complete, but this only happens
when we restart our nodes, that time all the piled up requests (during the
shutdown) gets processed, thats when bulk data ingestion happens, otherwise
for normal day to day real time operations it does not
Hi,
I have .Net ClientServer Ignite Application.I am using DataStreamer to load
data into ignite caches.
while loading data client node getting stop with stackoverflow message .And
on server node displaying message on console like
Error:data-streamer-stripeTimed out while waiting for schema
To clarify, I do not want to pause rebalancing. I want to see if a
rebalancing job is in progress, delay my job and a rebalancing job is not
in progress, delay any upcoming rebalancing job, till my job is finished.
On Wed, Jan 13, 2021 at 5:04 PM narges saleh wrote:
> Thanks Alex. I will study
Thanks Alex. I will study the links you provided. I need to deal with
rebalancing programmatically.
On Wed, Jan 13, 2021 at 4:33 PM akorensh wrote:
> Hi,
> You can monitor using JMX as described here:
>
> https://ignite.apache.org/docs/latest/monitoring-metrics/metrics#monitoring-rebalancing
Hi,
You can monitor using JMX as described here:
https://ignite.apache.org/docs/latest/monitoring-metrics/metrics#monitoring-rebalancing
you can also visually monitor rebalance via a special widget in control
center:
Hi All,
What is the best practice regarding partition rebalancing and jobs?
1) Before I start a job, how do I check whether a rebalancing process is in
progress?
2) If no rebalancing is in progress, how do I delay or pause upcoming
rebalancing processes until my job is finished, assuming I don't
Hello everyone.
I have several ignite clusters with version 2.7.6 and persistence enabled.
I have a 3 caches on every cluster, with 10M~ records each.
Sometimes when I reboot a node, it takes a lot of time to boot, it can be
hours.
With rebooting I mean stopping the container that's running
Ok thanks , but I am looking forward for the Aws steps.
On Wed, 13 Jan 2021 at 11:39, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Hi Sri,
>
> This will be available in future releases. Current alpha focuses on
> demonstrating how Ignite 3.0 will be delivered, and how you will
Hi Sri,
This will be available in future releases. Current alpha focuses on
demonstrating how Ignite 3.0 will be delivered, and how you will run
operations using the new CLI tool.
-Val
On Wed, Jan 13, 2021 at 11:21 AM sri hari kali charan Tummala <
kali.tumm...@gmail.com> wrote:
> Sure few
Hi Wesley,
This is quite a long-term project, so it's hard to have exact predictions -
it all depends on how fast the code is contributed. But based on the scope,
I think we're looking towards around the end of this year - early next year.
-Val
On Tue, Jan 12, 2021 at 8:26 PM Wesley Peng
The meetup has been scheduled, please RSVP here:
https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/275722317/
-Val
On Wed, Jan 13, 2021 at 11:21 AM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Link to the Getting Started Guide:
>
Link to the Getting Started Guide:
https://ignite.apache.org/docs/3.0.0-alpha/quick-start/getting-started-guide
-Val
On Tue, Jan 12, 2021 at 7:55 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Igniters,
>
> I'm excited to announce that the first alpha build of the Ignite 3 is
Sure few steps are missing.
Creating a ignite cluster is missing (example 3 ec2 instances)
Creating a ignite cluster on Aws would be nice step to add
Thanks
Sri
On Wed, 13 Jan 2021 at 04:14, Kseniya Romanova
wrote:
> Here's the link for the online gathering:
>
Sorry about mixing the terminology. My post was meant to be about the PME
and the primary keys.
So the summary of my post and what it was trying to show was the PME was
only happening on cluster node leaves (server or visor) but not cluster node
joins (at least with previously joined nodes -
Haven't tested on 2.9.1 as we don't have that database provisioned and sadly
won't for awhile. When we do though I will update.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Let me debug this a bit more. Also I will try and capture another set of
thread dumps when this occurs again. This issue occurs on my windows machine
sometimes - doesnt happen all the time. I have not seen this on my linux
env. yet.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I dont think the server dumps were taken after the client disconnected . They
were taken when the client was in the stuck state.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Kindly confirm the below :
a. Are you on :2.8.1
b. Is this cod uncommented :
ignite.active(true);
addPersistentCacheConfiguration(
ignite);
c. using both server and client on the reproducer?
I get this on all env. ( even in our linux env. )
--
Sent from:
Hello!
Maybe it's some kind of Windows thing or otherwise depends on your
environment? I have tried to run your reproducer, but I never get these
exceptions. Instead, I will only see:
янв 13, 2021 6:38:56 PM org.apache.ignite.logger.java.JavaLogger info
INFO: Accepted incoming communication
Hello!
But are they collected after the client node has already left? Not to
mention that server nodes too have an obscene number of threads, and as
such are vulnerable to the same problem.
Regards,
--
Ilya Kasnacheev
ср, 13 янв. 2021 г. в 18:25, VeenaMithare :
> Hello,
>
> Thread dump from
Hello,
Thread dump from the server nodes has been provided in the original post,
regards,
Veena
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi, As you correctly pointed to the PME implementation details webpage, this is a process of exchanging information about partition holders. And it’s happening on every topology change, cluster deactivation, etc. The process itself is not about data rebalancing, it’s about what node should store a
Hello!
Does it happen to work on 2.9.1, or will fail too? I recommend checking it
since I vaguely remember some discussions about late affinity assignments
fix.
Regards,
--
Ilya Kasnacheev
сб, 9 янв. 2021 г. в 03:11, tschauenberg :
> Here's my attempt to demonstrate and also provide logs
>
>
Hello!
Please provide full thread dump from server nodes.
Of course, you will need to kill client JVM first.
Regards,
--
Ilya Kasnacheev
ср, 13 янв. 2021 г. в 17:09, VeenaMithare :
>
> a. If you see the thread dump, it shows these locked synchronizers
>Locked ownable synchronizers:
>
a. If you see the thread dump, it shows these locked synchronizers
Locked ownable synchronizers:
- <0x0006da73f540> (a
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
- <0x0006da73f690> (a
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
Hello!
I'm not sure what happens on the server nodes. Restarting the JVM with this
client should be enough.
Regards,
--
Ilya Kasnacheev
вт, 12 янв. 2021 г. в 19:14, VeenaMithare :
> Okay, thanks Ilya . After it gets this issue, the app doesnt startup till
> I
> restart my server nodes.
>
>
Hi, It’s too internal details and it’s not possible to catch *Critical Workers HealthCheck* on client side. I think you might want to listen for Ignite events on your clients and apply your custom logic accordingly. The most essential candidate - EVT_NODE_FAILED You might check more available
Here's the link for the online gathering:
https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/275722317/
ср, 13 янв. 2021 г. в 13:47, Pavel Tupitsyn :
> Getting Started Guide:
>
> https://ignite.apache.org/docs/3.0.0-alpha/quick-start/getting-started-guide
>
> On Wed, Jan 13, 2021 at
Raymond,
Please use ICluster.SetActive [1] instead, the API linked above is obsolete
[1]
https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cluster.ICluster.html?#Apache_Ignite_Core_Cluster_ICluster_SetActive_System_Boolean_
On Wed, Jan 13, 2021 at 11:54 AM Raymond
Getting Started Guide:
https://ignite.apache.org/docs/3.0.0-alpha/quick-start/getting-started-guide
On Wed, Jan 13, 2021 at 1:29 PM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:
> What is the link to the Getting Started Guide?
>
> On 13 Jan 2021, at 03:55, Valentin Kulichenko <
>
What is the link to the Getting Started Guide?
> On 13 Jan 2021, at 03:55, Valentin Kulichenko
> wrote:
>
> Igniters,
>
> I'm excited to announce that the first alpha build of the Ignite 3 is out and
> available for download!
>
> Ignite 3 is the new project that was initiated by the Ignite
Of course. Obvious! :)
Sent from my iPhone
On 13/01/2021, at 9:15 PM, Zhenya Stanilovsky wrote:
Is there an API version of the cluster deactivation?
https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core.Tests/Cache/PersistentStoreTestObsolete.cs#L131
Hi,
I had raised this ticket:
https://issues.apache.org/jira/browse/IGNITE-13974
Currently I do not see any cleanup functions getting called when we do a
'kubectl delete pod'.
May I know, what is the best practice for restarting k8s ignite pod ?
How do we handle scenario when we need to scale
When will the stable version of 3.0 get released? thanks.
Valentin Kulichenko wrote:
I'm excited to announce that the first alpha build of the Ignite 3 is
out and available for download!
Ignite 3 is the new project that was initiated by the Ignite community
last year. Please refer to this
>Is there an API version of the cluster deactivation?
https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core.Tests/Cache/PersistentStoreTestObsolete.cs#L131
>On Wed, Jan 13, 2021 at 8:28 PM Zhenya Stanilovsky < arzamas...@mail.ru >
>wrote:
>>
>>
>>
35 matches
Mail list logo
