From 79b10f8c0df9bf0b37742c3f572c9223a55ea763 Mon Sep 17 00:00:00 2001
From: Martijn van Groningen <martijn.v.groningen@gmail.com>
Date: Thu, 20 Nov 2014 11:32:54 +0100
Subject: [PATCH] Don't let Quartz check for updates.

Original commit: elastic/x-pack-elasticsearch@dd1e4c2577e484e9793c18182f34f72dff525802
---
 .../java/org/elasticsearch/alerts/scheduler/AlertScheduler.java  | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/main/java/org/elasticsearch/alerts/scheduler/AlertScheduler.java b/src/main/java/org/elasticsearch/alerts/scheduler/AlertScheduler.java
index bcc909a4745..2d1f1543e5f 100644
--- a/src/main/java/org/elasticsearch/alerts/scheduler/AlertScheduler.java
+++ b/src/main/java/org/elasticsearch/alerts/scheduler/AlertScheduler.java
@@ -52,6 +52,7 @@ public class AlertScheduler extends AbstractComponent {
             // Can't start a scheduler that has been shutdown, so we need to re-create each time start() is invoked
             Properties properties = new Properties();
             properties.setProperty("org.quartz.threadPool.class", AlertQuartzThreadPool.class.getName());
+            properties.setProperty(StdSchedulerFactory.PROP_SCHED_SKIP_UPDATE_CHECK, "true");
             SchedulerFactory schFactory = new StdSchedulerFactory(properties);
             scheduler = schFactory.getScheduler();
             scheduler.setJobFactory(new SimpleJobFactory());