Re: Can't write to Ignite cluster

Hello Pavel, I have found out why the topology version keeps increasing. It's because my colleague created a customized Ignite monitor system which will fetches metrics from Ignite visor. And this monitor system will launch a Visor client connects to the cluster every minute, after fetching all

Re: Apache Flink Sink + Ignite: Ouch! Argument is invalid

Hi Ray, Thank you for validating the changes, I see that in cluster mode when I am checking the IgniteSink it is working as desired. In stand alone mode I can see we are getting the exception class org.apache.ignite.IgniteException: Default Ignite instance has already been started. Please take a

RE: Best practice for class versioning: marshaller error

Got it, thanks for the info. Thanks, Calvin -Original Message- From: dkarachentsev [mailto:dkarachent...@gridgain.com] Sent: Monday, July 16, 2018 9:57 PM To: user@ignite.apache.org Subject: RE: Best practice for class versioning: marshaller error Hi Calvin, > Can I assume that

Re: Possible starvation in striped pool

Please find attached thread dump as requested. ServerThreadDump0716.txt -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Running Server Node in UNIX

Thank you. I have all jars in lib as below and added to the cp command. lib folder - ./lib/ignite-indexing-2.5.0.jar ./lib/ignite-rest-http-2.5.0.jar ./lib/mssql-jdbc-6.4.0.jre8.jar ./lib/ignite-slf4j-2.5.0.jar ./ib/...jar source code compiled as below structure(.class)

Re: Running Server Node in UNIX

You cannot include JARs into another JAR, Java is not going to add them to classpath. You should list all required JARs in the '-cp' parameter, or create an uber-JAR with all the dependencies unpacked there. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Running Server Node in UNIX

I don't have IGNITE_HOME set up from my windows- eclipse and able to run without any issue. I have ignite-core, ignite-spring, ignite-indexing and ignite-rest-http in the pom.xml. I am trying to run same structure in UNIX. I have required libs in the jar. Is anything am i missing? -- Sent

Re: Running Server Node in UNIX

Hi, Did you add to IGNITE_HOME to the path? https://apacheignite.readme.io/docs/getting-started#section-with-default-configuration In case if you are going to create maven project then you still need to download the binaries and set the IGNITE_HOME: https://ignite.apache.org/download.cgi BR,

Re: Tracing all SQL Queries

Hi, Yes, it can be specified in your Spring configuration file as follows: ... Thanks, Slava. пн, 16 июл. 2018 г. в 19:39, ApacheUser : > Hi Slava, > Sorry to get into this thread,I have similar problem to control long > running > SQLs. I want timeout SQLs running more than 500ms.

Re: Tracing all SQL Queries

Hi Slava, Sorry to get into this thread,I have similar problem to control long running SQLs. I want timeout SQLs running more than 500ms. I sthere any way to set etLongQueryWarningTimeout() in CONFIG File? Appreciate your response. Thanks -- Sent from:

Re: Port Assigned? Work on specific Node?

Hello! I can address the immediate questions that you are having, but I'm afraid that you will be only getting further away from optimal solution of your case. What is your case? Can you please tell us more about the scenario that you are trying to implement? Regards, -- Ilya Kasnacheev

Re: Port Assigned? Work on specific Node?

I have read the links that you have shared, but there is no information about different clusters I have found Ignite native persistence, can it be a solution for my case? And I have allow to create different cluster in my laptop? ilya.kasnacheev wrote > Hello! > > I think you could use

Re: Possible starvation in striped pool

Hello! Can you please provide the thread dump of problematic cluster after removal of close statements on caches? Regards, -- Ilya Kasnacheev 2018-07-16 17:21 GMT+03:00 Shailendrasinh Gohil < shailendrasinh.go...@salientcrgt.com>: > Thanks again for the response. > > We have tried removing

Re: Possible starvation in striped pool

Thanks again for the response. We have tried removing the close statements but the result was same. And yes, other threads accessing cache from the same Dao. We also tried both the atomicityMode to see if any improvement. We also have write behind enabled for the large tables with frequent get

Re: Exception while running sql inside ignite transaction

Hi Akash, First of all SQL is not transactional yet, this feature will be available only since 2.7 [1]. Your exception might be caused if query was canceled or node stopped. [1] https://issues.apache.org/jira/browse/IGNITE-5934 Thanks! -Dmitry -- Sent from:

RE: Best practice for class versioning: marshaller error

Hi Calvin, > Can I assume that BinaryMarshaller won't be used for any object embedded > inside GridCacheQueryResponse? Yes, because Binary can fallback to Optimized, but not vice versa. > If I am correct, do you have any suggestion on how I can avoid this type > of issue? Probably you need

