You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Animesh Chaturvedi (JIRA)" <ji...@apache.org> on 2013/10/21 23:46:23 UTC

[jira] [Updated] (CLOUDSTACK-3211) Object_Store_Refactor - S3 GUI timeout units are unclear

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Animesh Chaturvedi updated CLOUDSTACK-3211:
-------------------------------------------


ACS 4.3,0 feature freeze is Nov 8th. I will cut the 4.3 branch from master on that day. Please provide an update on your issue as a comment. 

> Object_Store_Refactor - S3 GUI timeout units are unclear
> --------------------------------------------------------
>
>                 Key: CLOUDSTACK-3211
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3211
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>         Environment: devcloud
> Cloudian or AWS S3 services.
>            Reporter: Thomas O'Dowd
>            Assignee: Thomas O'Dowd
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Connection Timeout:
> Socket Timeout:
> The units for these are unclear. I assumed they were seconds but now I think they might be milliseconds. 
> When I added S3 secondary storage to a local Cloudian S3 server, I was setting 60 for the connection timeout and it was ok. However, when I set 60 for the same timeout when adding the S3 server, I could never manage to upload a template. So I suspect that the connection was taking longer to setup. No errors are logged which is another problem but when I changed the timeouts to 60000, I could finally get a template uploaded to AWS.
> The gui should be clear regarding the units and provide help if possible.



--
This message was sent by Atlassian JIRA
(v6.1#6144)