flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias (Jira)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-15871) Support to start sidecar container
Date Fri, 28 Aug 2020 09:26:00 GMT

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

Matthias commented on FLINK-15871:
----------------------------------

{color:#C1C7D0}This issue was revisited in the context of the Engine team's backlog grooming
on August 28, 2020. No action were taken since it is a subtask of the umbrella ticket FLINK-17709
which people are actively working on.{color}

> Support to start sidecar container
> ----------------------------------
>
>                 Key: FLINK-15871
>                 URL: https://issues.apache.org/jira/browse/FLINK-15871
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Deployment / Kubernetes
>    Affects Versions: 1.10.0
>            Reporter: Yang Wang
>            Priority: Major
>             Fix For: 1.12.0
>
>
> >> How does sidecar container work?
> A sidecar container is running beside the Jobmanager and TaskManager container. It could
be used to collect log or debug some problems. For example, when we configure the sidecar
container to fluentd and share the TaskManager log with volume, then it could be used to upload
the logs to HDFS, elastic search, etc. Also we could start a sidecar container with debugging
image which contains lots of tools and help to debug the network problems.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message