You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Sahil Takiar (JIRA)" <ji...@apache.org> on 2018/02/05 18:45:00 UTC

[jira] [Updated] (HIVE-18596) Synchronize value of hive.spark.client.connect.timeout across unit tests

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

Sahil Takiar updated HIVE-18596:
--------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0
           Status: Resolved  (was: Patch Available)

Pushed to master. Thanks Peter for the review.

> Synchronize value of hive.spark.client.connect.timeout across unit tests
> ------------------------------------------------------------------------
>
>                 Key: HIVE-18596
>                 URL: https://issues.apache.org/jira/browse/HIVE-18596
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Spark
>            Reporter: Sahil Takiar
>            Assignee: Sahil Takiar
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: HIVE-18596.1.patch
>
>
> {{hive.spark.client.connect.timeout}} is set to 30 seconds for {{TestMiniSparkOnYarnCliDriver}} but it left at the default value for all other tests. We should use the same value (30 seconds) for all other tests.
> We have seen flaky tests due to failure to establish the remote within the allotted timeout. This could be due to the fact that we run our tests in the cloud so maybe occasional network delays are more common.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)