Page History

...

pool my_pool {
         lb_mode fastest
         min active members 2
member 10.12.10.7:80 priority 3
member 10.12.10.8:80 priority 3
member 10.12.10.9:80 priority 3
member 10.12.10.4:80 priority 2
member 10.12.10.5:80 priority 2
member 10.12.10.6:80 priority 2
member 10.12.10.1:80 priority 1
member 10.12.10.2:80 priority 1
member 10.12.10.3:80 priority 1
}

Virtualize Configuration

Ensure that the load balancer is configured so that changes are propagated to only one node before configuring Virtualize for load balancing. 

...

Workspace Configuration

Anchor
WorkspaceConfig WorkspaceConfig

The workspace needs to be configured to share the VirtualAssets project and all of its associated content (.pmpdd, .pvadd, .pjcdd, VirtualAssets.xml, .git, and so on) across the cluster. This is necessary to keep members of the cluster in sync when changes are made. There are two ways to accomplish this:

1. Use network attached storage (NAS) to mount a shared file system containing the workspace that all members of the cluster will access.
2. Set up a source control repository (for example, git) that has a checked-in workspace.
   • An external process would need to be responsible for pulling in new changes as appropriate to keep cluster members in sync. We recommend using git fetch or an equivalent command as a post-commit trigger to synchronize sharing.

Virtualize Configuration

Ensure that the load balancer is configured so that changes are propagated to only one node before configuring Virtualize for load balancing. 

WAR, Docker, or Kubernetes

After sharing the workspace (see Workspace Configuration), start your deployment with the following JVM argument:

-Dparasoft.auto.deploy.new=false

Desktop/Command Line

1. Share the VirtualAssets project across the cluster. See Workspace Configuration for more information.
2. etc.) across the cluster. We recommend using a git fetch command as a post commit trigger to synchronize sharing.Enable refreshing using native hooks or polling:
   • From the GUI: 
     1. Choose Window > Preference > General > Workspace from the Virtualize main menu.
     2. Enable the Refresh using native hooks or polling option and restart the server.
        
   • From the command line:
     1. Open the org.eclipse.core.resources.prefs file in the <WORKSPACE>/.metadata/.plugins/org.eclipse.core.runtime/.settings/ directory.

     2. Add the refresh.enabled=true property, for example:
        

        Code Block
        eclipse.preferences.version=1 version=1 refresh.enabled=true

     3. Restart the server.

3. Add the following Java option to JVM argument to your startup command on all nodes in the cluster to put the server. :
   
   -J-Dparasoft.auto.deploy.new=false
   
   
4. Restart your servers.

...