move comment about scheduling being reprocessed

Author: guzzijones

st2actions/st2actions/scheduler/handler.py

@@ -44,13 +44,6 @@
 
 LOG = logging.getLogger(__name__)
 
-# If an ActionExecutionSchedulingQueueItemDB object hasn't been updated fore more than this amount
-# of milliseconds, it will be marked as "handled=False".
-# As soon as an item is picked by scheduler to be processed, it should be processed very fast
-# (< 5 seconds). If an item is still being marked as processing it likely indicates that the
-# scheduler process which was processing that item crashed or similar so we need to mark it as
-# "handling=False" so some other scheduler process can pick it up.
-
 # When a policy delayed execution is detected it will be try to be rescheduled by the scheduler
 # again in this amount of milliseconds.
 POLICY_DELAYED_EXECUTION_RESCHEDULE_TIME_MS = 2500
@@ -61,6 +54,12 @@ def __init__(self):
         self.message_type = LiveActionDB
         self._shutdown = False
         self._pool = eventlet.GreenPool(size=cfg.CONF.scheduler.pool_size)
+        # If an ActionExecutionSchedulingQueueItemDB object hasn't been updated fore more than this amount
+        # of milliseconds, it will be marked as "handled=False".
+        # As soon as an item is picked by scheduler to be processed, it should be processed very fast
+        # (< 5 seconds). If an item is still being marked as processing it likely indicates that the
+        # scheduler process which was processing that item crashed or similar so we need to mark it as
+        # "handling=False" so some other scheduler process can pick it up.
         self._execution_scheduling_timeout_threshold_ms = \
                 cfg.CONF.scheduler.execution_scheduling_timeout_threshold_min \
                 * 60 * 1000