Skip to content

scheduling for prestoooo #2

@jayunit100

Description

@jayunit100

Looks like theres some kind of client churn going on... ? not sure if this is leftover state from another container?


2019-06-11T04:16:57.050Z        INFO    node-state-poller-0     io.prestosql.metadata.DiscoveryNodeManager      Previously active node is missing: client-4 (last seen at 172.31.5.143:8080)
2019-06-11T04:16:57.050Z        INFO    node-state-poller-0     io.prestosql.metadata.DiscoveryNodeManager      Previously active node is missing: client-6 (last seen at 172.31.0.52:8080)
2019-06-11T04:16:57.050Z        INFO    node-state-poller-0     io.prestosql.metadata.DiscoveryNodeManager      Previously active node is missing: client-2 (last seen at 172.31.7.81:8080)
2019-06-11T04:16:57.050Z        INFO    node-state-poller-0     io.prestosql.metadata.DiscoveryNodeManager      Previously active node is missing: client-8 (last seen at 172.31.4.134:8080)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions