Ryfujk

Why are vacuum tubes still used in amateur radios?

Why not send Voyager 3 and 4 following up the paths taken by Voyager 1 and 2 to re-transmit signals of later as they fly away from Earth?

New Order #6: Easter Egg

Does the Black Tentacles spell do damage twice at the start of turn to an already restrained creature?

How to write capital alpha?

Is openssl rand command cryptographically secure?

License to disallow distribution in closed source software, but allow exceptions made by owner?

AppleTVs create a chatty alternate WiFi network

What would you call this weird metallic apparatus that allows you to lift people?

I can't produce songs

What order were files/directories output in dir?

Is multiple magic items in one inherently imbalanced?

How can I prevent/balance waiting and turtling as a response to cooldown mechanics

My mentor says to set image to Fine instead of RAW — how is this different from JPG?

A proverb that is used to imply that you have unexpectedly faced a big problem

Test print coming out spongy

Monty Hall Problem-Probability Paradox

Central Vacuuming: Is it worth it, and how does it compare to normal vacuuming?

Moving a wrapfig vertically to encroach partially on a subsection title

Tannaka duality for semisimple groups

Co-worker has annoying ringtone

Would color changing eyes affect vision?

Is there hard evidence that the grant peer review system performs significantly better than random?

Should a wizard buy fine inks every time he want to copy spells into his spellbook?

Timeouts while trying to connect to DynamoDB endpoint

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}

4

We were performing a test deployment of an application, that utilizes DynamoDB for persistency. A number of tables was created in the us-east region. Then we ran some tests against the application, that resulted in a significant number of writes and reads of those tables, exceeding the throughput thresholds. All of a sudden, though, the requests to the DynamoDB stopped coming through at all from that particular machine. We recreated the tables in the eu-west region and ran the tests again. It worked for some time, but in the morning it was discovered, that the same thing happened to the eu-west installation, but at the same time, the requests against the us-west one started coming through.

There's more, after a bit of investigation, it was discovered, that if, at the time, when all requests against some region failed, we could not even open a connection to the DynamoDB endpoint for that region (basically, "wget https://dynamodb.us-west-1.amazonaws.com" failed with a timeout).

Even more, at the time, when we could not connect to a particular DynamoDB endpoint, all other machines could do that just fine. Even the ones, that were in the same subnet with the affected machine and behind the same NAT (therefore, sharing its source IP address!).

All the machines, that I am talking about are actually EC2 instances so there's no real hardware involved on our side.

Any idea, what could be wrong?

We didn't touch the network configuration for the duration of the tests. Could it be some form of throttling that we were experiencing?

amazon-ec2 amazon-dynamodb

share|improve this question

edited Jul 23 '12 at 5:23

shylent

asked Jul 20 '12 at 19:25

shylentshylent

669920

bumped to the homepage by Community♦ 9 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

add a comment | 

4

We were performing a test deployment of an application, that utilizes DynamoDB for persistency. A number of tables was created in the us-east region. Then we ran some tests against the application, that resulted in a significant number of writes and reads of those tables, exceeding the throughput thresholds. All of a sudden, though, the requests to the DynamoDB stopped coming through at all from that particular machine. We recreated the tables in the eu-west region and ran the tests again. It worked for some time, but in the morning it was discovered, that the same thing happened to the eu-west installation, but at the same time, the requests against the us-west one started coming through.

There's more, after a bit of investigation, it was discovered, that if, at the time, when all requests against some region failed, we could not even open a connection to the DynamoDB endpoint for that region (basically, "wget https://dynamodb.us-west-1.amazonaws.com" failed with a timeout).

Even more, at the time, when we could not connect to a particular DynamoDB endpoint, all other machines could do that just fine. Even the ones, that were in the same subnet with the affected machine and behind the same NAT (therefore, sharing its source IP address!).

All the machines, that I am talking about are actually EC2 instances so there's no real hardware involved on our side.

Any idea, what could be wrong?

We didn't touch the network configuration for the duration of the tests. Could it be some form of throttling that we were experiencing?

