Home > Blogs > VMware vFabric Blog


SQLFire Client HA Configuration

One of the most common misconceptions about the level of high availability provided by SQLFire is the client configuration. A lot of times, when people see the client connection string defined with a single IP, they assume that to mean that client will only communicate with that one SQLFire cluster host and deem that to be a single point of failure in the SQLFire data grid.

In reality however, SQLFire is based on multi-faced shared nothing architecture. One of its tenants is transparent failover at the protocol level.

Sqlfire-ha

When the client connects to the SQLFire locator, that locator serves as a facade for all other SQLFire data nodes. Locator also balances client requests to all SQLFire servers available in a cluster; so multiple connection requests to the same locator may result in connections to different data servers. (more on SQLFire failover and redundancy)

So, even though the client is configured with a single host and port, in case of a failure of one of the data nodes, the locator to which the client connects will redirect its connections to the next available cluster tenant.

Furthermore, in case of failure of the locator itself, the client driver internally will redirect its data connections to the next available locator and continue benefiting from the same load balancing services.

In short, the locator connection on the client is only a control connection to fetch server information. This is done dynamically whenever the cluster information is updated, as to assure that all cluster node information is always up to date.

This entire process is transparent to the client application and does not require changes to the connection string.

In short, to achieve highest level of HA, the recommended configuration for SQLFire cluster should:

  • Configure multiple locators in addition to data servers
  • Configure locators on a standalone machines, not on the same host as data server
  • Configure clients to connect to one of the standalone locators to achieve best durability of your connections

While it is possible to run SQLFire cluster without locator, for production environments the recommended configuration should include at least one standalone locator.

Separating locator from the SQLFire data servers, further increases the HA of the overall system. Since locators do not host data and have very little activity, they are unlikely to fail. Redundancy among locators themselves will further alleviate possibility of locator failures.

For detail description of connecting to a SQLFire cluster with the thin client please see on-line documentation

This entry was posted in SQLFire and tagged , , , , on by .
Mark Chmarny

About Mark Chmarny

During his 15+ year career, Mark Chmarny has worked across various industries. Most recently, as a Cloud Architect at EMC, Mark developed numerous Cloud Computing solutions for both Service Provider and Enterprise customers. As a Data Solution Evangelist at VMware, Mark works in the Cloud Application Platform group where he is actively engaged in defining new approaches to distributed data management for Cloud-scale applications. Mark received a Mechanical Engineering degree from Technical University in Vienna, Austria and a BA in Communication Arts from Multnomah University in Portland, OR.

22 thoughts on “SQLFire Client HA Configuration

  1. salinasqswd.deviantart.com

    Link exchange is nothing else except it is only placing the other person’s webpage link
    on your page at proper place and other person will also do similar in favor of you.

    Here is my web site; best ecig reviews; salinasqswd.deviantart.com,

    Reply
  2. اخبار اجتماعی

    and have very little activity, they are unlikely

    Reply
  3. نرم افزار روز

    e is actively engaged in defining new

    Reply
  4. اخبار حوادث

    Cloud Application Platform group where he is actively engaged in defining new approaches to distributed data management for

    Reply
  5. اخبار روز موبایل

    tion should include at least one standalone locator.

    Reply
  6. اخبار ورزشی

    in the Cloud Application Platform group

    Reply
  7. اخبار های روز فناوری

    works in the Cloud Application Platform group where he is actively engaged in defining new approaches to distributed

    Reply
  8. مطالب و جزوه های تحقیقاتی

    where he is actively engaged in defining new approaches to distributed data management

    Reply
  9. خبرهای سیاسی ایران و جهان

    This entry was posted in SQLFire and tagged cluster

    Reply
  10. بازی های رایانه ای

    Service Provider and Enterprise customers

    Reply
  11. بین الملل

    creases the HA of the overall system. Since locators

    Reply
  12. آموزش برنامه نویسی

    creases the HA of the overall system

    Reply
  13. مدلباس

    Redundancy among locators themselves will further alleviate possibility of locator failures.

    Reply
  14. بازارموزیک

    Data Solution Evangelist at VMware

    Reply
  15. گرافیک و کاریکاتور

    One of its tenants is transparent failover at the protocol level.

    Reply
  16. دنیای اقتصاد

    works in the Cloud Application Platform group

    Reply
  17. دانستنی ها

    While it is possible to run SQLFire cluster without locator

    Reply
  18. اخبار خودرو

    Link exchange is nothing else except

    Reply
  19. اخبار هنرمندان

    worked across various industries. Most recently, as a Cloud Architect at EMC, Mark developed numerous Cloud Computing solutions for both Service Provider and Enterprise customers.

    Reply
  20. اخبارتجارت

    on your page at proper place and other person will also do similar in favor of you.

    Reply
  21. اخبار فضای مجازی

    Separating locator from the SQLFire data servers, further increases the HA of the overall system. Since locators do not host data and have very little activity

    Reply
  22. کاندوم خاردار

    دانلود آهنگ

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

*