Hi Igniters,
We were performing PT for ignite cluster and observed that
after enabling write services, query service TPS drops more than 1500 TPS.
While analyzing thread dump we found that only one thread is writing to disk
(native persistence enabled) and rest all are in WAITING state. Please find
below analysis of the same (we are using default Thread pool configuration) :
sys-stripe-43-#44%EDIFCustomer% thread obtained
java.util.concurrent.locks.ReentrantLock$NonfairSync's lock & did not release
it for writing to file.
sys-stripe-43 thread is performing IO operations for persistency, due to that
all other threads are in WAITING state as shown below.
[cid:[email protected]]
System details as follow:
1. CPU 48 core
2. RAM 190 GB
3. We have separate disk for WAL and DATASTORE
4. HDD is striped
Now the concern is, is this the expected behavior? Or we can change this by
using different thread pools ?
Kindly help !
Thanks and Regards,
Kamlesh Joshi
"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."
