Hi, I’m running 2.0.1 python client on python3 Flask based web application. Time to time, when load is higher, getting a key failed with (-1, ‘Bad file descriptor’, ‘src/main/client/get.c’, 113) error. I’m using one object per process, that is constructed in this way: conf = {"hosts": self.addr…

Hi, I have the same problem, but when writing (puting or incrementing). Maybe proto-fd-max is low?

[image] manana: Bad file descriptor This message ( 1 , 2 , 3 ) occurs when an Aerospike server closes an active socket. One way which this may happen, as mentioned by @tivvit , is if proto-fd-max has been exceeded.

I have set this option to 100.000, but it didin’t solve the problem. This problem occurs, when i’m trying to get data from LLIST contains 10-20 million elements. I have also set timeout to 2 min, but this problem occurs immediately when i’m trying to work with llist.

What version of Aerospike Server are you running and do any warnings appear in the logs when these transactions timeout?

There are no any warnings in the logs. How can i get my AS version?

Bad file descriptor error while getting a key

Client Libraries Python Client

_PPC-help.ru October 6, 2016, 7:04pm 3

I have this problem too, anyone solved it?

Topic		Replies	Views
Weird error happening randomly with Node client- Bad file descriptor as_socket_read_limit line 432 Node.js Client	4	2535	February 24, 2017
Context about three, somewhat commonly seen, Aerospike errors Node.js Client error , message , record	5	3558	September 29, 2015
Not able to change proto-fd-max to more than one lakh	6	2943	March 23, 2017
1024 system file descriptors not enough, config specified 15000	1	373	August 15, 2024
What does "Bad file descriptor" mean PHP Client Library	1	3178	March 31, 2015

Bad file descriptor error while getting a key

Related topics