[
https://issues.apache.org/jira/browse/HIVE-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623687#comment-15623687
]
Siddharth Seth commented on HIVE-15041:
---------------------------------------
Got it. Was looking at the error.
A post call to projects/gcp-hive-upstream/global/firewalls
complaining about gcp-hive-upstream/global/networks/jclouds-hive-ptest-slaves
not being available. (Should this have been
gcp-hive-upstream/global/networks/hive-ptest-slaves). Not sure where the
jclouds gets inserted.
Anyway - seems like any refresh causes this problem. Till this figured out, one
possibility would be to try and re-created the ExecutionContextProvider once
the timeout has expired, instead of attempting to re-use the same
executionContextProvider to get more nodes.
Couldn't trace down what changes in between which could cause this to fail. The
config etc could change a bit to make parameters final for thread visibility -
but I don't think that is the problem.
> Specify GCE network name on Hive ptest
> --------------------------------------
>
> Key: HIVE-15041
> URL: https://issues.apache.org/jira/browse/HIVE-15041
> Project: Hive
> Issue Type: Task
> Components: Hive
> Reporter: Sergio Peña
> Assignee: Sergio Peña
> Attachments: HIVE-15041.1.patch, HIVE-15041.2.patch
>
>
> NO PRECOMMIT TESTS
> A new option on cloudhost.properties should be added to specify the GCE
> network name:
> # GCE network option
> network =
> https://www.googleapis.com/compute/v1/projects/<PROJECT-ID>/global/networks/default
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
