?????? Read request response time is unstable, often more than500milliseconds, but the cluster load is small

Using the LOG_ONLY mode, I remember having encountered this problem. After the node rebooted and printed an error message, the node could not be started. At that time, I did not reserve the error message. I searched for the source code, which may be one of the two. 1. 'Failed to find

Re: Example of SQL query

I didn't exactly get 1), but I'm sure your best bet is to use keyConfiguration (CacheKeyConfiguration) in this case to set affinity key. Otherwise you're at risk of getting "incompatible affinity keys" error. BTW isn't it a better topic for dev@? Care to crosspost? Regards, -- Ilya Kasnacheev

?????? Read request response time is unstable, often more than 500milliseconds, but the cluster load is small

Hi, I have tested -DIGNITE_WAL_FSYNC_WITH_DEDICATED_WORKER=true set this parameter, but it will seriously affect the write speed, I do not know what the impact of setting this parameter is, whether it is necessary to set other parameters to increase the write speed? --

Re: Read request response time is unstable, often more than 500milliseconds, but the cluster load is small

Please, try to check performance with LOG_ONLY mode. 2018-05-10 12:03 GMT+03:00 NO <727418...@qq.com>: > Hi, > > I have tested -DIGNITE_WAL_FSYNC_WITH_DEDICATED_WORKER=true set this > parameter, but it will seriously affect the write speed, I do not know what > the impact of setting this

Re: Read request response time is unstable, often more than500milliseconds, but the cluster load is small

Ignite node should start with any wal mode. I suppose that the same error should be occurred with FSYNC mode. Would you be able to restart with LOG_ONLY mode and show the logs. 2018-05-10 12:39 GMT+03:00 NO <727418...@qq.com>: > Using the LOG_ONLY mode, I remember having encountered this

Re: Read request response time is unstable, often more than 500 milliseconds, but the cluster load is small

Hi, I see several exceptions in your logs. Probably it causes the slowdown. >> java.lang.ClassCastException: org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager cannot be cast to

Re: Local Client not connecting to Server deployed in azure cloud.

Hi, I am running ignite with -Djava.net.preferIPv4Stack=true and also ports 47100, 47101, 47500. Server nodes and Client nodes are connecting but after some interval it throwing connection timeout. and in visior, if queried for cache -scan then going to hang and after some time throwing

Re: Local Client not connecting to Server deployed in azure cloud.

This is my Ignite Configurations for both server in vm1 and client in vm2, public static IgniteConfiguration getIgniteConfig() throws Throwable { TcpDiscoverySpi discoverySpi = new TcpDiscoverySpi(); discoverySpi.setLocalPort(47500);

Re: Local Client not connecting to Server deployed in azure cloud.

Hello! I can see that your local node is trying to connect to private IP ranges: 10.0.0.9 and 192.168.1.31 Those are probably valid only in limited context (just on the cloud, or just in your private network) and not valid otherwise. You could

Re: Local Client not connecting to Server deployed in azure cloud.

Hi, Now I have two VM in azure cloud. In one vm started Ignite Server and in another Ignite Clients. Both are configured with same subnet. Server and Client are connected. But below error throwing continuously.. Can you give some suggestions to solve this issue?. 2018-05-10 13:45:45 ERROR

Re: Local Client not connecting to Server deployed in azure cloud.

Hello! Can you please provide details on the exact network configuration on both servers? BTW, if the remoteAddr in your example was an external IP, this might be the source of problem. Try setting localAddress on communicationSpi to local address of server on both clients and server nodes.

Re: Id-generator

Hello! For example, you could have an IgniteAtomicLong, call incrementAndGet() on it. This way you can be reasonably sure that numbers are unique per cluster. Regards, -- Ilya Kasnacheev 2018-05-10 16:59 GMT+03:00 Rusher,Gary : > Hi, > > > > Doing proof of

Id-generator

Hi, Doing proof of concept. Having an issue with identity column, found it's not possible, but there's a workaround using the ID-generator. How does this work? If I have numerous clients attempting to write db records, won't the id-generator fail to provide a unique value? Maybe? Can anyone

Unsubscribe

Re: why I can't join node?(Error msg : Some error in join process)

Hi Thanks for reply. I checked my classpath. There is Guava dependency. I think it conflict with Ignite's Guava. I think below is almost almost same in my case. https://stackoverflow.com/questions/49154736/apache-ignite-old-guava-dependency-conflict So, i resolved. Thank you! -- Sent from:

Re: NullPointer Exception in Continuous Query

Hi Seems to you have the issue related to https://issues.apache.org/jira/browse/IGNITE-7865 that fixed in the 2.5 version. As workaround you could change WALMode to LOG_ONLY or start ignite with the jvm property -DIGNITE_WAL_FSYNC_WITH_DEDICATED_WORKER=true Thanks, Pavel 2018-05-10 9:50

Re: NullPointer Exception in Continuous Query

Thanks for reply, but unfortunately, I could understand the details in the link provided. Could you please brief about it. Whats the root cause. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

NullPointer Exception in Continuous Query

Hi, I am getting this exception in logs but not sure on which cache it is happening. Logs does not help me identifying the cache either. Apologies to ask here without much details but just wondering if someone know what are the chances to get this exception. I have set of caches and CacheMode is

Unsubscribe

On Thu, May 10, 2018 at 10:19 AM wrote: >

Re: Id-generator

You can specify atomic configuration in your Ignite configuration XML, but you will have to do key generation manually. Allocate an IgniteAtomicLong, call methods on it. Regards, -- Ilya Kasnacheev 2018-05-10 17:50 GMT+03:00 Rusher,Gary : > So can I specify

Re: Local Client not connecting to Server deployed in azure cloud.

what I thought is, if we are not setting communication api it will take default value as local only. Is that the scenario right? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Id-generator

So can I specify IgniteAtomicLong in my cacheconfiguration xml I use to bring up my server node? Gary From: Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com] Sent: Thursday, May 10, 2018 9:17 AM To: user@ignite.apache.org Subject: Re: Id-generator Hello! For example, you could have an