Re: Port Assigned? Work on specific Node?

Hello! I think you could use ContinuousQuery (with initial query) to copy all data from cache in one cluster to cache in another cluster. It will also take care of the situation where cache on node1 is changed while it is being copied. If

Re: Port Assigned? Work on specific Node?

OMG!!! Yep, If there are belonging to different cluster, there is way to copy caches data? Especially I am looking for ignite features. Now one cluster has 1 datas I will copy these datas to another cluster Sorry man, I forget to write this. -- Sent from:

Re: Port Assigned? Work on specific Node?

thanks, but this is not the answer that I expected, maybe this scenario can be more understandable: 1 cache is in node1, okey, node2 is created and node2 has copy of the node1(and node2 will not be ready until copy is done!!) now in node2 there is cache which name is "myCache" and I iterates

Re: Port Assigned? Work on specific Node?

Hello! I have a feeling that you are trying to perform a manual sunset: reimplement something which is a part of core functionality and always provided out of box. * Apache Ignite will read values from primary node only unless "readFromBackup" property is set. * Anyway, Apache Ignite will not

Re: Port Assigned? Work on specific Node?

thanks for your understanding, Last question, I want to use data rebalancing, because I have scenario like this: let's say node 1 has 1 datas in its caches. (Which cache mode is REPLICATED) Now I will invoke another node2, then node2 will copy of node1's cache datas. But when copying

RE: Deployment of Ignite/Application upgrades to production in 100+ nodecluster

Hi Stan - Thanks a lot for quick response on this. Yeah just checked gridgain and looks likes exactly what I need. May be will explore this feature. Not sure if they have a trial. Thanx and Regards, KR Kumar -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Port Assigned? Work on specific Node?

Hello! It is stopped because it is created in try-with-resources block. It is closed when try-block is exited. The equivalent code is IgnitePredicate lsnr = new IgnitePredicate() { public boolean apply(TaskEvent e) { ... } } Regards, -- Ilya Kasnacheev 2018-07-16 14:59 GMT+03:00

Re: Port Assigned? Work on specific Node?

thanks, I am looking for some features about ignite for my case and I am stuck with this code: Event Example Github Ignite In this example works fine, but why ignite node

RE: Deployment of Ignite/Application upgrades to production in 100+ nodecluster

The functionality you’re looking for is generally called Rolling Upgrade. Ignite doesn’t support clusters with mixed versions out of the box. There are third-party solutions on top of Ignite, such as GridGain, that do have that. Thanks, Stan From: KR Kumar Sent: 16 июля 2018 г. 12:44 To:

Re: Port Assigned? Work on specific Node?

Hello! setClientMode(true) is thick client. IgniteJdbcThinDriver is an example of thin client. Note that thin clients' functionality is limited compared to thick client. It is insufficient information about your use case to say which one suits your needs. Regards, -- Ilya Kasnacheev

Re: Port Assigned? Work on specific Node?

thanks, Q2) What is the difference between setClientMode(true) and thin client? I probably will embed the nodes(which is responsible for CRUD operation for users). Which one I should, thin client or client Node -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Port Assigned? Work on specific Node?

Hello! Q1) This is because you can have more than one client or server node per host, that will make use of port range. Moreover, you only have to discovery one node via broadcast, and it will reveal the information of all other nodes it knows, along with addressed. Q2) This is only possible

Deployment of Ignite/Application upgrades to production in 100+ node cluster

Hi - I have a 100 node cluster that is going to production in next 3 months. The problem I am trying to figure out is how do i handle version and application upgrades i.e when I am deploying the nodes in a sequence, I will reach a point where half of my nodes are in the old version and half in the

Re: Can't write to Ignite cluster

Ray, As I see from following logs: 18/07/13 01:33:18 WARN cache.GridCachePartitionExchangeManager: >>> GridDhtPartitionsExchangeFuture [topVer=AffinityTopologyVersion [topVer=25309, minorTopVer=0], evt=NODE_JOINED, evtNode=TcpDiscoveryNode [id=0caad476-3652-453f-8fc8-e8880c12eea9,

Re: Ignite AWS cluster setup

Hi, Could you please show the cluster configuration. 2018-07-13 17:56 GMT+03:00 Kia Rahmani : > Hello all, > I recently started using Ignite for benchmarking a research project on a > local multi-node cluster. Now I need to deploy the cluster on > geographically > distributed nodes, but I am

Port Assigned? Work on specific Node?

I have many question: - In local we have this line in config file: *bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">127.0.0.1:47500..47509* If I understood properly, our node sends a broadcast to message to other nodes which have address