RE: How to set JVM opts in the configuration xml

2018-07-06 Thread Cong Guo
Hi, Please ignore this email. I lost common sense. Sorry. From: Cong Guo Sent: 2018年7月6日 15:25 To: user@ignite.apache.org Subject: How to set JVM opts in the configuration xml Hi, I start the Ignite node in my own code instead of using ignite.sh. How do I set JVM opts in the configuration

Re: Continuous TCPDiscovery

2018-07-06 Thread Kristopher Kane
It seems that was not correct. I was attempting to use with TcpDiscoveryVmIpFinder with VM infra public IPs and Ignite was not liking that. Changing to internal host names allowed me to still connect to the cluster from a JDBC client. On Fri, Jul 6, 2018 at 11:44 AM, Kristopher Kane wrote: >

How to set JVM opts in the configuration xml

2018-07-06 Thread Cong Guo
Hi, I start the Ignite node in my own code instead of using ignite.sh. How do I set JVM opts in the configuration xml? Thanks, Cong

Apache Ignite with Caching : How do I sure that cache(s) has all datas?

2018-07-06 Thread monstereo
I'm looking for an answer this question. Here is the scenario - I have datas from the database over 100.000 - I have created cache node(node1) then, I have loaded 100.000 datas to the cache memory.(REPLICATED mode) - Now I will create another node(s) which is/are served for client to consume

Continuous TCPDiscovery

2018-07-06 Thread Kristopher Kane
Hi, Am I supposed to see continuous TCPDiscovery lines in the log? 'TCP discovery accepted incoming connection' ... 'Finished serving remote node connection' I guess I would suspect these to be at the DEBUG level and now assume I have a misconfiguration. -Kris

Re: Metrics for IgniteDataStreamer

2018-07-06 Thread Evgenii Zhuravlev
Hi, It's possible to set only one DataStreamer to the KafkaStreamer, So, I'd recommend using one KafkaStreamer per cache. Evgenii 2018-07-05 20:03 GMT+03:00 vbm : > HI Evangii, > > Thanks for the reply. I have some more question regarding ignite data > streamer. > > Below is our scenario: > We

Re: Performance acting as a redis server

2018-07-06 Thread Ilya Kasnacheev
Hello! Since Java is a garbage-collected language, you can expect that there will be some timeouts. You should really be targeting 99th while having reasonably large timeout. Regards, -- Ilya Kasnacheev 2018-07-06 11:44 GMT+03:00 胡海麟 : > Hi, > > Thank you for your advice. > > We are

Re: Performance acting as a redis server

2018-07-06 Thread 胡海麟
Hi, Thank you for your advice. We are checking if we can modify the connection part of the client. Meanwhile, we still have timeout issue on ignite. Our write timeout setting is 20ms, but timeout happens several times 1 minute. The workload is like "Atomic Put, Throughput 100 - 150 Ops/Sec".