Re: Local Client not connecting to Server deployed in azure cloud.

Hello! I'm not sure about that. I recommend removing the guesswork from this scenario, trying to configure everything explicitly. Once you get your cluster working you can ease some options to default. Regards, -- Ilya Kasnacheev 2018-05-10 18:04 GMT+03:00 JP : > what I

Re: Example of SQL query

Denis, If this will be awailable in ignite-2.5 Why link is pointing to 2.4 ? On Thu, May 10, 2018 at 9:53 PM, Denis Magda wrote: > Guys, > > Starting with Ignite 2.5 it will be possible to use other types of keys in > addition to String:

Re: Example of SQL query

Guys, Starting with Ignite 2.5 it will be possible to use other types of keys in addition to String: https://apacheignite.readme.io/v2.4/docs/rest-api-25#section-data-types -- Denis On Thu, May 10, 2018 at 4:39 AM, Ilya Kasnacheev wrote: > I didn't exactly get 1),

Re: Local Client not connecting to Server deployed in azure cloud.

As I have already said, try to add TcpCommunicationSpi setter and set local address for it. Taking hints from https://apacheignite.readme.io/docs/cluster-config#section-isolated-ignite-clusters-on-same-set-of-machines Regards, -- Ilya Kasnacheev 2018-05-10 17:31 GMT+03:00 JP

Unsubscribe Me

Please unsubscribe me from the mailing list. Thanks

Re: Local Client not connecting to Server deployed in azure cloud.

