<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to ensure only one node runs the LDAP sync? in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/how-to-ensure-only-one-node-runs-the-ldap-sync/m-p/229396#M182526</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;&amp;gt; but we do want to avoid having these run in parallel.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Indeed the simplest way is disabling ldap sync on the other nodes&amp;nbsp; (using the ldap.synchronization.full.enabled and ldap.differential.full.enabled) properties on the other nodes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;However, if you can't distinguish nodes from each other … that's not going to work … I would indeed go for the route you suggest there: have something that all nodes can write to globally and to the 'selecting the master node' via that data. Could use the database for it … that will do the trick for sure or maybe something like Hazelcast. And then triggers the ldap sync bean when it becomes the master.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 26 May 2016 13:20:07 GMT</pubDate>
    <dc:creator>jbarrez</dc:creator>
    <dc:date>2016-05-26T13:20:07Z</dc:date>
    <item>
      <title>How to ensure only one node runs the LDAP sync?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/how-to-ensure-only-one-node-runs-the-ldap-sync/m-p/229395#M182525</link>
      <description>In our environment, all of our deployments are automated, and we at present have no way of distinguishing one node from another. We will probably find a way to do this, but it won't be completely failsafe.I ask this to see that we can have just one server run the LDAP sync. Testing in 1.4.2, we see</description>
      <pubDate>Wed, 18 May 2016 19:08:10 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/how-to-ensure-only-one-node-runs-the-ldap-sync/m-p/229395#M182525</guid>
      <dc:creator>jonnyg</dc:creator>
      <dc:date>2016-05-18T19:08:10Z</dc:date>
    </item>
    <item>
      <title>Re: How to ensure only one node runs the LDAP sync?</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/how-to-ensure-only-one-node-runs-the-ldap-sync/m-p/229396#M182526</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;&amp;gt; but we do want to avoid having these run in parallel.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Indeed the simplest way is disabling ldap sync on the other nodes&amp;nbsp; (using the ldap.synchronization.full.enabled and ldap.differential.full.enabled) properties on the other nodes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;However, if you can't distinguish nodes from each other … that's not going to work … I would indeed go for the route you suggest there: have something that all nodes can write to globally and to the 'selecting the master node' via that data. Could use the database for it … that will do the trick for sure or maybe something like Hazelcast. And then triggers the ldap sync bean when it becomes the master.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 May 2016 13:20:07 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/how-to-ensure-only-one-node-runs-the-ldap-sync/m-p/229396#M182526</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2016-05-26T13:20:07Z</dc:date>
    </item>
  </channel>
</rss>

