Hi Ilya,
Looking at the logs, every time checkpoint starts due to
‘timeout’ reason not because the buffer is full. So still do we need to
increase checkpointing buffer or only changing checkpointing frequency will
help ?
Thanks and Regards,
Kamlesh Joshi
From: Ilya Kasnacheev <ilya.kasnach...@gmail.com>
Sent: Wednesday, May 22, 2019 4:19 PM
To: user@ignite.apache.org
Subject: Re: [External]Re: Read/query TPS is decreasing after enabling mix load
i.e. write services
The e-mail below is from an external source. Please do not open attachments or
click links from an unknown or suspicious origin.
Hello!
We recommend using SSD and not HDD with Ignite. Otherwise, try to increase size
of Checkpoint Page Buffer - if you run out of this buffer, all activity will
stop until checkpoint is finished. Maybe you also need to decrease time between
checkpoints.
Regards,
--
Ilya Kasnacheev
вт, 7 мая 2019 г. в 13:01, Kamlesh Joshi
<kamlesh.jo...@ril.com<mailto:kamlesh.jo...@ril.com>>:
Hi,
Unfortunately, I cant share the reproducer.
We are using Ignite Binary Objects for performing operations on the cluster
(Get/Put). We have exposed these operations to other application (i.e. TIBCO BW
services) which performs operations on the cluster.
Thanks and Regards,
Kamlesh Joshi
-----Original Message-----
From: Maxim.Pudov <pudov....@gmail.com<mailto:pudov....@gmail.com>>
Sent: Wednesday, April 17, 2019 8:18 PM
To: user@ignite.apache.org<mailto:user@ignite.apache.org>
Subject: [External]Re: Read/query TPS is decreasing after enabling mix load
i.e. write services
The e-mail below is from an external source. Please do not open attachments or
click links from an unknown or suspicious origin.
Hi, could you share a reproducer of your problem? We are missing a lot of
information here. The configuration of your nodes, cache configurations, what
API you use to query and update the data.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
"Confidentiality Warning: This message and any attachments are intended only
for the use of the intended recipient(s).
are confidential and may be privileged. If you are not the intended recipient.
you are hereby notified that any
review. re-transmission. conversion to hard copy. copying. circulation or other
use of this message and any attachments is
strictly prohibited. If you are not the intended recipient. please notify the
sender immediately by return email.
and delete this message and any attachments from your system.
Virus Warning: Although the company has taken reasonable precautions to ensure
no viruses are present in this email.
The company cannot accept responsibility for any loss or damage arising from
the use of this email or attachment."
"Confidentiality Warning: This message and any attachments are intended only
for the use of the intended recipient(s).
are confidential and may be privileged. If you are not the intended recipient.
you are hereby notified that any
review. re-transmission. conversion to hard copy. copying. circulation or other
use of this message and any attachments is
strictly prohibited. If you are not the intended recipient. please notify the
sender immediately by return email.
and delete this message and any attachments from your system.
Virus Warning: Although the company has taken reasonable precautions to ensure
no viruses are present in this email.
The company cannot accept responsibility for any loss or damage arising from
the use of this email or attachment."
