You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@heron.apache.org by GitBox <gi...@apache.org> on 2018/06/14 11:15:43 UTC

[GitHub] cristobalcl opened a new issue #2919: Launch PEX on Kubernetes fails

cristobalcl opened a new issue #2919: Launch PEX on Kubernetes fails
URL: https://github.com/apache/incubator-heron/issues/2919
 
 
   I recently get this error each time I try to launch a topology to Kubernetes:
   
   ```
   [2018-06-14 12:17:11 +0000] [DEBUG]: Starting new HTTP connection (1): localhost
   [2018-06-14 12:17:55 +0000] [DEBUG]: http://localhost:8001 "POST /api/v1/proxy/namespaces/heron/services/heron-apiserver:9000/api/v1/topologies HTTP/1.1" 500 137
   [2018-06-14 12:17:55 +0000] [ERROR]: Encountered exceptions on uploading the package 'xxxxxxxxxx.tar.gz'
   [2018-06-14 12:17:55 +0000] [ERROR]: Failed to launch topology 'xxxxxxxxxx' 
   [2018-06-14 12:17:55 +0000] [DEBUG]: Elapsed time: 44.295s.
   ```
   
   This is running locally through a kubectl proxy, but I get the same error when I try from another POD in the same Kubernetes cluster.
   
   ```
   $ heron version
   heron.build.git.revision : ddbb98bbf173fb082c6fd575caaa35205abe34df
   heron.build.git.status : Clean
   heron.build.host : ci-server-01
   heron.build.time : Sat Mar 31 09:25:55 UTC 2018
   heron.build.timestamp : 1522488355000
   heron.build.user : release-agent1
   heron.build.version : 0.17.8
   ```
   
   This is the log from the heron-apiserver instance in the Heron POD:
   
   [heron-apiserver.log](https://github.com/apache/incubator-heron/files/2101959/heron-apiserver.log)
   
   I  deploy Heron in Kubernetes (AWS) using Helm:
   
   ```
   helm repo add heron-charts https://storage.googleapis.com/heron-charts
   helm install heron-charts/heron --name heron --namespace heron
   ```
   
   Of course, the topologies work OK in my local Heron.
   
   It's fail both with big (~50 mb) and small (1.5 mb) PEX. In the past, I have got it worked trying repeatedly 10-20 times (in a Jenkins pipeline in the same cluster), but now it does not work anymore.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services