<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Manually triggering a scheduled job on slave instance in a clustered setup</title>
  <link rel="self" href="https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=122388707" />
  <subtitle>Manually triggering a scheduled job on slave instance in a clustered setup</subtitle>
  <id>https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=122388707</id>
  <updated>2026-04-04T14:58:50Z</updated>
  <dc:date>2026-04-04T14:58:50Z</dc:date>
  <entry>
    <title>RE: RE: Manually triggering a scheduled job on slave instance in a clustered setup</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122453994" />
    <author>
      <name>Michał Bączkowski</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122453994</id>
    <updated>2024-03-07T17:22:54Z</updated>
    <published>2024-03-07T09:55:33Z</published>
    <summary type="html">&lt;p&gt;Hi, do you have any timeline for this issue? I'm wondering if this
  could be fixed in Q1 this year, or perhaps do you have any alternative estimations?&lt;/p&gt;</summary>
    <dc:creator>Michał Bączkowski</dc:creator>
    <dc:date>2024-03-07T09:55:33Z</dc:date>
  </entry>
  <entry>
    <title>RE: Manually triggering a scheduled job on slave instance in a clustered setup</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122410616" />
    <author>
      <name>Jamie Sammons</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122410616</id>
    <updated>2024-02-20T19:23:26Z</updated>
    <published>2024-02-20T19:23:25Z</published>
    <summary type="html">&lt;p&gt;Hi, my apologizes but this one fell off my radar.  I have now created
  bug report: https://liferay.atlassian.net/browse/LPD-18251 in Jira. 
  Thanks for following up.&lt;/p&gt;</summary>
    <dc:creator>Jamie Sammons</dc:creator>
    <dc:date>2024-02-20T19:23:25Z</dc:date>
  </entry>
  <entry>
    <title>RE: Manually triggering a scheduled job on slave instance in a clustered setup</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122402601" />
    <author>
      <name>Michał Bączkowski</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122402601</id>
    <updated>2024-02-20T17:38:42Z</updated>
    <published>2024-02-16T09:01:55Z</published>
    <summary type="html">&lt;p&gt;Hello! Is there any update on the progress of this issue?&lt;/p&gt;</summary>
    <dc:creator>Michał Bączkowski</dc:creator>
    <dc:date>2024-02-16T09:01:55Z</dc:date>
  </entry>
  <entry>
    <title>Manually triggering a scheduled job on slave instance in a clustered setup</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122388706" />
    <author>
      <name>Michał Bączkowski</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122388706</id>
    <updated>2024-02-12T17:43:10Z</updated>
    <published>2024-02-08T15:10:20Z</published>
    <summary type="html">&lt;p&gt;When I go to the Job Scheduler in the admin panel and manually run a
  scheduled job the outcome is different depending on the instance in a
  clustered setup I'm connected to. If it's the master node the job
  triggers as expected, however if it's the slave node the page just
  reloads and the job doesn't actually run.&lt;/p&gt;
&lt;p&gt;I traced the problem to the ClusterSchedulerEngine - all the
  job-related methods have a @Clusterable annotation with some variation
  of parameters, there is one exception however - public void run(...).
  This method is responsible for actually running the job and I believe
  it should have the @Clusterable annotation as well. All the related
  methods (getScheduledJob, delete, pause, resume, schedule) are
  cluster-aware (through the annotation) and the run method is the only
  one that doesn't have any clustering-related logic despite all the
  other job-related methods having them. This seems like a simple
  omission and just adding the annotation should fix the issue. &lt;/p&gt;</summary>
    <dc:creator>Michał Bączkowski</dc:creator>
    <dc:date>2024-02-08T15:10:20Z</dc:date>
  </entry>
</feed>
