[jira] [Updated] (SDAP-107) Ningester container does not report exit code correctly

2018-06-06 Thread Frank Greguska (JIRA)


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

Frank Greguska updated SDAP-107:

Component/s: nexus

> Ningester container does not report exit code correctly
> ---
>
> Key: SDAP-107
> URL: https://issues.apache.org/jira/browse/SDAP-107
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>  Components: nexus
>Reporter: Frank Greguska
>Assignee: Frank Greguska
>Priority: Major
>
> When the Spring batch job fails the exit code is being reported as 0 instead 
> of non-zero to indicate failure. This is making debugging many jobs very 
> difficult because it is impossible to determine which jobs failed.



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


[jira] [Created] (SDAP-107) Ningester container does not report exit code correctly

2018-06-06 Thread Frank Greguska (JIRA)
Frank Greguska created SDAP-107:
---

 Summary: Ningester container does not report exit code correctly
 Key: SDAP-107
 URL: https://issues.apache.org/jira/browse/SDAP-107
 Project: Apache Science Data Analytics Platform
  Issue Type: Bug
Reporter: Frank Greguska


When the Spring batch job fails the exit code is being reported as 0 instead of 
non-zero to indicate failure. This is making debugging many jobs very difficult 
because it is impossible to determine which jobs failed.



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


[jira] [Assigned] (SDAP-107) Ningester container does not report exit code correctly

2018-06-06 Thread Frank Greguska (JIRA)


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

Frank Greguska reassigned SDAP-107:
---

Assignee: Frank Greguska

> Ningester container does not report exit code correctly
> ---
>
> Key: SDAP-107
> URL: https://issues.apache.org/jira/browse/SDAP-107
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>  Components: nexus
>Reporter: Frank Greguska
>Assignee: Frank Greguska
>Priority: Major
>
> When the Spring batch job fails the exit code is being reported as 0 instead 
> of non-zero to indicate failure. This is making debugging many jobs very 
> difficult because it is impossible to determine which jobs failed.



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


[GitHub] fgreg opened a new pull request #9: SDAP-107 Ningester container does not report exit code correctly

2018-06-06 Thread GitBox
fgreg opened a new pull request #9: SDAP-107 Ningester container does not 
report exit code correctly
URL: https://github.com/apache/incubator-sdap-ningester/pull/9
 
 
   Because I was using a pipe to prepend text to every log line, when the java 
command failed the exit status was being overwritten by the exit status of the 
sed command effectively making it 0. This caused the container to exit with 
code 0 and would show up as a successful job completion in kubernetes.
   
   Fix was to use `set -o pipefail` in entrypoint script.


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:
us...@infra.apache.org


With regards,
Apache Git Services


[jira] [Commented] (SDAP-107) Ningester container does not report exit code correctly

2018-06-06 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/SDAP-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503736#comment-16503736
 ] 

ASF GitHub Bot commented on SDAP-107:
-

fgreg opened a new pull request #9: SDAP-107 Ningester container does not 
report exit code correctly
URL: https://github.com/apache/incubator-sdap-ningester/pull/9
 
 
   Because I was using a pipe to prepend text to every log line, when the java 
command failed the exit status was being overwritten by the exit status of the 
sed command effectively making it 0. This caused the container to exit with 
code 0 and would show up as a successful job completion in kubernetes.
   
   Fix was to use `set -o pipefail` in entrypoint script.


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:
us...@infra.apache.org


> Ningester container does not report exit code correctly
> ---
>
> Key: SDAP-107
> URL: https://issues.apache.org/jira/browse/SDAP-107
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>  Components: nexus
>Reporter: Frank Greguska
>Assignee: Frank Greguska
>Priority: Major
>
> When the Spring batch job fails the exit code is being reported as 0 instead 
> of non-zero to indicate failure. This is making debugging many jobs very 
> difficult because it is impossible to determine which jobs failed.



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


[GitHub] jjacob7734 opened a new pull request #30: SDAP-13

2018-06-06 Thread GitBox
jjacob7734 opened a new pull request #30: SDAP-13
URL: https://github.com/apache/incubator-sdap-mudrod/pull/30
 
 
   Progress on SDAP-13


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:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] asfgit commented on issue #30: SDAP-13

2018-06-06 Thread GitBox
asfgit commented on issue #30: SDAP-13
URL: 
https://github.com/apache/incubator-sdap-mudrod/pull/30#issuecomment-395176398
 
 
   Can one of the admins verify this patch?


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:
us...@infra.apache.org


With regards,
Apache Git Services


[jira] [Commented] (SDAP-13) Rearchitect MUDROD storage

2018-06-06 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/SDAP-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503749#comment-16503749
 ] 

ASF GitHub Bot commented on SDAP-13:


asfgit commented on issue #30: SDAP-13
URL: 
https://github.com/apache/incubator-sdap-mudrod/pull/30#issuecomment-395176398
 
 
   Can one of the admins verify this patch?


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:
us...@infra.apache.org


> Rearchitect MUDROD storage
> --
>
> Key: SDAP-13
> URL: https://issues.apache.org/jira/browse/SDAP-13
> Project: Apache Science Data Analytics Platform
>  Issue Type: New Feature
>  Components: mudrod
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Critical
> Fix For: 0.1
>
>
> [~Yongyao] we were discussing dropping support for ES and moving to Solr. 
> Lets use this issue to track development. [~nchung] which version of Solr are 
> we going to support across SDAP products?



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


[jira] [Commented] (SDAP-13) Rearchitect MUDROD storage

2018-06-06 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/SDAP-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503748#comment-16503748
 ] 

ASF GitHub Bot commented on SDAP-13:


jjacob7734 opened a new pull request #30: SDAP-13
URL: https://github.com/apache/incubator-sdap-mudrod/pull/30
 
 
   Progress on SDAP-13


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:
us...@infra.apache.org


> Rearchitect MUDROD storage
> --
>
> Key: SDAP-13
> URL: https://issues.apache.org/jira/browse/SDAP-13
> Project: Apache Science Data Analytics Platform
>  Issue Type: New Feature
>  Components: mudrod
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Critical
> Fix For: 0.1
>
>
> [~Yongyao] we were discussing dropping support for ES and moving to Solr. 
> Lets use this issue to track development. [~nchung] which version of Solr are 
> we going to support across SDAP products?



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