I think this might be because the timeout only applied to each request, and the driver is paginating in the background. Each page is a new request.
On Mon, Aug 5, 2019, 12:08 AM Oleksandr Shulgin < oleksandr.shul...@zalando.de> wrote: > On Mon, Aug 5, 2019 at 8:50 AM nokia ceph <nokiacephus...@gmail.com> > wrote: > >> Hi Community, >> >> I am using Cassanadra 3.0.13 . 5 node cluster simple topology. Following >> are the timeout parameters in yaml file: >> >> # grep timeout /etc/cassandra/conf/cassandra.yaml >> cas_contention_timeout_in_ms: 1000 >> counter_write_request_timeout_in_ms: 5000 >> cross_node_timeout: false >> range_request_timeout_in_ms: 10000 >> read_request_timeout_in_ms: 10000 >> request_timeout_in_ms: 10000 >> truncate_request_timeout_in_ms: 60000 >> write_request_timeout_in_ms: 2000 >> >> i'm trying a cassandra query using cqlsh and it is not getting timeout. >> >> #time cqlsh 10.50.11.11 -e "CONSISTENCY QUORUM; select >> asset_name,profile_name,job_index,active,last_valid_op,last_valid_op_ts,status,status_description,live_depth,asset_type,dest_path,source_docroot_name,source_asset_name,start_time,end_time,iptv,drm,geo,last_gc >> from cdvr.jobs where model_type ='asset' AND docroot_name='vx0000030' >> LIMIT 100000 ALLOW FILTERING;" >> Consistency level set to QUORUM. >> (....) >> (....) >> (79024 rows) >> >> real 16m30.488s >> user 0m39.761s >> sys 0m3.896s >> >> The query took 16.5 minutes to display the output. But my >> read_request_timeout is 10 seconds. why the query doesn't got timeout after >> 10 s ?? >> > > Hi Renoy, > > Have you tried the same query with enabling TRACING beforehand? > > https://docs.datastax.com/en/archived/cql/3.3/cql/cql_reference/cqlshTracing.html > > It doesn't sound all too likely that it has taken the client 16 minutes to > display the resultset, but this is definitely not included in the request > timeout from the server point of view. > > Cheers, > -- > Alex > >
