https://sourceforge.net/p/postgres-xc/xc-wiki/Reconnect_GTM-Proxy/Recent changes to Reconnect_GTM-ProxyenFri, 27 Jun 2014 02:32:28 -0000https://sourceforge.net/p/postgres-xc/xc-wiki/Reconnect_GTM-Proxy/<div class="markdown_content"><pre></pre> </div>Koichi SuzukiFri, 27 Jun 2014 02:32:28 -0000https://sourceforge.netf88a427d1126c62d5db20ffe0d9045e0c59da1f3https://sourceforge.net/p/postgres-xc/xc-wiki/Reconnect_GTM-Proxy/<div class="markdown_content"><pre></pre> </div>Koichi SuzukiFri, 27 Jun 2014 02:32:28 -0000https://sourceforge.net7da4a0813d7a5ea86653b4b647ca9512e7b38f18https://sourceforge.net/p/postgres-xc/xc-wiki/Reconnect_GTM-Proxy/<div class="markdown_content"><pre></pre> </div>Koichi SuzukiFri, 27 Jun 2014 02:32:28 -0000https://sourceforge.net00995b5249cdf8d8db90f850a99ade51ffccab48https://sourceforge.net/p/postgres-xc/xc-wiki/Reconnect_GTM-Proxy/<div class="markdown_content"><pre></pre> </div>Koichi SuzukiFri, 27 Jun 2014 02:32:28 -0000https://sourceforge.net5b10dd4611c70491c6e469d44c8b393b470321a7https://sourceforge.net/p/postgres-xc/xc-wiki/Reconnect_GTM-Proxy/<div class="markdown_content"><pre></pre> </div>Koichi SuzukiFri, 27 Jun 2014 02:32:28 -0000https://sourceforge.net43fa45d8f41f1423a29eea0ee5ea126f19fb27b8https://sourceforge.net/p/postgres-xc/xc-wiki/Reconnect_GTM-Proxy/<div class="markdown_content"><pre></pre> </div>Koichi SuzukiFri, 27 Jun 2014 02:32:28 -0000https://sourceforge.netb441e16a3e2d86f0ab8f15eaa7841a36b50cc228https://sourceforge.net/p/postgres-xc/xc-wiki/Reconnect_GTM-Proxy/<div class="markdown_content"><pre></pre> </div>Koichi SuzukiFri, 27 Jun 2014 02:32:28 -0000https://sourceforge.net8347c78fb0b3e2e825983da4dee2c9fe43a3b566https://sourceforge.net/p/postgres-xc/xc-wiki/Reconnect_GTM-Proxy/<div class="markdown_content"><pre></pre> </div>Koichi SuzukiFri, 27 Jun 2014 02:32:28 -0000https://sourceforge.net425d5bbb83387143d88c50b06d770d26d9fed421https://sourceforge.net/p/postgres-xc/xc-wiki/Reconnect_GTM-Proxy/<div class="markdown_content"><pre>--- v14 +++ v15 @@ -15,30 +15,16 @@ gtm_ctl -S gtm_proxy reconnect -D dir -o "-s xxx -t xxx" + where -D option describes gtm_proxy's working directory, which must be the same as it started. -s and -t specifies address and the port number of the new GTM. + +Also, at the time of start, gtm_ctl will have new options, namely, -w and -n. They indicates how long and how many times GTM-Proxy waits when it detects connection closure from GTM. During this wait, users can issue gtm_ctl reconnect to GTM-Proxy. + + Within gtm_ctl, these options are backed up to gtm_proxy.opts file in GTM's working directory, merged with existing options. Then gtm_ctl will prepare gtm_proxy_sighup.opt (file name may change) file to indicate to reconnect and issue SIGHUP signal to the gtm_proxy. -Gtm_proxy SIGHUP signal handler will check grm_proxy_sighup_opt and determines it should reconnect to the new GTM (at present, this is only one option of SIGUP action), and update a flag to indicate reconnect. Such a flag can be stored in thread-specific structure like: - - - - - - typedef struct thread_interrupt[xx] { - - GTM_RWLock ti_lock; - - bool should_lock; - - } thread_interrupt; - - - - - - -where xx is the number of created thread. +Gtm_proxy SIGHUP signal handler will check grm_proxy_sighup_opt and determines it should reconnect to the new GTM (at present, this is only one option of SIGUP action), and update a flag to indicate reconnect. Such a flag can be stored in thread-specific structure. Each thread checks this flag before it send commands to GTM. If error is detected to receive response from GTM, it will be the time to check this structure. If it is no set, then the thread can wait for a little while and recheck this. </pre> </div>Koichi SuzukiFri, 27 Jun 2014 02:32:28 -0000https://sourceforge.net6fdc7316a66d9bb82e0c84631125b3d0a26f780chttps://sourceforge.net/p/postgres-xc/xc-wiki/Reconnect_GTM-Proxy/<div class="markdown_content"><pre></pre> </div>Koichi SuzukiFri, 27 Jun 2014 02:32:28 -0000https://sourceforge.netbdf51a8f3a5dec77fe74aae832dee84cc2e7348c