hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nkeywal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7839) Add a script to simulate a dead machine during the integration tests
Date Fri, 15 Feb 2013 17:15:12 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579333#comment-13579333

nkeywal commented on HBASE-7839:

I don't press 'submit patch' because it's a pure C and shell script stuff, so I save Jenkins
resources, but 7839.v1.patch is what I would like to commit. So feedback is welcome :-).
As it's not critical but a little bit different from the usual patches, I will wait a few
days in any case.

> Add a script to simulate a dead machine during the integration tests
> --------------------------------------------------------------------
>                 Key: HBASE-7839
>                 URL: https://issues.apache.org/jira/browse/HBASE-7839
>             Project: HBase
>          Issue Type: New Feature
>          Components: test
>    Affects Versions: 0.96.0
>            Reporter: nkeywal
>            Assignee: nkeywal
>            Priority: Minor
>             Fix For: 0.96.0
>         Attachments: 7839.v1.patch
> A kill -9 cannot be used to simulate a dead box. With a kill -9:
> 1) the sockets are closed by the OS
> 2) the next calls will get immediately a connection refused.
> Physically unplugging the cable does work.
> To automate this, the best solution seems to be using a firewall config.
> It's a little bit complicated however, because we need to refuse the incoming packets.
If we block the out connection, it's detected by the OS and there is no wait on the socket.
> Moreover you need to be root, or use a program with a sticky bit to launch the script
that changes the firewall config.
> This will be usable from the integration tests.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message