Hello Yehuda,
Thanks for your response.
I'm still confused with log files. Say load balancer now put us on hot
standby node. We already have some logs ( both access and error) at
master node. How can we get all those logs as soon as we are on hot
standby ? We need unique log files for produc
On Mon, Feb 15, 2016 at 9:24 AM, Bob wrote:
> The challenge is to maintain unique web server log across the nodes. Any
> clue about that ?
> Again for pages which send emails, all nodes must have running postfix
> with same domain.
> I'm also wondering how to do that.
>
To keep the configuration
Dear John,
Thank you for sharing the ideas. Well, my servers are running with
Linux. Hence haproxy with failover come closer to the requirement. As
per the links you shared, seems DNS route with two load balancing can
do the job. four servers are required in total.
The challenge is to maint
Bob,
simple diagram for what you are looking for:
http://www.1stserv.com/images/Load-balancer-Setup1.png
And here is a more detailed document:
https://f5.com/resources/white-papers/load-balancing-101-nuts-and-bolts
If you're using MS Windows Server to host your Apache Servers you can look
into
Hello John,
Could you please give me some more clue / pointers/ link ?
Please allow me repeating my questions again
What can be done to assure the high-availability of the reverse proxy
itself ?
What about the latency if the master and hot standby located in two
different data center ?
O
We have it implemented using and external, redundant , load balancer.
It really comes down to your budget.
John
On Mon, Feb 15, 2016 at 8:58 AM, Bob wrote:
> Hello,
>
> Thanks for the valuable suggestions.
>
> What can be done to assure the high-availability of the reverse proxy
> itself ?
> Wh
Hello,
Thanks for the valuable suggestions.
What can be done to assure the high-availability of the reverse proxy
itself ?
What about the latency if the master and hot standby located in two
different data center ?
On Sunday 14 February 2016 10:43 PM, Yehuda Katz wrote:
We use three diffe
We use three different methods:
1. Content on NFS server
2. Content auto-committing and auto-pulling over git about every 15 minutes
3. Separate database server - with replication for backup.
- Y
Sent from a device with a very small keyboard and hyperactive autocorrect.
On Feb 14, 2016 5:28 PM, "
What is your preferred approach to keeping content in sync?
Sent from my iPad
On Feb 14, 2016, at 3:47 PM, Daniel
mailto:dferra...@gmail.com>> wrote:
with a reverse proxy in front of both, you use balancer setup specifying the
second web server as hot standby
El dom., 14 feb. 2016 a las 16:49
with a reverse proxy in front of both, you use balancer setup specifying
the second web server as hot standby
El dom., 14 feb. 2016 a las 16:49, Bob () escribió:
> Hello list,
>
> I have two servers. One is already up with apache, mysql etc..
> Now I wonder if I can configure the second server as
Hello list,
I have two servers. One is already up with apache, mysql etc..
Now I wonder if I can configure the second server as a fallback web server.
The idea is.. if first web server is down , the second one will serve
the requests.
Any suggestion / idea is very much welcome.
Thanks and reg
11 matches
Mail list logo