Skip to main content

Using Amazon SQS for Out-Scaled Deployers

Image
By
When a Deployer Receiver receives a transport package, it notifies the Deployer Workers there is 'work' for them to do. This notification can take the form of JMS messages sent using some kinds of queuing mechanism. This post describes the Amazon Simple Queuing Service (SQS) to send these notifications. The Deployer workers receive these messages from SQS and they start deploying/undeploying the package.

In order to setup this notification system, we must first create the SQS queues and configure them across the Deployer Receiver and all Deployer Workers.

Start by creating Standard Queues using all default properties. We need 3 queues (commit, content, and prepare):



Once the SQS queues are in place, we can configure the Deployers to use them in the file deployer-config.xml. Amazon gives us the queues URLs. We need to specify the URL base separately, and then simply name the queues individually, as per below:

<Queues>
    <Queue Default="true" Verbs="Content" Adapter="JMS" Id="mihai-content">
        <Property Name="Workers" Value="16"/>
    </Queue>
    <Queue Verbs="Commit,Rollback" Adapter="JMS" Id="mihai-commit">
        <Property Name="Workers" Value="16"/>
    </Queue>
    <Queue Verbs="Prepare" Adapter="JMS" Id="mihai-prepare">
        <Property Name="Workers" Value="16"/>
    </Queue>

    <Adapter Id="JMS">
        <Property Name="JMSConnectionFactoryBuilderClass"
                  Value="com.sdl.delivery.spring.configuration.jms.AmazonSQSConnectionFactoryBuilder"/>
        <Property Name="JMSUri" Value="https://sqs.eu-west-1.amazonaws.com/692321"/>
        <Property Name="Username" Value="username"/>
        <Property Name="Password" Value="password"/>
        <Property Name="ReceiveTimeout" Value="200"/>
    </Adapter>
</Queues>

The properties Username and Password represent the AWS account credentials and they can be found in AWS user security settings.

The property Workers specifies the number of worker threads for each queue. Values that perform best are around 10-20 worker threads. Performance degrades using lower values and there isn't any significant performance gain when using higher values.



Labels:

Comments

Post a Comment

Popular posts from this blog

Running sp_updatestats on AWS RDS database

By
Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as
1 comment
Read more

Scaling Policies

By
This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the
Post a Comment
Read more

I Have Gone Dark

By Unknown
Maybe it's the Holidays, but my mood has gone pretty dark. That is, regarding the look and feel of my computer and Tridion CME, of course. What I did was to dim the lights on the operating system, so I installed Placebo themes for Windows 7 . I went for the Ashtray look -- great name :) My VM looks now like this: But, once you change the theme on Windows, you should 'match' the theme of your applications. Some skin easily, some not. The Office suite has an in-built scheme, which can be set to Black , but it doesn't actually dim the ribbon tool bars -- it looks quite weird. Yahoo Messenger is skinnable, but you can't change the big white panels where you actually 'chat'. Skype is not skinnable at all. For Chrome, there are plenty of grey themes. Now i'm using Pro Grey . But then I got into changing the theme of websites. While very few offer skinnable interfaces (as GMail does), I had to find a way to darken the websites... Enter Stylish -- a pl
4 comments
Read more