HI
Scanquery on a cache is not working, but simple GET with a key and select
statement on SQL console working fine. This is the error I get on the client
side
Ignite cluster is unavailable
[sock=14555e0a[TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384:
Hi team,
Just wandering what happened behind a remote service call.
Is there anything persisted for a service call? Or the service call is
actually based on memory grid?
thank you
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Regards this section of code:
maxDirtyPages = throttlingPlc != ThrottlingPolicy.DISABLED
? pool.pages() * 3L / 4
: Math.min(pool.pages() * 2L / 3, cpPoolPages);
I think the correct ratio will be 2/3 of pages as we do not have a
throttling policy
Hi Zhenya,
The matching checkpoint finished log is this:
2020-12-15 19:07:39,253 [106] INF [MutableCacheComputeServer] Checkpoint
finished [cpId=e2c31b43-44df-43f1-b162-6b6cefa24e28, pages=33421,
markPos=FileWALPointer [idx=6339, fileOff=243287334, len=196573],
walSegmentsCleared=0,
Hello!
Sounds correct to me.
Regards,
--
Ilya Kasnacheev
ср, 30 дек. 2020 г. в 14:23, Naveen :
> On the same email chain what is the best way to create a cache, which
> should work for both KV, Binary and SQL CREATE TABLE IF NOT EXISTS
> curated.TEST_1_COPY ( test_id VARCHAR, test_f1
All write operations will be blocked for this timeout :
checkpointLockHoldTime=32ms (Write Lock holding) If you observe huge amount of
such messages : reason=' too many dirty pages ' may be you need to store
some data in not persisted regions for example or reduce indexes (if you use
Correct code is running from here:
if (checkpointReadWriteLock.getReadHoldCount() > 1 ||
safeToUpdatePageMemories() || checkpointer.runner() == null)
break;
else {
CheckpointProgress pages = checkpointer.scheduleCheckpoint(0, "too many
dirty pages");
and near you can see that :
On the same email chainwhat is the best way to create a cache, which should
work for both KV, Binary and SQLCREATE TABLE IF NOT EXISTS
curated.TEST_1_COPY ( test_id VARCHAR, test_f1 VARCHAR, created_On1
timestamp, PRIMARY KEY (test_id)) WITH "TEMPLATE=TemplateWith1Copy,
Hello!
I can see the following ticket in our JIRA:
https://issues.apache.org/jira/browse/IGNITE-13504
However, I don't see any obvious workaround from Ignite side. Maybe it may
be configured in your network stack.
Regards,
--
Ilya Kasnacheev
пн, 21 дек. 2020 г. в 19:40, rakshita04 :
> Hi
In (
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood),
there is a mention of a dirty pages limit that is a factor that can trigger
check points.
I also found this issue:
http://apache-ignite-users.70518.x6.nabble.com/too-many-dirty-pages-td28572.html
I'm working on getting automatic JVM thread stack dumping occurring if we
detect long delays in put (PutIfAbsent) operations. Hopefully this will
provide more information.
On Wed, Dec 30, 2020 at 7:48 PM Zhenya Stanilovsky
wrote:
>
> Don`t think so, checkpointing work perfectly well already
11 matches
Mail list logo
