aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <>
Subject [jira] [Commented] (AURORA-1963) Structdump endpoint shows thrift metadata
Date Fri, 05 Jan 2018 00:43:00 GMT


Bill Farner commented on AURORA-1963:

{quote}Well, it is true if you are an operator that don't want to code your way around it
for troubleshooting{quote}
This may be true, depending on what information you're after.  Executor-level information
is delegated to the executor to render, which is accessible when you drill into a task in
the UI.

{quote}Is that endpoint unsupported?{quote}
I wouldn't say unsupported, but definitely less exercised than the API (apparently resulting
in the issue here).  I only point out the alternative route for any passers-by looking for
the same info.

> Structdump endpoint shows thrift metadata
> -----------------------------------------
>                 Key: AURORA-1963
>                 URL:
>             Project: Aurora
>          Issue Type: Bug
>          Components: Scheduler
>    Affects Versions: 0.19.0
>         Environment: Devcluster VM
>            Reporter: Juan Manuel Fresia
>            Priority: Minor
>              Labels: patch
> The structdump endpoint changed the way it displays the task config. This change made
some thrift internal metadata visible, such as {{__isset_bitfield}} on optionals fields and
appending underscores on the names of other fields.
> For example, here is a fragment of a 0.19 structdump output:
> {code}
>             "timestamp": 1514573549125,
>             "status": "RUNNING",
>             "scheduler": "ee5feaf3d8b1",
>             "__isset_bitfield": 1,
>             "optionals": [
>               "MESSAGE",
>               "SCHEDULER"
>             ]
> {code}
> And here is the same fragment, but with 0.18 scheduler:
> {code}
>         Item[2] = 
>           timestamp: 1514574966299
>           status: RUNNING
>           message: not set
>           scheduler: "84611e03fe9e"
> {code}
> As the structdump is the only way to get the full configuration of a task through the
UI, it is inconvenient to have those fields and naming messing around.
> The issue seems to be caused by a change in the way data taken from thrift is converted
to be pretty printed; by changing a thrift specific converter to a GSON serializer. The proposed
fix is to backport the old converter and restore the old structdump style.
> The review of the change related to the issue is [here|]
> The old pretty print utility used in 0.18 is  [here|]

This message was sent by Atlassian JIRA

View raw message