[bind10-dev] Parallel implementation of Xfrout Server

[Jerry]

Hi all,

 

I discussed with Likun about the parallel implementation of Xfrout Server.
Share them below, and appreciate your suggestions:-)

 

BIND10-Xfrout was designed to support the short connection from several auth
processes, which means Auth needs to simply make a new connection every
time, and the connection will be closed after the handling of a xfrout
request is complete.   

In order to reduce the overhead, currently we use long tcp connection
between Xfrout and Auth, that is, Xfrout will maintain a tcp connection with
each Auth process, until an error occurs or Xfrout/Auth shutdown.

See diagram below : 

                  |----------|

                  |  Xfrout  | 

                  |----------|

                  /     |     \

                 /      |      \

                /       |       \

         |----------|----------|-------|

         |   Auth1  |   Auth2  |  ...  |  

         |----------|----------|-------|

          /    |    \

         /     |     \

        /      |      \

 |----------|----------|-------|

 | Request1 | Request2 |  ...  |  

 |----------|----------|-------| 

 

* The connection between Xfrout and Auth needs to be created only on the
first time or if an error occur

* On receiving a request, Auth will send the corresponding socket fd and
request message to Xfrout Server via tcp connection, then Xfrout Server can
handle the request and send xfrout response(AXFR/IXFR) via the socket fd in
a new thread.

* Xfrout server will maintain M + N tcp connections(If we have M Auth
processes and handle N xfrout requests at the same time).  

 

Any suggestions?

 

Thanks.

 

--

Jerry

 

 

 

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20101215/6cf60608/attachment.html>