Jump to content

Search the Community

Showing results for tags 'highload'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • uniGUI Public
    • Announcements
    • General
    • Feature Requests
    • Installation
    • Deployment
    • Other Platforms
  • Licensing
    • Licensing
    • Ordering uniGUI
  • Bug Reports
    • Active Reports
    • Closed Reports
    • Old Bug Reports
  • uniGUI Development
    • General Development
    • uniGUI Releases & Roadmaps
    • Utilities
  • Mobile Platform
    • uniGUI Mobile
    • Mobile Browsers
  • Users Area
    • Sample Projects
    • Components and Code Samples
    • Third Party Components
  • Non-English
    • Non-English
  • Miscellaneous
    • Hosting
    • Server Security
    • Jobs

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Hi. We want to deploy our application on several datacenters, we are going to use the popular multiIP DNS routing(LoadBalancing) approach used for example in Google or large companies. Ie, when a user sends an NS request, the nearest (one of the IP addresses) is returned to him via DNS, thereby the user will get to one of our datacenters (in Lithuania, Finland, Russia, etc.).. In each of the datacenters there are several hyper_server instances with VRRP(keepAlived) – a common IP, if one of the hyper_server instances refuses VIP service, the second instance will be responsible, while it will access the same nodes (slave) the same as the first one. Because we plan to use the Rewrite load balancing mod and assign a unique white address to each working node (slave). I.e. users come with NS: mydomain.com Mydomain.com these are 3 IP addresses (different datacenters): { 1. XXX.XXX.XXX.XXX – Finland(a) 2. XXX.XXX.XXX.XXX – Lithuania(b) 3. XXX.XXX.XXX.XXX – Russia © } DataCenter #1(a) (for example Finland): Common IP master – mydomain.com = XXX.XXX.XXX.XXX – Finland { Master#1 – keepAlived IP – Active Master#2 – keepAlived IP – Reserve Master#3 – keepAlived IP – Reserve } All master servers within the datacenter have the same configuration for working nodes (slave): [server-0], [server-1],[server-2],[server-3]..[server-n] In Finland (slave), the nodes will be as follows: Slave – subdomain.mydomain.com = XXX.XXX.XXX.XXX – Finland { Slave #1 - a0.mydomain.com Slave #2 – a1.mydomain.com Slave #3 – a2.mydomain.com Slave #4 – a3.mydomain.com ... n } (If one of the slave servers falls, it's not as scary as if the master falls and the automatic reserve does not rise.) Then, of course, there is a VRRP for several PgBouncer (for a single pool of DBMS connections), followed by DBMS clusters with sharding and replication. (with auto-failower) All this architecture is not problematic except for one issue: Will we be able to organize a hot backup via master hyper_server via VRRP? Did someone do it? How to automatically raise another master nearby (with the same IP – VIP)(he will immediately pick up all the nodes(slave VM)), does anyone have experience?
×
×
  • Create New...