Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-1564 Ozone multi-raft support
  3. HDDS-2756

Handle pipeline creation failure in different way when it exceeds pipeline limit

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • 0.5.0
    • None

    Description

      In current codes, pipeline creation failure will print out entire error trace when it exceeds pipeline number limit., which is very like false alarms. We should limit printing this type of trace and don't consider it as an error.

      Attachments

        Issue Links

          Activity

            People

              timmylicheng Li Cheng
              timmylicheng Li Cheng
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m