(which are still only 63k).
>
> Please make extra sure that when you open a socket, you close it regardless
> of errors, etc.
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-07-05 13:33 GMT+03:00 胡海麟 :
>>
>> Hi,
>>
>> Challenged again and I'm back :)
&g
oth.
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-07-04 13:19 GMT+03:00 胡海麟 :
>>
>> Hi,
>>
>> After googling for 1 hour to get nothing, I'm back for some basic
>> knowledges.
>>
>> igniteConfiguration.setConnectorConfiguration(
y setting
> igniteConfiguration.setConnectorConfiguration(new
> ConnectorConfiguration().setThreadPoolSize(64))
> Or the corresponding Spring XML.
>
> This is as per https://apacheignite.readme.io/docs/rest-api
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-07-04 12:04 GMT+03:00 胡海麟 :
>>
&g
readPoolSize(64))
> Or the corresponding Spring XML.
>
> This is as per https://apacheignite.readme.io/docs/rest-api
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-07-04 12:04 GMT+03:00 胡海麟 :
>>
>> Hi,
>>
>> Here is the thread dump.
>>
>> Thank
t have to take a look at the thread dump to be sure.
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-07-04 11:33 GMT+03:00 胡海麟 :
>>
>> Hi,
>>
>> We use ignite as a redis server.
>>
>> The use case is
>> a. Write timeout is 15ms on the cl
Sorry, write req/s was wrong.
It is about 25,000, 12,500/s for each node.
On Wed, Jul 4, 2018 at 5:33 PM, 胡海麟 wrote:
> Hi,
>
> We use ignite as a redis server.
>
> The use case is
> a. Write timeout is 15ms on the client side.
> b. 2 server nodes. each is an EC2 r4.4xlarge
Hi,
After have some more tests, I believe the things are like this:
1. client writes to ignite and timeout (client setting is 15ms)
2. client resets the connection since it seems dead (timeout).
3. server catches the connection reset and throw the exception
Actually, it's just a normal use case
Hi,
We use ignite as a redis server.
The use case is
a. Write timeout is 15ms on the client side.
b. 2 server nodes. each is an EC2 r4.4xlarge instance.
c. Write req/s is about 120,000. In another word, 60,000 for each node.
The problem is that timeout happens frequently, several ones per
Hi,
In case dial timeout, client is nil so that client.Close() can't work.
Thanks.
Hi,
Sorry I have no knowledge about maven.
Here is my config file and sample code of the client.
I reproduced "Connection reset by peer" by adjust the timeout setting,
but ignite's file descriptor count didn't increase.
Before ignite was halted by "Too many open files", there was a close
wait
I set it 32768, exhausted. I have many clients to connect to ignite,
but don't have so many.
I'm afraid that to set it higher just win me a little more time, but
not a solution.
On Mon, Jun 25, 2018 at 5:20 AM, David Harvey wrote:
> MYou must increase the Linux NOFILE ulimit when running Ignite.
Hi,
Re-post message 'cause I failed to post my logs pasted.
I have got repeated Too many open files exceptions since sometime.
[11:26:24,493][SEVERE][grid-nio-worker-tcp-rest-1-#57][GridTcpRestProtocol]
Failed to process selector key
Hello,
The docs says:
https://apacheignite-tools.readme.io/docs/ignite-web-console
The web console also features cluster monitoring functionality
(available separately as GridGain plugin) that shows various cache and
node metrics as well as CPU and heap usage.
I googled and failed to find
Wow, I got it.
Thank you very much.
On Fri, Jun 15, 2018 at 11:28 PM, ilya.kasnacheev
wrote:
> Hello!
>
> It turns out that Dalli will marshal data by default, and set 'serialized'
> flag in memcached message.
> Apache Ignite will treat 'serialized' data as Java Serialized Objects, will
>
Hello,
https://apacheignite.readme.io/docs/memcached-support
I have run php and ruby codes according to the page above, and perl
and golang ones with library using memcache binary protocol, but only
the php codes work.
Especially, I require a piece of workable ruby codes. My test shows
that it
15 matches
Mail list logo