Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-18159

Add support for trimming stack traces in user-facing components

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      Add a verbosity query parameter / flag(==config option) into the REST API / CLI to trim the exception stack traces, which means excluding the location information.

      The result would be something like this:

      org.apache.flink.runtime.client.JobSubmissionException: Failed to submit job.
      Caused by: java.lang.RuntimeException: org.apache.flink.runtime.client.JobExecutionException: Could not set up JobManager
      Caused by: org.apache.flink.runtime.client.JobExecutionException: Could not set up JobManager
      Caused by: java.io.FileNotFoundException: Cannot find checkpoint or savepoint file/directory 'ashudasd' on file system 'file'.
      

      This approach renders even the biggest stack traces fairly readable, and is rather convenient since it only requires changes in the actual user-facing components.

      Logging would not be impacted by this.

      The trimming was already implemented in this PR, but the flags are missing.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            chesnay Chesnay Schepler

            Dates

              Created:
              Updated:

              Slack

                Issue deployment