amazon-ec2 amazon-dynamodb

share|improve this question

edited Jul 23 '12 at 5:23

shylent

asked Jul 20 '12 at 19:25

shylentshylent

669920

bumped to the homepage by Community♦ 9 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

add a comment | 

We were performing a test deployment of an application, that utilizes DynamoDB for persistency. A number of tables was created in the us-east region. Then we ran some tests against the application, that resulted in a significant number of writes and reads of those tables, exceeding the throughput thresholds. All of a sudden, though, the requests to the DynamoDB stopped coming through at all from that particular machine. We recreated the tables in the eu-west region and ran the tests again. It worked for some time, but in the morning it was discovered, that the same thing happened to the eu-west installation, but at the same time, the requests against the us-west one started coming through.

There's more, after a bit of investigation, it was discovered, that if, at the time, when all requests against some region failed, we could not even open a connection to the DynamoDB endpoint for that region (basically, "wget https://dynamodb.us-west-1.amazonaws.com" failed with a timeout).

Even more, at the time, when we could not connect to a particular DynamoDB endpoint, all other machines could do that just fine. Even the ones, that were in the same subnet with the affected machine and behind the same NAT (therefore, sharing its source IP address!).

All the machines, that I am talking about are actually EC2 instances so there's no real hardware involved on our side.

Any idea, what could be wrong?

We didn't touch the network configuration for the duration of the tests. Could it be some form of throttling that we were experiencing?

amazon-ec2 amazon-dynamodb

share|improve this question

edited Jul 23 '12 at 5:23

shylent

asked Jul 20 '12 at 19:25

shylentshylent

669920

share|improve this question

edited Jul 23 '12 at 5:23

shylent

asked Jul 20 '12 at 19:25

shylentshylent

669920

share|improve this question

edited Jul 23 '12 at 5:23

shylent

asked Jul 20 '12 at 19:25

shylentshylent

669920

asked Jul 20 '12 at 19:25

shylentshylent

669920

asked Jul 20 '12 at 19:25

shylentshylent

669920

2 Answers
2

active

oldest

votes

0

Have you tried rebooting your router? The fact that some of the servers behind your NAT gateway work, but others do not leave me to believe that the problem is on your end, not Amazon's.

If it's a consumer grade device, try updating the firmware. What brand/model is it?

share|improve this answer

answered Jul 22 '12 at 23:21

jamiebjamieb

2,82941934

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  All of the machines (including the one, where NAT is performed) are EC2 instances, so there's no "device" to reboot or update the firmware on.
  
  – shylent
  Jul 23 '12 at 3:25
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  When DynamoDB throttles, it returns HTTP 400 errors, it doesn't just drop packets. How reliability are you able to reproduce the problem?
  
  – jamieb
  Jul 23 '12 at 23:39
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Very reliably indeed. I've just made a couple hundred requests against the eu-west-1 endpoint and, there it is - I am timing out while trying to connect to it from that machine.
  
  – shylent
  Jul 24 '12 at 6:53
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Have you taken a look at your CloudWatch metrics for DyanmoDB? Are you running into the limits of your provisioned capacity? Also, what library/SDK are you using to connect to DynamoDB?
  
  – jamieb
  Jul 25 '12 at 14:59
  

  
  
  
  

add a comment | 

0

Have you checked the read/write capacity of your Dynamodb tables. Every table has read/write capacity associated with it. If you reach max capacity, it stops receiving connection. Also there is limit for updating these read/write of Dynamodb in one day. Check that as well. I hope this helps.

share|improve this answer

answered Jul 24 '17 at 3:35

Shailesh SutarShailesh Sutar

65021029

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f409747%2ftimeouts-while-trying-to-connect-to-dynamodb-endpoint%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

Have you tried rebooting your router? The fact that some of the servers behind your NAT gateway work, but others do not leave me to believe that the problem is on your end, not Amazon's.

If it's a consumer grade device, try updating the firmware. What brand/model is it?

share|improve this answer

answered Jul 22 '12 at 23:21

jamiebjamieb

