Loading ...

Configuring Communifire on a Load Balanced Web Farm | Communifire Documentation

Home » Spaces » communifire documentation » Wiki » configuring communifire on a load balanced web farm
Vivek Thakur likes this.
 

Comments (1)

  
anubhavshah
Anubhav Shah said:
Regarding "Background tasks synchronization in a web farm": It would be ideal to have a shared directory containing web files
Therefore, please consider moving the option of web IIS config settings to registry. So this RunBackgroundJobs could ideally be pulled from registry, and be set unique on each server. Likewise for Lucene, etc.

7/24/2014 03:55 PM
 · 
 
by
  
anubhavshah
Anubhav Shah said:
A potential problem that could be solved by having a common share for site files is that they match and are managed easily (updates, etc.) But since web configs are part of site files, the registry could be leveraged for these settings.
7/24/2014 03:57 PM
 · 
 
by
  
vivek-thakur
Vivek Thakur said:
Hi Tony,It's not only web.config, but all *config files (like CFAppSettings.config) and we basically want to avoid registry because of obvious issues dealing with system registries on different machines. Also, you will anyways need to have common "assets" folder because having a single copy of assets and lucene index is not recommended, so having a single copy of just "aspx/ascx" files will not make much sense. Anyways, I will discuss this with the team on how we can implement both options, having it in config as well as in registry.Thanks,Vivek
7/24/2014 05:53 PM
 · 
 
by
  
anubhavshah
Anubhav Shah said:
In particular RunBackgroundJobs key. The other values make sense in config file as they dont impact instances in the web farm. Does that make sense? If we can keep separate locations for assets folder, can we avoid any file lock issues? But could that result in more bugs and data ambiguity?
8/25/2014 07:45 PM
 · 
 
by

Pages

Intranet Software