Uploaded image for project: 'Bigtop'
  1. Bigtop
  2. BIGTOP-844

hadoop rpm upgrade sequence is broken

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.5.0
    • Fix Version/s: 0.6.0
    • Component/s: rpm
    • Labels:
      None

      Description

      Here's the deal – during the RPM upgrade sequence there's a point in time when files that have different names in new and old package exist side-by-side. What it means for our style of hadoop packaging is that we'll have both /usr/lib/hadoop/foo-<old version>.jar and /usr/lib/hadoop/foo-<new version>.jar getting onto the classpath when we issue a condrestart for any service.

      This is pretty bad.

      At this point my knee jerk reaction is to re-evaluate why do we need versioned jars to begit with. Do you guys think there's any value in something like:

      • /usr/lib/hadoop/hadoop-common-2.0.0.jar

      vs a simple:

      • /usr/lib/hadoop/hadoop-common.jar

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: