code hasn't changed this sprint and appears to work in online.

I also experimented with changing the memory setting on a devenv and creating the cart and saw apc.shm_size respond accordingly.

QE can you confirm this is an issue and/or check stage?

> for i in small medium large; do
>   rhc app create php$i php-5.3 -g $i
>   rhc ssh php$i 'php -i | grep apc.shm_size'
>   rhc ssh php$i 'echo $OPENSHIFT_GEAR_MEMORY_MB'
> done
>
> Application Options
> -------------------
> Domain:     vvitek
> Cartridges: php-5.3
> Gear Size:  small
> Scaling:    no
> 
> apc.shm_size => 64M => 64M
> 512
>
> Application Options
> -------------------
> Domain:     vvitek
> Cartridges: php-5.3
> Gear Size:  medium
> Scaling:    no
> 
> apc.shm_size => 64M => 64M
> 512
>
> Application Options
> -------------------
> Domain:     vvitek
> Cartridges: php-5.3
> Gear Size:  large
> Scaling:    no
> 
> apc.shm_size => 64M => 64M
> 
> 512

I can confirm this on latest devenv. The problem is caused by $OPENSHIFT_GEAR_MEMORY_MB env var, which is still set to 512.

Lei Zhang, can you confirm this cannot be reproduced in PROD? Otherwise, we'd need migration, once fixed. Thanks!

Just tested on PROD. Can't reproduce there.

> $ rhc app create php$i php-5.3 -g $i
>
> $rhc ssh php$i 'php -i | grep apc.shm_size'
> apc.shm_size => 256M => 256M
>
> $ rhc ssh php$i 'echo $OPENSHIFT_GEAR_MEMORY_MB'
> 2048

Works as expected on devenv_5305.

From resource_limits.conf:

memory_limit_in_bytes=536870912       # 512MB
memory_memsw_limit_in_bytes=641728512 # 512M + 100M (100M swap)

create application
#echo $OPENSFHIT_GEAR_MEMORY_DB
512

Edit resource_limits.conf:
memory_limit_in_bytes=1073741824       # 1024MB
memory_memsw_limit_in_bytes=1178599424 # 1024M + 100M (100M swap)

# restart mcollective

create application
#echo $OPENSFHIT_GEAR_MEMORY_DB
1024

If other environments are returning wrong values, verify the values in resource_limits.conf with Ops.  Ops is responsible for these files after converting them to be ERB processed via puppet.

i think the reported issue here was if you create a large gear on a devenv w/o changing the resource file (which, strangely, works, i'm not sure sure).  in that case the ENV variable is still 512.

^^ "i'm not sure why"

node_profile in resource_limits.conf is reported from the Node to the Broker. It is up to the Broker to allocate gears to the correct Node with the given node_profile.

So a couple clarifications:

1) devenvs allow creation of small, medium, and large gears, but will always set the memory to 512megs.

2) the original bug report was against INT which does not have the behavior described in #1.  It should have different memory sizes for small/medium/large, and the original report shows that in the env variable value.  The original issue really had nothing to do w/ the memory env variable, it had to do w/ the php setting not being set correctly.  The bug title is wrong (i'm going to change it now)

3) stage/prod don't have this bug.

