Hi Veena,
There is a message in the logs:
[WARNING][jvm-pause-detector-worker][IgniteKernal] Possible too long JVM
pause: 8023 milliseconds.
In most cases, it is a sign of the long GC pause. Of course, this JVM pause
can be related to the problems with a virtual environment or something
else, bu
Hi Evgenii,
Thank you for the reply and suggestion.
regards,
Veena.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
For each connection, on node side will be created its own datastreamer. I
think it makes sense to try pooling for data load, but you will need to
measure everything, since the pool size depends on the lot of things
вт, 14 апр. 2020 г. в 07:31, narges saleh :
> Yes, Evgenii.
>
> On Mon, Apr 13, 20
Evgenii,
It also came to me if there is a similar code in C++ for the following java
code as I did not find it. If not, Does it mean I need to configure it in
xml file?
IgniteConfiguration igniteConfiguration = new IgniteConfiguration();
BinaryConfiguration bCfg = new BinaryConfiguration(
Hi Kay, Could you please describe your case with more details?It would be great if you could explain what exactly confuses you in the Ignite websession management algorithm. As far as I know it uses common java contract about the method https://javaee.github.io/javaee-spec/javadocs/javax/servlet/ht
Can you provide full log files from all nodes? it's impossible to find the
root cause from this.
Evgenii
вт, 14 апр. 2020 г. в 07:49, Rajan Ahlawat :
> server starts with following configuration:
>
> ignite_application-1-2020-03-17.log:14:[2020-03-17T08:23:33,664][INFO
> ][main][IgniteKernal%ign
Hi,
Segmentation plugin won't help with the issue itself. If you have a long GC
pause, it means that node is unresponsive for all this time. If you have GC
pause longer than 10 seconds, node will be dropped from the cluster(by
default). If you have long GC pauses, probably your load too big for yo
server starts with following configuration:
ignite_application-1-2020-03-17.log:14:[2020-03-17T08:23:33,664][INFO
][main][IgniteKernal%igniteStart] IgniteConfiguration
[igniteInstanceName=igniteStart, pubPoolSize=32, svcPoolSize=32,
callbackPoolSize=32, stripedPoolSize=32, sysPoolSize=30,
mgmtPool
Yes, Evgenii.
On Mon, Apr 13, 2020 at 10:06 PM Evgenii Zhuravlev
wrote:
> Hi,
>
> Do you use STREAMING MODE for thin JDBC driver?
>
> Evgenii
>
> пн, 13 апр. 2020 г. в 19:33, narges saleh :
>
>> Thanks Alex. I will study the links you provided.
>>
>> I read somewhere that jdbc datasource is avai
Hi Dmitry,
Would having a segmentation plugin help to resolve segmentation due to GC
pauses ?
Or is the best resolution for long GC pauses is to resolve it and get the GC
pauses to be within the failure detection timeout ?
regards,
Veena.
--
Sent from: http://apache-ignite-users.70518.x6.nab
Thanks for sharing this useful info
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
11 matches
Mail list logo