<?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 Batch uploading and attaching a document fails in a clustered configuration -- how can it be fixed? in Nuxeo Forum</title>
    <link>https://connect.hyland.com/t5/nuxeo-forum/batch-uploading-and-attaching-a-document-fails-in-a-clustered/m-p/320691#M7692</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I have been following the &lt;A href="http://doc.nuxeo.com/display/NXDOC/Blob+Upload+for+Batch+Processing"&gt;"Blob Upload for Batch Processing"&lt;/A&gt; directions with some success in development, but I have run into a very severe problem when attempting to use it in a production configuration in a two-node cluster.&lt;/P&gt;
&lt;P&gt;I believe the root of the problem is described in that documentation. "The files attached to the batch are stored on a temporary disk storage (inside java.io.tmp) until the batch is executed or dropped." -- this means that batch-uploaded files are only available on the original node. So given the following configuration:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;nuxeo-lb.example.com load balancer&lt;/LI&gt;
&lt;LI&gt;nuxeo-a.example.com node A&lt;/LI&gt;
&lt;LI&gt;nuxeo-b.example.com node B&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;If one uses nuxeo-lb.example.com to access the batch processing and document modification API as documented, then one is quite likely to upload the file to node-a.example.com and attempt to use it from node-b.example.com, which results in an error because node-b.example.com does not have access to that file.&lt;/P&gt;
&lt;P&gt;As a temporary workaround we can directly use the nuxeo-a.example.com address for everything, but this is certainly not an ideal solution. What else can we do? We are using S3 binary storage on an EC2 instance, so sharing a directory isn't quite as straightforward as a shared NFS mount, and it's not even clear that &lt;STRONG&gt;java.io.tmp&lt;/STRONG&gt; should be shared anyway.&lt;/P&gt;</description>
    <pubDate>Wed, 03 Dec 2014 20:14:36 GMT</pubDate>
    <dc:creator>Steven_Huwig1</dc:creator>
    <dc:date>2014-12-03T20:14:36Z</dc:date>
    <item>
      <title>Batch uploading and attaching a document fails in a clustered configuration -- how can it be fixed?</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/batch-uploading-and-attaching-a-document-fails-in-a-clustered/m-p/320691#M7692</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I have been following the &lt;A href="http://doc.nuxeo.com/display/NXDOC/Blob+Upload+for+Batch+Processing"&gt;"Blob Upload for Batch Processing"&lt;/A&gt; directions with some success in development, but I have run into a very severe problem when attempting to use it in a production configuration in a two-node cluster.&lt;/P&gt;
&lt;P&gt;I believe the root of the problem is described in that documentation. "The files attached to the batch are stored on a temporary disk storage (inside java.io.tmp) until the batch is executed or dropped." -- this means that batch-uploaded files are only available on the original node. So given the following configuration:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;nuxeo-lb.example.com load balancer&lt;/LI&gt;
&lt;LI&gt;nuxeo-a.example.com node A&lt;/LI&gt;
&lt;LI&gt;nuxeo-b.example.com node B&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;If one uses nuxeo-lb.example.com to access the batch processing and document modification API as documented, then one is quite likely to upload the file to node-a.example.com and attempt to use it from node-b.example.com, which results in an error because node-b.example.com does not have access to that file.&lt;/P&gt;
&lt;P&gt;As a temporary workaround we can directly use the nuxeo-a.example.com address for everything, but this is certainly not an ideal solution. What else can we do? We are using S3 binary storage on an EC2 instance, so sharing a directory isn't quite as straightforward as a shared NFS mount, and it's not even clear that &lt;STRONG&gt;java.io.tmp&lt;/STRONG&gt; should be shared anyway.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Dec 2014 20:14:36 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/batch-uploading-and-attaching-a-document-fails-in-a-clustered/m-p/320691#M7692</guid>
      <dc:creator>Steven_Huwig1</dc:creator>
      <dc:date>2014-12-03T20:14:36Z</dc:date>
    </item>
    <item>
      <title>Re: Batch uploading and attaching a document fails in a clustered configuration -- how can it be fixed?</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/batch-uploading-and-attaching-a-document-fails-in-a-clustered/m-p/320692#M7693</link>
      <description>&lt;P&gt;Have you set up session affinity at the load balancer level? If you're not using a session cookie for these uploads, maybe you can add a custom header and do affinity on that?&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2014 11:39:16 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/batch-uploading-and-attaching-a-document-fails-in-a-clustered/m-p/320692#M7693</guid>
      <dc:creator>Florent_Guillau</dc:creator>
      <dc:date>2014-12-04T11:39:16Z</dc:date>
    </item>
    <item>
      <title>Re: Batch uploading and attaching a document fails in a clustered configuration -- how can it be fixed?</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/batch-uploading-and-attaching-a-document-fails-in-a-clustered/m-p/320693#M7694</link>
      <description>&lt;P&gt;We have the load balancer set up for user logins, but this is a sessionless direct call to the REST API. We are considering just using IP affinity for the time being unless there is a better way.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2014 14:37:10 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/batch-uploading-and-attaching-a-document-fails-in-a-clustered/m-p/320693#M7694</guid>
      <dc:creator>Steven_Huwig1</dc:creator>
      <dc:date>2014-12-04T14:37:10Z</dc:date>
    </item>
  </channel>
</rss>

