408928 - Clear netscaler cache on www.mozilla.com

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Wil Clouser [:clouserw]]

We need to clear the netscaler cache on www.mozilla.com so we can get the release done.

Thx. <3

Comment 1

[Jeremy Orem [:oremj]]

Cache flushed.

Comment 2

[Mike Beltzner [:beltzner, not reading bugmail]]

Is there any way we can request this through Kubla in the future?

Comment 3

[Jeremy Orem [:oremj]]

This is a shared cache, so we have to be pretty careful about flushing it.  I don't think it would be possible to flush the cache from kubla. Justin or Mrz does that sound correct?

Comment 4

[Wil Clouser [:clouserw]]

(In reply to comment #2)
> Is there any way we can request this through Kubla in the future?
> 

I can add a link to file a bug, but I don't want the hate when it starts getting abused.  We can try it though.

Comment 5

[Wil Clouser [:clouserw]]

(In reply to comment #3)
> This is a shared cache, so we have to be pretty careful about flushing it.  I
> don't think it would be possible to flush the cache from kubla. Justin or Mrz
> does that sound correct?
> 

We looked for a way to flush the cache through AMO and we talked briefly about some kind of NS API.  I don't think anything ever came of it - shaver, do you remember?

Comment 6

[matthew zeier [:mrz]]

Nothing ever came of it and the dev box I had for you guys at that time is now in China.  

The only method we have right now is:

  nscachemgr -a | nawk '/www.mozilla.com/ {print $1}' | xargs -n 1 nscli -U 63.245.209.4:nsroot:<password> flush cache object -locator

which is run from the Netscaler's BSD shell.

Comment 7

[Justin Fitzhugh]

This is pretty serious level of effort, and you are only waiting 15 minutes for the cache to expire as it stands now.  Is there a reason why 15 min of time can't be planned into the release schedule?  Seems to be by far one of the smaller time elements...

Comment 8

[Wil Clouser [:clouserw]]

(In reply to comment #7)
> This is pretty serious level of effort, and you are only waiting 15 minutes for
> the cache to expire as it stands now.  Is there a reason why 15 min of time
> can't be planned into the release schedule?  Seems to be by far one of the
> smaller time elements...
> 

My concern would be elements expiring at different times.  When we do a pretty big change to a page (like http://www.mozilla.com/en-US/firefox/3.0b2/firstrun/) if the CSS, images, content, etc. all doesn't expire at the same time it looks pretty broken.

Comment 9

[Justin Fitzhugh]

Good point - might make sense if thats the motivation...