cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
568
Views
0
Helpful
1
Replies

ACE 4710 shows over Weeks dramatically increasing Sticky entries

Gerhard.Oettle
Level 1
Level 1

                   Hello,

I have a strange effect at my ACE 4710. I loadbalances normally reliable only 14 WEB-Services.

It's running on SW A3.25. Since several weeks I regognized a dramatical increase of Sticky entries. So when running in limitations (the stolen for reuse counter increased then) (show np 1 me-stats "-slb -v") gave more and more resources for sticky ... last it was at 65% and ran again into limits at round 650500 Sticky entries.

So I began to find out what of the services was affected with most sticky database entries and could Identify it. There were really to see round about
640000 entries for that specific service.

The sticky for that service was defined to look at a specific cookie in the http header and the timeout defined is 120 minutes.

So round about 45000 Entries was to see with a "show sticky databse group Cookie_Sticky"  with a time-to-expire value of   zero   in the database like the follwing examüple shows:

timeout      : 120           timeout-activeconns : FALSE
  sticky-entry          rserver-instance                 time-to-expire flags
  ---------------------+--------------------------------+--------------+-------+
  13765297814690832647  server1:0                          0              -
  4799436437302419802   server2:0                          0              -
  3352922268004415581   server1:0                          0              -
  17120375021283790771  server2:0                          0              -
  18319552650970721619  server1:0                          0              -

That looked for zombie databse entries....

When I modified my Sticky definition  with the command "timeout activeconns"   all the Zero-Entries were kicked out and the rsources used for Sticky
went back to 5% of usage....

Has anybody seen such an effect ?  What could this caused by ?

Many thanks for help in advance

Gerhard

1 Reply 1

ajayku2
Cisco Employee
Cisco Employee
Hi,
  
The way it works is this: after one connection is open and
the sticky entry for that connection is created, the timeout will
immediatly start decreasing. Once it reaches 0, if there are still
active connections for that sticky entry, the entry won't be deleted
unless the "timeout activeconns" option within the sticky group is
enabled. If no active conns are present for that sticky entry, the entry
will be freed. So I would say it as expected behavior. 

regards, 
Ajay Kumar
 
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: