| Author |
Message |
|
|
Hi,
The systems are syncronized via NTP..
cluster-checkin iterval = 20000
Plz comment if this value is advisable..
|
 |
|
|
Hi all,
This seems to be a common warning..But can someone explain whats the root cause..
What are the implications of it..
This happens many times when a new node is added to the cluster or suddenly these warning start to appear on a existing node
|
 |
|
|
Hi,
Im using clustering of 2 quartz nodes..
Few days after continuous quartz running it was observed that a TRIGGER went into ACQUIRED state and refused to trigger.
I manually changed the state to WAITING..
Could someone plz explain why does this happen??
Also plz provide me good resources on quartz clustering and fine tuning the same..
I am using quartz version 1.7.1
Is this a issue with the version??
We will upgrade to latest quartz..but would take sometime..
Plz comment If this is issue is versionspecific..
|
 |
|
|