2,82941934

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  All of the machines (including the one, where NAT is performed) are EC2 instances, so there's no "device" to reboot or update the firmware on.
  
  – shylent
  Jul 23 '12 at 3:25
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  When DynamoDB throttles, it returns HTTP 400 errors, it doesn't just drop packets. How reliability are you able to reproduce the problem?
  
  – jamieb
  Jul 23 '12 at 23:39
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Very reliably indeed. I've just made a couple hundred requests against the eu-west-1 endpoint and, there it is - I am timing out while trying to connect to it from that machine.
  
  – shylent
  Jul 24 '12 at 6:53
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Have you taken a look at your CloudWatch metrics for DyanmoDB? Are you running into the limits of your provisioned capacity? Also, what library/SDK are you using to connect to DynamoDB?
  
  – jamieb
  Jul 25 '12 at 14:59
  

  
  
  
  

add a comment | 

0

Have you tried rebooting your router? The fact that some of the servers behind your NAT gateway work, but others do not leave me to believe that the problem is on your end, not Amazon's.

If it's a consumer grade device, try updating the firmware. What brand/model is it?

share|improve this answer

answered Jul 22 '12 at 23:21

jamiebjamieb

2,82941934

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  All of the machines (including the one, where NAT is performed) are EC2 instances, so there's no "device" to reboot or update the firmware on.
  
  – shylent
  Jul 23 '12 at 3:25
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  When DynamoDB throttles, it returns HTTP 400 errors, it doesn't just drop packets. How reliability are you able to reproduce the problem?
  
  – jamieb
  Jul 23 '12 at 23:39
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Very reliably indeed. I've just made a couple hundred requests against the eu-west-1 endpoint and, there it is - I am timing out while trying to connect to it from that machine.
  
  – shylent
  Jul 24 '12 at 6:53
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Have you taken a look at your CloudWatch metrics for DyanmoDB? Are you running into the limits of your provisioned capacity? Also, what library/SDK are you using to connect to DynamoDB?
  
  – jamieb
  Jul 25 '12 at 14:59
  

  
  
  
  

add a comment | 

Have you tried rebooting your router? The fact that some of the servers behind your NAT gateway work, but others do not leave me to believe that the problem is on your end, not Amazon's.

If it's a consumer grade device, try updating the firmware. What brand/model is it?

share|improve this answer

answered Jul 22 '12 at 23:21

jamiebjamieb

2,82941934

share|improve this answer

answered Jul 22 '12 at 23:21

jamiebjamieb

2,82941934

answered Jul 22 '12 at 23:21

jamiebjamieb

2,82941934

answered Jul 22 '12 at 23:21

jamiebjamieb

2,82941934

0

Have you checked the read/write capacity of your Dynamodb tables. Every table has read/write capacity associated with it. If you reach max capacity, it stops receiving connection. Also there is limit for updating these read/write of Dynamodb in one day. Check that as well. I hope this helps.

share|improve this answer

answered Jul 24 '17 at 3:35

Shailesh SutarShailesh Sutar

65021029

add a comment | 

0

Have you checked the read/write capacity of your Dynamodb tables. Every table has read/write capacity associated with it. If you reach max capacity, it stops receiving connection. Also there is limit for updating these read/write of Dynamodb in one day. Check that as well. I hope this helps.

share|improve this answer

answered Jul 24 '17 at 3:35

Shailesh SutarShailesh Sutar

65021029

add a comment | 

Have you checked the read/write capacity of your Dynamodb tables. Every table has read/write capacity associated with it. If you reach max capacity, it stops receiving connection. Also there is limit for updating these read/write of Dynamodb in one day. Check that as well. I hope this helps.

share|improve this answer

answered Jul 24 '17 at 3:35

Shailesh SutarShailesh Sutar

65021029

share|improve this answer

answered Jul 24 '17 at 3:35

Shailesh SutarShailesh Sutar

65021029

answered Jul 24 '17 at 3:35

Shailesh SutarShailesh Sutar

65021029

answered Jul 24 '17 at 3:35

Shailesh SutarShailesh Sutar

65021029