Hi forum,
An alert register for "-cc=gt2", so that alert should be trigger when "cc"
(total number of available CPUs in the grid" is "gt" (greater than) 2.
However, I found alert keep trigger when "cc" become 1, here's the log
showing a cluster of 3 nodes/CPUs, alert still triggerd after removing
the alert was registered by "alert -r -t=15 -cc=gt2"
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/visor-keep-trigger-alert-when-condition-no-longer-satisfied-tp3772p3773.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Thanks Vasiliy, problem solved.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/How-to-setup-alert-recipients-in-visor-cli-tp3732p3775.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Thank Vasiliy, but I still got the same kind of error with it, have try both
signle quote and double quote:
# bin/ignitevisorcmd.sh -e='open -cpath=config/test-one.xml;cache'
OpenJDK Server VM warning: ignoring option MaxPermSize=128M; support was
removed in 8.0
___
thanks Vasiliy for the hint, finally got this right, found quotes within
quotes work, both of these seems to work fine:
bin/ignitevisorcmd.sh -e="'open -cpath=config/test-one.xml;cache'"
bin/ignitevisorcmd.sh -e='"open -cpath=config/test-one.xml;cache"'
f.e.:
# bin/ignitevisorcmd.sh
thanks Vasiliy!!
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/visor-keep-trigger-alert-when-condition-no-longer-satisfied-tp3772p4114.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
I have an Ignite (1.5.0.final) cache client node started in a Tomcat 8.0.32,
the client node connects to a server node started on the same machine.
Sometimes the get() need some 5 seconds, while most of the other get() need
almost no time.
I wonder how the 5 seconds was spent, how I can troublesho
thanks dsetrakyan,
Why use System.out.println()?
I have added the System.out.println(), and keep the log.info() just for
comparison:
log.info("### Before get()");
System.out.println("##~ Before get()");
Vendor vendor = cache.get(vendorCode);
After done some more testings, I have these findings so far:
- The slow get() symptom only found when the client node and the server node
are started on the SAME machine, I cannot reproduce the symptom when client
node and server node were started on their own machines.
- The symptom seems to occ
Thanks yakov,
I am using a Linux box.
The delay can also be observed after leaving client idle for some 3 to 10
minutes.
I will try disabling the shared memory communication, Thanks!
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/How-to-troubleshoot-a-slow-clie
sorry for late reply, really busy last week
can reproduce the read delay with a standalone program now, and use
System.out.println() to time the cache read:
public class App {
public static void main(String[] args) {
App app = new App();
app.run();
Thanks Yakov and sorry for late reply.
I tried to disable the shared memory communication and it seems working fine
so far:
public class App {
public static void main(String[] args) {
System.out.println("ver 0719-1933");
App app = new App();
I found the Ignition.start() seems to wait forever when it cannot find any
node to join,
the program waiting over 10 mins and the message "IP finder returned empty
addresses list. Please check IP finder configuration and make sure multicast
works on your network. Will retry every 2 secs." shows eve
Hi, i just face a similar problem.
have 2 Ignite 1.6 setup but failed to forma a cluster with the following
iptables:
# iptables-save
# Generated by iptables-save v1.4.21 on Wed Oct 19 11:45:31 2016
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [5:776]
-A
Hi,
I found in visor command line interface one can register alerts, but how can
I set the alert recipients?
thanks in advance!
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/How-to-setup-alert-recipients-in-visor-cli-tp3732.html
Sent from the Apache Ignite Us
Hi,
I am trying to write some script with the visor cli,
my first attempt is to connect visor to a cluster with a custom config, then
do a "cache" command
Visor seems don't allow both -cfg and -e:
# bin/ignitevisorcmd.sh -cfg=config/test-one.xml -e=cache
OpenJDK Server VM warning: ignori
16 matches
Mail list logo