A new firewall rule somehow blocked the traffic still connecting. No problems have occurred anymore. It has been really quiet. I have still been developing and testing only with a single client program at a time. More problems could occur in testing in parallel. In the man libmemcahced, there is a section called
"THREADS AND PROCESSES" ... "it is important to keep one instance of memcached_st per process or thread" ... The same information there. The problems are not always obvious. The fork already copies everything and allocation of new memory and copying the data is not necessary. The establishing of a new connection should be enough. Anyway, the information that the clone is the one needed, helps. Jouni L. torstai 9. maaliskuuta 2017 3.19.51 UTC+2 Dormando kirjoitti: > > Hi, > > memcached_clone is probably always necessary if you've created the > structures in one process and then use them in another. It's definitely > required if you're using the instance in both processes. However, even > with a single process you still have complications when processes exit or > hit other conditions. > > Did the firewall fix your connectivity issues? > > On Tue, 7 Mar 2017, [email protected] <javascript:> wrote: > > > > > A possible cause already. After reading the firewall rules again, an > error was found. An old IP-address was used instead of the memcached > IP-addresses. I am not sure yet but > > this may have caused the connection to close before getting anything > back from the server. Anyway, I already added > > > > memcached_clone > > > > after the fork command to each process using the connection. It would > still be good to know, if the cloning is necessary. The process gets its > own copy of the parent process > > and these do not have anything in common. Is it necessary to clone the > complite memory structure? Is there an easy way to just to duplicate the > connection or to just to > > establish a new connection to the processes (not threads). > > > > With kind regards, Jouni > > > > > > -- > > > > --- > > You received this message because you are subscribed to the Google > Groups "memcached" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > > > > > -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
