Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-4822

Allow dynamic log4j configuration for Catalog and Impalads

    Details

      Description

      Currently adjusting logging configuration for Catalog and impalads require a restart of services. It is a big supportability pain in production environments. A nice feature for supportability purposes is to have dynamic log4j configuration which doesn't require a restart of daemons. This jira aims to have a easy way to change logging level per class/per package without service restarts.

        Activity

        Hide
        anujphadke Anuj Phadke added a comment -

        I think there is already a JIRA for this -
        https://issues.cloudera.org/browse/IMPALA-4774

        Show
        anujphadke Anuj Phadke added a comment - I think there is already a JIRA for this - https://issues.cloudera.org/browse/IMPALA-4774
        Hide
        bharathv bharath v added a comment -

        IMPALA-4822: Implement dynamic log level changes

        Very often we have to change the logging levels
        of Impalads and Catalog server for debugging purposes.
        Currently, there is no way to do that without a restart
        of the daemons, which is not a viable option in production
        deployments.

        This patch addresses this supportability gap by exposing
        the ability to set dynamic logging levels using a simple
        web endpoint on Impalad/Catalog/Statestore web pages.

        This includes setting VLOG levels (equivalent to --v flag)
        as well as setting log4j levels on the Frontend and the
        Catalog JVMs.

        Change-Id: I588418e9bcb0b66d33138baf96207a5a35bfbd63
        Reviewed-on: http://gerrit.cloudera.org:8080/5792
        Reviewed-by: Bharath Vissapragada <bharathv@cloudera.com>
        Tested-by: Impala Public Jenkins

        Show
        bharathv bharath v added a comment - IMPALA-4822 : Implement dynamic log level changes Very often we have to change the logging levels of Impalads and Catalog server for debugging purposes. Currently, there is no way to do that without a restart of the daemons, which is not a viable option in production deployments. This patch addresses this supportability gap by exposing the ability to set dynamic logging levels using a simple web endpoint on Impalad/Catalog/Statestore web pages. This includes setting VLOG levels (equivalent to --v flag) as well as setting log4j levels on the Frontend and the Catalog JVMs. Change-Id: I588418e9bcb0b66d33138baf96207a5a35bfbd63 Reviewed-on: http://gerrit.cloudera.org:8080/5792 Reviewed-by: Bharath Vissapragada <bharathv@cloudera.com> Tested-by: Impala Public Jenkins

          People

          • Assignee:
            bharathv bharath v
            Reporter:
            bharathv bharath v
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development