i m setting timeouts
aerospike.connect_timeout 10000
aerospike.read_timeout 10000
aerospike.write_timeout 10000
in php.ini but when executing UDF from client it shows error Client timeout: timeout=1000 iterations=1 failedNodes=0 failedConns=0
extension=aerospike.so
aerospike.udf.lua_system_path=/opt/aerospike/client-php/sys-lua
aerospike.udf.lua_user_path=/opt/aerospike/client-php/usr-lua
aerospike.connect_timeout 6000000
aerospike.read_timeout 6000000
aerospike.write_timeout 6000000
this is my php.ini snippet for aerospike
Hi there. Can you confirm if this was fixed as Iām having the same issue. Below is my ext-aerospike.ini file which is loaded with PHP. If I run php -i | grep aero i get the following:
Additional .ini files parsed => /usr/local/etc/php/5.5/conf.d/ext-aerospike.ini, aerospike aerospike support => enabled aerospike version => 3.0 Registered save handlers => files user redis aerospike
So it shows that Aerospike is installed and running etc. My ext-aerospike.ini file contains the following:
An error occured while querying [9] Client timeout: timeout=1000 iterations=1 failedNodes=0 failedConns=0
any ideas on what may be causing the issue, or any other way I can set the timeout on this? Iām pretty new to Aerospike so not sure where to look from here on.
Ahhhh, perfect - thanks rbotzer - working fine now. One thing that is strange however is I also tried changing the timeout options by using Aerospike::OPT_READ_TIMEOUT => 12500 within my options array when connecting to the DB but this didnāt seem to have any effect. Again, is there something Iām doing wrong in terms of that?
So with a php.ini setting to 10000 and constructor value set to 12500, I expect the timeout to be 12500. If you passed a different value in the get() call, I expect that one to apply for the call. Please open a new issue in aerospike/aerospike-client-php.
By the way, 12.5s for timeout seems exceedingly huge. Is there a good reason for this?
Hey rbotzer - thanks for the feedback - Iāll submit an issue now detailing the bug.
I was only using 12.5s as a timeout for testing - just to ensure that the value was being passed form the relevant place etc, in reality itās no where near that high but it helped me debug the issue.