You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Thiruvalluvan M. G. (JIRA)" <ji...@apache.org> on 2010/09/10 10:22:33 UTC
[jira] Created: (AVRO-664) Ruby server takes a long time to start
in interop tests
Ruby server takes a long time to start in interop tests
-------------------------------------------------------
Key: AVRO-664
URL: https://issues.apache.org/jira/browse/AVRO-664
Project: Avro
Issue Type: Bug
Components: ruby
Affects Versions: 1.4.0
Environment: Ubuntu Lucid Lynx
Reporter: Thiruvalluvan M. G.
Assignee: Thiruvalluvan M. G.
Fix For: 1.4.1
The ruby server uses a wrong key in the config (:Host instead of :BindAddress) which cause Socket::getaddrinfo() take up to 15 seconds. The shell script which starts the server waits for jist 1 second and test fails abruptly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AVRO-664) Ruby server takes a long time to start
in interop tests
Posted by "Thiruvalluvan M. G. (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thiruvalluvan M. G. updated AVRO-664:
-------------------------------------
Attachment: AVRO-664.patch
The patch addresses both the problems.
It fixes the name in tools.rb and makes the shell script wait for variable amount of time (up to 60 seconds). Either of the fixes is actually sufficient. But I thought an extra level of protection will not hurt.
> Ruby server takes a long time to start in interop tests
> -------------------------------------------------------
>
> Key: AVRO-664
> URL: https://issues.apache.org/jira/browse/AVRO-664
> Project: Avro
> Issue Type: Bug
> Components: ruby
> Affects Versions: 1.4.0
> Environment: Ubuntu Lucid Lynx
> Reporter: Thiruvalluvan M. G.
> Assignee: Thiruvalluvan M. G.
> Fix For: 1.4.1
>
> Attachments: AVRO-664.patch
>
>
> The ruby server uses a wrong key in the config (:Host instead of :BindAddress) which cause Socket::getaddrinfo() take up to 15 seconds. The shell script which starts the server waits for jist 1 second and test fails abruptly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AVRO-664) Ruby server takes a long time to start
in interop tests
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908917#action_12908917 ]
Doug Cutting commented on AVRO-664:
-----------------------------------
+1
I slightly prefer the ruby change alone, since it keeps the test script simpler and may help to identify other future such issues, but, on the other hand, if we leave the test script alone it may sometimes fail spuriously.
> Ruby server takes a long time to start in interop tests
> -------------------------------------------------------
>
> Key: AVRO-664
> URL: https://issues.apache.org/jira/browse/AVRO-664
> Project: Avro
> Issue Type: Bug
> Components: ruby
> Affects Versions: 1.4.0
> Environment: Ubuntu Lucid Lynx
> Reporter: Thiruvalluvan M. G.
> Assignee: Thiruvalluvan M. G.
> Fix For: 1.4.1
>
> Attachments: AVRO-664.patch
>
>
> The ruby server uses a wrong key in the config (:Host instead of :BindAddress) which cause Socket::getaddrinfo() take up to 15 seconds. The shell script which starts the server waits for jist 1 second and test fails abruptly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AVRO-664) Ruby server takes a long time to start
in interop tests
Posted by "Thiruvalluvan M. G. (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thiruvalluvan M. G. resolved AVRO-664.
--------------------------------------
Resolution: Fixed
Committed revision 996877.
> Ruby server takes a long time to start in interop tests
> -------------------------------------------------------
>
> Key: AVRO-664
> URL: https://issues.apache.org/jira/browse/AVRO-664
> Project: Avro
> Issue Type: Bug
> Components: ruby
> Affects Versions: 1.4.0
> Environment: Ubuntu Lucid Lynx
> Reporter: Thiruvalluvan M. G.
> Assignee: Thiruvalluvan M. G.
> Fix For: 1.4.1
>
> Attachments: AVRO-664.patch
>
>
> The ruby server uses a wrong key in the config (:Host instead of :BindAddress) which cause Socket::getaddrinfo() take up to 15 seconds. The shell script which starts the server waits for jist 1 second and test fails abruptly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (AVRO-664) Ruby server takes a long
time to start in interop tests
Posted by "Thiruvalluvan M. G. (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909220#action_12909220 ]
Thiruvalluvan M. G. edited comment on AVRO-664 at 9/14/10 11:31 AM:
--------------------------------------------------------------------
Thanks Doug for reviewing the patch.
Increasing from 1 second time-out previously to 60 seconds in the patch appears too excessive. As Doug pointed out some serious problems may go unnoticed. I set the limit to 10 seconds in steps of 1-second and then committed revision 996877.
was (Author: thiru_mg):
Committed revision 996877.
> Ruby server takes a long time to start in interop tests
> -------------------------------------------------------
>
> Key: AVRO-664
> URL: https://issues.apache.org/jira/browse/AVRO-664
> Project: Avro
> Issue Type: Bug
> Components: ruby
> Affects Versions: 1.4.0
> Environment: Ubuntu Lucid Lynx
> Reporter: Thiruvalluvan M. G.
> Assignee: Thiruvalluvan M. G.
> Fix For: 1.4.1
>
> Attachments: AVRO-664.patch
>
>
> The ruby server uses a wrong key in the config (:Host instead of :BindAddress) which cause Socket::getaddrinfo() take up to 15 seconds. The shell script which starts the server waits for jist 1 second and test fails abruptly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.