Just noticed that three ipaddress assigned to server vm. Change my configuration with communication api. Still facing issue. 2018-05-10 16:12:33 ERROR TcpDiscoverySpi:495 - Failed to initialize connection (this can

Re: Unsubscribe

Hi, You need to send a message to this address: user-unsubscr...@ignite.apache.org -- Denis On Thu, May 10, 2018 at 8:17 AM, Janet Mendoza wrote: > > On Thu, May 10, 2018 at 10:19 AM wrote: > >>

Re: Unsubscribe Me

Hi, You need to send a message to this address: user-unsubscr...@ignite.apache.org -- Denis On Thu, May 10, 2018 at 8:19 AM, Amit Pundir wrote: > Please unsubscribe me from the mailing list. Thanks >

Re: Local Client not connecting to Server deployed in azure cloud.

Please check this https://blogs.msdn.microsoft.com/mast/2015/05/18/what-is-the-ip-address-168-63-129-16/ That ip belongs to Azure -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Local Client not connecting to Server deployed in azure cloud.

Hello! If your client tries to connect to your server and server sees this as traffic from 168.63.129.16, unfortunately that won't work. Intra-cluster Ignite connections can be reversed (it is not a client-server protocol rather than server-server), this means that connections should come from

Re: Local Client not connecting to Server deployed in azure cloud.

Now, I am just running only one server. In that only I am facing this error 2018-05-10 16:42:31 INFO TcpDiscoverySpi:475 - Started serving remote node connection [rmtAddr=/168.63.129.16:64338, rmtPort=64338] 2018-05-10 16:42:32 ERROR TcpCommunicationSpi:495 - Failed to process selector key

Re: Local Client not connecting to Server deployed in azure cloud.

Hello! Unfortunately it's hard to say from this message alone, can you put logs from all nodes somewhere? However, immediate red sign is that local and remote are in different class of networks. Regards, Ilya -- Ilya Kasnacheev 2018-05-10 19:45 GMT+03:00 JP : > Now, I

Re: Unsubscribe Me

Ive sent mail on user-unsubscr...@ignite.apache.org to unsubscribe thrice but still I am not unsubscribed yet. Thanks Shaleen From: Denis Magda Sent: Friday, 11 May, 3:03 am Subject: Re: Unsubscribe Me To: user@ignite.apache.org Hi, You need to

Re: Local Client not connecting to Server deployed in azure cloud.

Hi, Please find the logs from this link https://files.fm/u/mprbmab3#/view/logs.txt -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Local Client not connecting to Server deployed in azure cloud.

I am just running only one node. I didn't run other nodes... -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Local Client not connecting to Server deployed in azure cloud.

Hello! Are you sure that you can connect from one server to another? Maybe you have to adjust firewall rules? What does "nc anotherhost:47500" return? Can you type something there, get a response from server? Regards, -- Ilya Kasnacheev 2018-05-10 19:26 GMT+03:00 JP :

Re: Unsubscribe

Hi, You need to send a message to this address: user-unsubscr...@ignite.apache.org -- Denis On Wed, May 9, 2018 at 8:40 PM, Shaleen Sharma wrote: > > > Thanks > Shaleen > >

Re: Local Client not connecting to Server deployed in azure cloud.

I can see a suspicious "Failed to read magic header (too few bytes received)" message. Something is not right. Can we see log for the node that tries to connect here? Is it possible, btw, that 10.0.0.4 and 168.63.129.16 are on the same server and thus it tries to discover itself without

Re: Ignite hangs forever on add node

Hi, This is a known issue and is already fixed: https://issues.apache.org/jira/browse/IGNITE-8134 After calling cluster.active(true), cluster nodes form baseline topology and currently it's impossible to deploy services from node out of topology on active cluster. Will be available in future

Re: Unsubscribe Me

Is it the same email ? you have no forwarding, old email or something ? are you unsubscribing the same email as you subscribed ? Den 2018-05-10 kl. 19:17, skrev Shaleen Sharma: Ive sent mail on user-unsubscr...@ignite.apache.org to unsubscribe

RE: Ignite hangs forever on add node

Thanks for answer. After detail testing of this case I found some strange things in service starting. If autoActivation is enabled, then services correct start only after cluster restart. Deactivation and node restart cause cluster activation, but not start services. I can send reproducing

Node FAILED

Hi, We are running ignite 2.3 grid in 40 nodes cluster. 1 ignite server, 2 ignite clients per each node. so, total 40 ignite servers 80 ignite clients Topology snapshot [ver=120, servers=40, clients=80, CPUs=640, heap=560.0GB] It runs ok upto about 12 hours uptime, and total partitioned

Re: Node FAILED

It seems like ignite server process frozen. The dotnet ignite server process is still alive, but metrics stopped, no other logs, no CPU usage. This is the last error message in ignite server logs. * server log (in attached logfile) 2018/05/10 18:49:56.343 [INFO

Re: Node FAILED

jstack dump attached. ignite-jstack.txt -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

How to cancel long running sql query in sqlline?

After I restarted an Ignite cluster using persistent store, I ran a query in sqlline which takes a long time to finish. Is there any way to cancel that query? I googled and found run ran by java code can be canceled, so I wonder is there any way to cancel a sql query ran by sqlline? -- Sent

Re: How to cancel long running sql query in sqlline?

I tried killing the sqlline process, but it is not working. The sql is still running in the Ignite cluster because Ignite's response time is affected and the disk io is high(the long running sql is intended to load data from persistent store to memory) Also I tried ODBC, looks like when abort the

?????? Read request response time is unstable, often morethan500milliseconds, but the cluster load is small

I only encountered this problem once. I did not reproduce this problem in FSYNC mode, I have time to find ways to reproduce the problem. Regarding the issue of read performance degradation, I used the -DIGNITE_WAL_FSYNC_WITH_DEDICATED_WORKER=true parameter, but the problem was not solved.