Bigtop
  1. Bigtop
  2. BIGTOP-276

Standardize how clients create classpaths and java.library.paths

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 0.2.0
    • Fix Version/s: None
    • Component/s: General
    • Labels:
      None

      Description

      We need to standardize how clients (hadoop, pig, hive, sqoop, flume etc) create their classpath and java.library.path. It remains to be seen if we can also address the issue of log4j loglevels uniformly across the stack. The initial idea is to refactor the relevant bits of code from the hadoop launcher script into a universal script that'll be part of bigtop-utils.

        Issue Links

          Activity

          Hide
          Steve Loughran added a comment -
          Show
          Steve Loughran added a comment - see also HADOOP-6807 HADOOP-7466
          Hide
          Steve Loughran added a comment -

          Log4j is trouble. Step 1 is ensuring no artifacts have a log4j in there, then have the startup processes point to a log4j on the command line and/or add it to the standard classpath

          FWIW HADOOP-7705 adds a JSON format output log that is designed for machine parsing, not people.

          Show
          Steve Loughran added a comment - Log4j is trouble. Step 1 is ensuring no artifacts have a log4j in there, then have the startup processes point to a log4j on the command line and/or add it to the standard classpath FWIW HADOOP-7705 adds a JSON format output log that is designed for machine parsing, not people.

            People

            • Assignee:
              Roman Shaposhnik
              Reporter:
              Roman Shaposhnik
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Development