You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sergio Peña (JIRA)" <ji...@apache.org> on 2016/11/01 15:56:58 UTC
[jira] [Updated] (HIVE-15102) Hiveptest is killing nodes where IP
is reused after previous node termination
[ https://issues.apache.org/jira/browse/HIVE-15102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergio Peña updated HIVE-15102:
-------------------------------
Description:
NO PRECOMMIT TESTS
The Hiveptest framework has a background thread that runs every hour, and attempts to kill zombie nodes that are not being used by the test execution anymore.
These killed nodes are kept in a list of terminated nodes, and next time the background thread is executed, it will attempt to kill all those nodes again because Hiveptest consider them as zombie nodes.
The problem is that cloud providers can give you the same IP numbers for new nodes, and when the background thread runs, it will kill those nodes that may still be in used by Hiveptest.
was:
The Hiveptest framework has a background thread that runs every hour, and attempts to kill zombie nodes that are not being used by the test execution anymore.
These killed nodes are kept in a list of terminated nodes, and next time the background thread is executed, it will attempt to kill all those nodes again because Hiveptest consider them as zombie nodes.
The problem is that cloud providers can give you the same IP numbers for new nodes, and when the background thread runs, it will kill those nodes that may still be in used by Hiveptest.
> Hiveptest is killing nodes where IP is reused after previous node termination
> -----------------------------------------------------------------------------
>
> Key: HIVE-15102
> URL: https://issues.apache.org/jira/browse/HIVE-15102
> Project: Hive
> Issue Type: Bug
> Components: Hive
> Affects Versions: 2.2.0
> Reporter: Sergio Peña
> Assignee: Sergio Peña
>
> NO PRECOMMIT TESTS
> The Hiveptest framework has a background thread that runs every hour, and attempts to kill zombie nodes that are not being used by the test execution anymore.
> These killed nodes are kept in a list of terminated nodes, and next time the background thread is executed, it will attempt to kill all those nodes again because Hiveptest consider them as zombie nodes.
> The problem is that cloud providers can give you the same IP numbers for new nodes, and when the background thread runs, it will kill those nodes that may still be in used by Hiveptest.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)