Prevent SVN locking and slow response between Talend Administration Center Subversion and Talend Studio

author
Irshad Burtally
EnrichVersion
6.5
EnrichProdName
Talend Data Fabric
Talend Big Data Platform
Talend Real-Time Big Data Platform
Talend Big Data
Talend MDM Platform
Talend Data Integration
Talend Data Services Platform
Talend Data Management Platform
Talend ESB
task
Installation and Upgrade
EnrichPlatform
Talend Studio
Talend Administration Center

Prevent SVN locking and slow response between Talend Administration Center, Subversion and Talend Studio

This article explains how to prevent Subversion (SVN) locking and slow response between Talend Administration Center, SVN and Talend Studio by performing the correct configuration for SVN in Talend Administration Center.

Symptoms

There can be several symptoms for this issue. It can manifest itself as a slow response, with a job taking several minutes to save, or as an SVN locking issue. Most of the time, you will find that Studio takes too long to save the jobs.

Resolution

The SVN configuration in Talend Administration Center has been enhanced since version 5.5.1. Two URLs are required, the Server Location URL and the Library Location URL. It is very important that the two locations are not identical and that two different SVN repositories are being used.

On Windows, you must set up two SVN repositories in VisualSVN and set up correct user permissions on both repositories.

Creating and configuring two SVN repositories

This section explains how to create and configure two different SVN repositories in CentOS.

In this article, CentOS is used as an example. You should find the equivalent instructions for the distribution of Linux that you use. For the complete instructions on how to set up SVN with Apache Httpd on CentOS, see Subversion on CentOS.

Procedure

  1. Use the following commands to create two SVN repositories.
    svnadmin create /var/www/talend_libs_562
    svnadmin create /var/www/talend_projects_562
  2. Expose these two repositories through Apache Httpd by editing the file /etc/httpd/conf.d/subversion.conf, and define two locations for the SVN repositories as follows.
    
                    # Make sure you uncomment the following if they are commented out
                    LoadModule dav_svn_module     modules/mod_dav_svn.so
                    LoadModule authz_svn_module   modules/mod_authz_svn.so
                    
                    # Add the following to allow a basic authentication and point Apache to where the actual
                    # repository resides.
                    <Location /talend_libs_562>
                        DAV svn
                        SVNPath /var/www/svn/talend_libs_562
                        AuthType Basic
                        AuthName "Subversion repos"
                        AuthUserFile /etc/svn-auth-conf
                        Require valid-user
                    </Location>
                    
                    <Location /talend_projects_562>
                        DAV svn
                        SVNPath /var/www/svn/talend_projects_562
                        AuthType Basic
                        AuthName "Subversion repos"
                        AuthUserFile /etc/svn-auth-conf
                        Require valid-user
                    </Location>
                

Configuring two SVN repositories in Talend Administration Center

This section explains how to configure the two repositories you created in Talend Administration Center.

The Server and Library URLs are used for different purposes and interact with the SVN repository for different events. In a multi-user environment, this quickly causes issues if both URLs point to the same location.

For more information, see the Talend Administration Center User Guide.

Procedure

  1. Configure the Talend Administration Center Library Location and Server Location URLs as follows, pointing to two different repositories.

    When you use the same SVN repository for both, it causes excessive I/O interactions, which leads to significantly slower response times because of SVN locks.

    When you change the Library Location URL, the first connection will be slower than the subsequent ones, because various JAR files will download to the local machine.

  2. Open any remote Talend project with Talend Studio for the first time.
    The Library repository is populated with the Talend required and optional third-party libraries.
  3. Accept the download and installation of the required and optional third-party libraries.

Downloading and installing the Library repository

This section explains how to download the Library repository if it is still empty after the previous procedure.

Procedure

  1. Restart Talend Administration Center.
  2. Make sure that the user defined in the Talend Administration Center Configuration page has access to this Library repository.
  3. Delete the following folders in Talend Studio:
    • <studio>\configuration\lib
    • <studio>\configuration\org.eclipse.core.runtime
    • <studio>\configuration\org.eclipse.equinox.app
    • <studio>\configuration\org.eclipse.osgi
    • <studio>\configuration\org.eclipse.update
  4. Start Talend Studio and configure the remote connection to use a new workspace, create the workspace folder if it does not exist.
  5. Open a remote project and install the Talend required and optional third-party libraries when prompted.
    If you are not prompted, click Help > Install Additional Packages and follow the wizard.