Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-5998

Relax the maxFileStoreLength based upon TEIID-5584

    • Icon: Quality Risk Quality Risk
    • Resolution: Done
    • Icon: Major Major
    • 15.0
    • None
    • Query Engine
    • None
    • DV Sprint 66
    • 0.5

      Based upon https://github.com/teiid/teiid/issues/1314 we should relax the individual max file length to allow for session killing to be utilized if needed.

            [TEIID-5998] Relax the maxFileStoreLength based upon TEIID-5584

            With the default of 20 active plans the max size of a temporary lob is 1/80 of the storage space. With the default of 50 gb that is approximately 625 mb. A single large temporary lob or set of lobs (for example from using copylobs) could easily exceed that. Once we added TEIID-5584, we do a better job of recovering from out of disk situations (the biggest possible downside is that in high concurrency situations more sessions than necessary may be killed). So with this change we strike a different balance that will allow for a larger max size. With the default of 20 active plans we'll now allow a max size of 1/6 th of the storage space - anything larger than that is certainly indicative of a problem that should be killed immediately. The actual calculation is max space / max active plans ^ .6 so that even much higher numbers of active plans can still have rather large lobs.

            Steven Hawkins added a comment - With the default of 20 active plans the max size of a temporary lob is 1/80 of the storage space. With the default of 50 gb that is approximately 625 mb. A single large temporary lob or set of lobs (for example from using copylobs) could easily exceed that. Once we added TEIID-5584 , we do a better job of recovering from out of disk situations (the biggest possible downside is that in high concurrency situations more sessions than necessary may be killed). So with this change we strike a different balance that will allow for a larger max size. With the default of 20 active plans we'll now allow a max size of 1/6 th of the storage space - anything larger than that is certainly indicative of a problem that should be killed immediately. The actual calculation is max space / max active plans ^ .6 so that even much higher numbers of active plans can still have rather large lobs.

              rhn-engineering-shawkins Steven Hawkins
              rhn-engineering-shawkins Steven Hawkins
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 2 hours
                  2h
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 hours
                  2h