Page MenuHomePhabricator

Migrate tools-redis to a bigger instance
Closed, ResolvedPublic

Description

Per Yuvi.

Event Timeline

Legoktm raised the priority of this task from to Needs Triage.
Legoktm updated the task description. (Show Details)
Legoktm added projects: Cloud-Services, Toolforge.
Legoktm added subscribers: Legoktm, yuvipanda.
coren triaged this task as Low priority.Feb 10 2015, 9:20 PM
coren moved this task from Triage to Backlog on the Cloud-Services board.
coren subscribed.

tools-redis now is an instance with 16 GByte memory and 160 GByte disk space.

IIRC the problem was not with memory; of the 160 GByte disk space, only the default 18 GByte are mounted at the moment (11 GByte of that available). So we need to set up the rest and mount it.

I must have missed the last line:

root@tools-redis:~# df -h 
Filesystem                                       Size  Used Avail Use% Mounted on
/dev/vda1                                         18G  1.4G   16G   8% /
udev                                             7.9G   12K  7.9G   1% /dev
tmpfs                                            1.6G  276K  1.6G   1% /run
none                                             5.0M     0  5.0M   0% /run/lock
none                                             7.9G     0  7.9G   0% /run/shm
labstore.svc.eqiad.wmnet:/project/tools/home      30T   15T   16T  49% /home
labstore.svc.eqiad.wmnet:/keys                   960M   47M  913M   5% /public/keys
labstore1003.eqiad.wmnet:/dumps                   44T  9.8T   34T  23% /public/dumps
labstore.svc.eqiad.wmnet:/project/tools/project   30T   15T   16T  49% /data/project
labstore.svc.eqiad.wmnet:/scratch                7.3T  1.3T  6.0T  17% /data/scratch
/dev/mapper/vd-redis                             142G   24G  112G  18% /var/lib/redis
root@tools-redis:~#

because 24 GByte cannot have previously lived on / :-). So this is resolved and we have 112 GByte to breathe.