Beware that only existing files can be invalidated.
Instead of removing a file from opcache that you have delete, you need to call opcache_invalidate before deleting it.
(PHP 5 >= 5.5.0, PHP 7, PHP 8, PECL ZendOpcache >= 7.0.0)
opcache_invalidate — Invalida un script almacenado en caché
Esta función invalida un script particular desde el caché opcode.
Si el argumento force no está definido o vale false,
el script solo se invalidará si la fecha/hora de modificación del script
es más reciente que el opcode en caché.
Esta función solo invalida el caché en memoria y no el caché de ficheros.
filenameLa ruta de acceso al script a invalidar.
force
Si vale true, el script se invalidará independientemente de si
la invalidación es necesaria o no.
Devuelve true si el caché opcode para el filename
ha sido invalidado, o si no había nada que invalidar, o bien false
si el caché opcode está desactivado.
Beware that only existing files can be invalidated.
Instead of removing a file from opcache that you have delete, you need to call opcache_invalidate before deleting it.opcache_invalidate tries to acquire SHM lock. When the lock can not be acquired opcache_invalidate will return FALSE. During multiple concurrent opcache_invalidate calls with higher probability, the function will return FALSE.Note that invalidation doesn't actually evict anything from the cache, it just forces a recompile. You can verify this by calling opcache_get_status() and seeing that the invalidated script is not actually removed from "scripts". This means it cannot be used as a more graceful alternative to opcache_reset() when the cache is full ("cache_full":true in status). The cache will eventually fill up and refuse to cache new requests if you do atomic deployment of PHP code by changing the web server's document root. It appears opcache_reset() is the only way to prevent this, but opcache_reset() can disable the cache for any amount of time while attempting to restart, causing load spikes.