[jira] [Commented] (YUNIKORN-1095) Periodic state dump REST call doesn't return anything

["Anuraag Nalluri (Jira)" <ji...@apache.org>]

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

Anuraag Nalluri commented on YUNIKORN-1095:
-------------------------------------------

[~ccondit] IIUC, you're referring to the full state dump path [here|https://github.com/apache/incubator-yunikorn-core/blob/master/pkg/webservice/routes.go#L171-L175], right? Are you suggesting that doStateDump() should be parameterized so we can have divergent behaviors of logging to a file and directly returning JSON?

If so, shouldn't the period state dump should be the one that logs to a file (as it does today), while the full state dump request should directly return JSON?

> Periodic state dump REST call doesn't return anything
> -----------------------------------------------------
>
>                 Key: YUNIKORN-1095
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1095
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: core - scheduler
>            Reporter: Craig Condit
>            Assignee: Anuraag Nalluri
>            Priority: Major
>
> After YUNIKORN-949, the REST call for period state dump doesn't return any data. This appears to be related to the changes added into doStateDump() which also log to a file. This should be separated out so that the JSON is preserved for immediate dumps, and background dumps to a file can use an alternate path.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org