4) devenvs appear to work correctly in that if you change the memory size in the resource file, the env variable changes accordingly.  (Jhon's comment #6 and my comment #1)

So all in all it seems we can't recreate this, though i don't think anyone except QE has actually tried in INT.

to save QE some time....i'm still seeing this in INT, it's pretty bizarre:


[medapp-bparees.int.rhcloud.com 546bc59becb8d47bb7000023]\> php -i |grep apc.shm
apc.shm_segments => 1 => 1
apc.shm_size => 32M => 32M

[medapp-bparees.int.rhcloud.com 546bc59becb8d47bb7000023]\> env | grep MB
OPENSHIFT_GEAR_MEMORY_MB=1024

and the code in question is:

apc.shm_size=<%= (ENV['OPENSHIFT_PHP_APC_SHM_SIZE'] =~ /^[0-9]+[MG]$/) ? ENV['OPENSHIFT_PHP_APC_SHM_SIZE'] : ((ENV['OPENSHIFT_GEAR_MEMORY_MB'].to_i/8).to_i.to_s+"M") %>


and OPENSHIFT_PHP_APC_SHM_SIZE is not set.

as best i can tell, apc.ini.erb isn't being processed at all, and we're just picking up a default value from php.

I couldn't reproduce this on STG last Friday. INT was unavailable, as the restart was in progress. I'm waiting on new INT to become available right now.

Sorry for the confuse. Let me make it clear here.

The issue ONLY happens on INT.
STG does NOT have this issue.
PROD should be OK (we checked the small gear size since our account only have that capacity, it shows the correct value, apc.shm_size => 64M => 64M, OPENSHIFT_GEAR_MEMORY_MB=512)

INT:
  values of apc.shm_size are *incorrect*, always 32M
    apc.shm_size => 32M => 32M  (small)
    apc.shm_size => 32M => 32M  (medium)
    apc.shm_size => 32M => 32M  (large)
  values of OPENSHIFT_GEAR_MEMORY_MB are correct
    OPENSHIFT_GEAR_MEMORY_MB=512  (small)
    OPENSHIFT_GEAR_MEMORY_MB=1024 (medium)
    OPENSHIFT_GEAR_MEMORY_MB=2048 (large)

STG:
  values of apc.shm_size are correct
    apc.shm_size =>  64M =>  64M  (small)
    apc.shm_size => 128M => 128M  (medium)
    apc.shm_size => 256M => 256M  (large)
  values of OPENSHIFT_GEAR_MEMORY_MB are correct
    OPENSHIFT_GEAR_MEMORY_MB=512  (small)
    OPENSHIFT_GEAR_MEMORY_MB=1024 (medium)
    OPENSHIFT_GEAR_MEMORY_MB=2048 (large)

Seems like there's APCu RPM installed instead of APC RPM on INT.

The APCu RPM effectively obsoletes the APC RPM.. which is super weird, as it comes different (and thus not OpenShift-customized) .ini file.
> php-pecl-apcu provides "php-pecl-apc = 4.0.7" 

I'm going to downgrade to the "older & stable" APC. I guess we don't want to upgrade all php-5.3 gears to APCu at all, unless we have really strong arguments for this step. If doing so, I suspect there might be really dangerous side effects / backward incompatibilities.

Seems like the APCu conflicts with APC already. Will add subsequent PR to ensure this even from our cartridge RPMs.

> Processing Conflict: php-pecl-apcu-4.0.7-1.el6.x86_64 conflicts php-pecl-apc < 4
> Error: php-pecl-apcu conflicts with php-pecl-apc-3.1.9-2.el6.x86_64

Manual steps to fix the INT, if it doesn't get fixed automatically tomorrow during the reset:
https://github.com/openshift/puppet-openshift-online/issues/975

https://github.com/openshift/origin-server/pull/5981

Once there is new INT (reset) or https://github.com/openshift/puppet-openshift-online/issues/975 is addressed, the issue should be fixed.

https://github.com/openshift/origin-server/pull/5994 (follow-up for PHP 5.4 as well)

Verified on INT(devenv_5330)

[rayzhang@ray Work]$ rhc app ssh myappsmall "php -i |grep [Aa]pc.shm_size"
apc.shm_size => 64M => 64M
[rayzhang@ray Work]$ rhc app ssh myappmedium "php -i |grep [Aa]pc.shm_size"
apc.shm_size => 128M => 128M
[rayzhang@ray Work]$ rhc app ssh myapplarge "php -i |grep [Aa]pc.shm_size"
apc.shm_size => 256M => 256M