Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
U
unique-xids
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
uplex-varnish
unique-xids
Commits
13c60b52
Commit
13c60b52
authored
Mar 08, 2011
by
Per Buer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Spelling errors (thanks to Camiel Dobbelaar)
parent
095f6b23
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
5 deletions
+5
-5
handling_misbehaving_servers.rst
doc/sphinx/tutorial/handling_misbehaving_servers.rst
+5
-5
No files found.
doc/sphinx/tutorial/handling_misbehaving_servers.rst
View file @
13c60b52
...
@@ -17,10 +17,10 @@ one copy from the back end. In some products this is called request
...
@@ -17,10 +17,10 @@ one copy from the back end. In some products this is called request
coalescing and Varnish does this automatically.
coalescing and Varnish does this automatically.
If you are serving thousands of hits per second the queue of waiting
If you are serving thousands of hits per second the queue of waiting
requests can get huge. There are to potential problems - one is a
requests can get huge. There are t
w
o potential problems - one is a
thundering he
a
rd problem - suddenly releasing a thousand threads to
thundering herd problem - suddenly releasing a thousand threads to
serve content might send t
o
load sky high. Secondly - nobody likes to
serve content might send t
he
load sky high. Secondly - nobody likes to
wait. To deal with this
Varnish can
we can instruct Varnish to keep
wait. To deal with this we can instruct Varnish to keep
the objects in cache beyond their TTL and to serve the waiting
the objects in cache beyond their TTL and to serve the waiting
requests somewhat stale content.
requests somewhat stale content.
...
@@ -88,7 +88,7 @@ Known limitations on grace- and saint mode
...
@@ -88,7 +88,7 @@ Known limitations on grace- and saint mode
If your request fails while it is being fetched you're thrown into
If your request fails while it is being fetched you're thrown into
vcl_error. vcl_error has access to a rather limited set of data so you
vcl_error. vcl_error has access to a rather limited set of data so you
can't enable saint mode or grace mode here. This will be addressed in a
can't enable saint mode or grace mode here. This will be addressed in a
future release but a work-around
is
available.
future release but a work-around available.
* Declare a backend that is always sick.
* Declare a backend that is always sick.
* Set a magic marker in vcl_error
* Set a magic marker in vcl_error
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment