Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-5582

Hadoop Vaidya throws number format exception due to changes in the job history counters string format (escaped compact representation).

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.20.0
    • 0.21.0
    • None
    • None
    • Reviewed
    • Fixed error parsing job history counters after change of counter format.

    Description

      Hadoop Vaidya (contrib/vaidya) tool throws number format exception while parsing the job history log files due to change in the format of counters string in 0.20.

      Attachments

        1. vaidya-0.21.0-5582-5764.patch
          26 kB
          Suhas
        2. vaidya_patch_21.patch
          22 kB
          Suhas

        Issue Links

        is depended upon by

        Bug - A problem which impairs or prevents the functions of the product. HADOOP-5764 Hadoop Vaidya test rule (ReadingHDFSFilesAsSideEffect) fails w/ exception if number of map input bytes for a job is zero.

        • Major - Major loss of function.
        • Closed
        relates to

        Bug - A problem which impairs or prevents the functions of the product. HADOOP-5583 method fromEscapedCompactString() from the depricated class, org.apache.hadoop.mapred.Counters is not supported in org.apache.hadoop.mapreduce.Counters

        • Major - Major loss of function.
        • Closed

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

          People

            vgogate Suhas
            vgogate Suhas
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment