[
https://issues.apache.org/jira/browse/SLIDER-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128671#comment-14128671
]
thomas liu commented on SLIDER-158:
-----------------------------------
To get around the issue mentioned in SLIDER-418, one option may be making a
different code control flow path in serviceInit, only for the case when the
action.equals("diagnostics"). For example, when executing serviceInit(), we
first check if the action equals to diagnostics(given that by now we are
already able to check action from serviceArgs), if so, we just do what is
needed for diagnostics and then return.
Does this break existing code execution path too much?
> add a "slider diagnostics" command
> ----------------------------------
>
> Key: SLIDER-158
> URL: https://issues.apache.org/jira/browse/SLIDER-158
> Project: Slider
> Issue Type: New Feature
> Components: client
> Affects Versions: Slider 0.30
> Reporter: Steve Loughran
> Assignee: thomas liu
>
> Tech preview users are having problems, and it is very hard for us to
> diagnose what is going on.
> I propose a {{slider diagnostics}} command to print out the client-side
> state, look at HDFS and see what's up there
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
