Gemini Scheduler 3.6 with Gemini 3.5?
We are having significant issues with Gemini Scheduler 3.5. Every 2 - 3 days we have to restart the service, and some days we start getting the same notifications over and over again and the record in the database does not get deleted.
Two questions:
1.) Is Scheduler 3.6 more reliable?
2.) Can we use Scheduler 3.6 with Gemini 3.5?
Thanks.
mmatos
· 1 |
|
Thursday, February 4, 2010, 5:36:53 PM |
0
|
You should upgrade to 3.6.3 as it should be better and solve your issue. Note that it will need the web app to be 3.6.3 as well. |
||||
|
0
|
Alright, after hours of researching and debugging, I figured out the issue. The scheduler service is just not very efficient at batching emails when there are thousands of users, dozens of projects, and dozens of watchers on a variety of projects.
Anyway, it turns out that it takes something like 2 minutes and 10MB of data to send out the alerts on ONE ticket on a project that has many watchers. We get 5-10 tickets a minute during the busy time of our day. Upgrading our production system to 3.6 at this time is not an option, but after installing a test version of 3.6 and migrating the data and analyzing the traffic, I don't really see any improvement. I don't understand why the service needs to pull the same issue's data over and over and over again for one alert. I don't see any good options to resolve this: 1.) Disable users from watching a project (bad idea). 2.) Disable Scheduler and use MailPlugin (spammy) 3.) Pay someone to create a more efficient scheduler (expensive) 4.) Bug reports, wait for new release, then upgrade our system 5.) ??? Any ideas? |
||||
|
0
|
This is becoming very frustrating. |
||||
|
0
|
...and it turns out it was a configuration issue. We had WATCHER alerts disabled, so all users were subscribing to project level alerts to get their notifications and Scheduler was having to do a lot of work to figure out who to email. We mistakenly believed that WATCHER alerts would send a notification when a watcher was added or removed, not that it enabled alerts for watchers. The Gemini documentation is not clear about this. |
||||
|
0
|
Thanks for the update, glad all is well now. We will revise our docs. |
||||
|
0
|
Okay, now that we're back to high volume I'm still seeing issues. It's getting pretty slow in processing notifications, and I'm noticing that there always seem to be 2 scheduler processes running. Is this normal? |
||||
|
0
|
If you have more than 2 instances running (2 is ok) then it means that the interval is too low (too fast). Set it to 2 as a minimum but 5 minutes should do the trick. If this doesn't help let us know. |
||||
|