Release 2.0.5
Media Flow Controller 2.0.5 Release Notes
10
Known Behavior
Copyright © 2010, Juniper Networks, Inc.
Known Behavior
There are no new Known Behavior issues in Release 2.0.5. Some Known Behavior issues are
described in earlier release notes.
Resolved Known Issues
These Known Issues were reported in the Media Flow Controller Release 2.0.4 Release Notes
and have now been resolved:
•
When an invalid license (malformed, not expired) is installed, a “Required condition was
not met” error message is displayed.
ID: 1633
•
Avoid running parallel CPU-intensive operations.
Some management operations are CPU-intensive. If you run two or more operations in
parallel in Media Flow Controller, you might receive several syslog messages, which can
cause the command-line interface (CLI) to hang for a few minutes. Data delivery is
unaffected.
ID: 4414
Known Issues
This section identifies the known problems and limitations in Release 2.0.5.
•
Analytics Manager
•
Logging
•
Origin Server—Platform
Analytics Manager
•
When a namespace is configured with namespace <name> delivery protocol http
origin-request host-header inherit incoming-req permit, there is memory usage up to
3 GB.
Workaround: For deployments with namespace <name> delivery protocol http origin-
request host-header inherit incoming-req permit, you must plan for a larger amount of
RAM—at least 24 GB, and allocate more for the operating system (OS). For example, in a
system with 24GB RAM, by default 9.6GB is allocated for OS; increase the allocation to
OS to 12.6GB using ram-cache cache-size-MB <integer> in the CLI. Use show ram-
cache to verify.
ID: 6642
•
When namespace <name> delivery protocol http origin-fetch cache-fill client-driven
is configured, Media Flow Controller may send byte-range requests even if the origin
cannot send byte-range responses.
When the namespace origin-fetch option cache-fill client-driven is configured, and a
partial file from Media Flow Controller is in the cache and another request for the same
