Welcome to the new Gigaspaces XAP forum. To recover your account, please follow these instructions.

Ask Your Question

PU deploy folders refreshed in high availability mode


I found that when I configured our product(built upon XAP 9.6) to run in HA mode (2 hosts in my example), the deploy folders (NOT work/processing-units folders) of PUs of the host that running the backup GSM always got refreshed (re-download everything in deploy folders from the host running managing GSM).

It looks to me a feature of XAP's 'Hot Deploy'. Is there a config to stop this as it is creating issues like a deploy folder left empty if the processes got killed during the download. And then when we restart the product and the previous backup GSM got elected to be the mananging GSM, it will be a problem as the PU's deploy folder is empty!

In the backup GSM log, below logs can be found for each PU:

2014-11-25 16:36:58,289 GSM INFO [com.gigaspaces.grid.gsm.peer] - Adding [reports] from GSM - [GSM pid[3864] host[serverA/]] 2014-11-25 16:36:58,312 GSM INFO [com.gigaspaces.grid.gsm.peer] - Downloading [reports] into [C:\THEAPP\deploy\reports] from managing GSM located at [ ] ... 2014-11-25 16:37:47,417 GSM INFO [com.gigaspaces.grid.gsm.peer] - Downloaded [reports], size [68.4mb] to [C:\THEAPP\deploy\reports]

Thanks very much!


asked 2014-11-25 00:19:44 -0500

Edwin gravatar image
edit retag flag offensive close merge delete


Hi Edwin,

When restarting the gs-agent and the second GSM will take over, there should not be any issue even if the deploy folder is empty. Did you test it?


Yuval gravatar imageYuval ( 2014-11-26 02:46:28 -0500 )edit

Hi Yuval

Thanks for your response. We had this happened once in one of our UAT environments, the product kept restarting(due to the empty folder I believe). We had to stop the product, copied the files back to the empty deploy folder and then restarted it.

We had other problems in production related to this behavior, such as some files not from deploy folder got copied into the deploy folder (we haven't located the cause of it yet). We had to make the deploy folders readonly as a temp solution.

Do you have any idea why XAP behaves this way(is it for hot deploy) and if this can be stopped by configuration? (we don't hot deploy binary updates)

Thanks very much Edwin

Edwin gravatar imageEdwin ( 2014-11-26 18:21:52 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

Hi Edwin,

We didn't bump into such an issue. Can you please open a support case via the support portal and attache reproduction and logs.



answered 2014-11-30 04:57:24 -0500

Yuval gravatar image
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools



Asked: 2014-11-25 00:19:24 -0500

Seen: 144 times

Last updated: Nov 30 '14