Scalr creates DNS records for your DB roles as follows: int-<db role name>.<domain>.com or ext-<db role name>.domain.com for internal and external ip addresses respectively. These hostnames can even be resolved from your own desktop machine (which bothers me but that is another story). Because they can be resolved from just about anywhere, any instance that you create will also be able to connect to them.
Short answer: No, nothing should be required to connect to them. Akshay On Fri, Jul 10, 2009 at 4:58 PM, kenvogt <[email protected]> wrote: > > Excellent. Does anything special have to be done to make it them > accessible to each other? > > On Jul 10, 12:47 pm, Frédéric Sidler <[email protected]> > wrote: > > there is a penalty if the instances are not located in the same area > (zone) > > otherwise there is no penalty > > > > > > > > On Fri, Jul 10, 2009 at 6:56 PM, kenvogt<[email protected]> wrote: > > > > > So is there a performance penalty for the app server of one farm > > > connecting to a database server on another farm? Does anything special > > > have to be done to make it them accessible to each other? > > > > > On Jul 10, 4:47 am, Nickolas Toursky <[email protected]> wrote: > > >> One master per farm. > > >> AFAIK, community members achieve this with farm-per-shard setup. > > > > >> 2009/7/9 kenvogt <[email protected]>: > > > > >> > I am curious, since Scalr only allows one master msql server, how > are > > >> > you sharding your database? Don't you require 12 masters? > > > > >> > On May 23, 5:21 pm, Rod Frey <[email protected]> wrote: > > >> >> OK, must be an AWS problem then. They claimed they bumped my > limit, > > >> >> perhaps they didn't or did it on the wrong account. > > > > >> >> On May 23, 3:37 pm, Alex Kovalyov <[email protected]> wrote: > > > > >> >> > We're making plain API calls. and would never set any limits. > > >> >> > Please describe an issue in detail. You may use > [email protected] if > > >> >> > any confidential details involved. > > > > >> >> > On Sat, May 23, 2009 at 6:58 PM, Rod Frey <[email protected]> > wrote: > > > > >> >> > > Hi. I'm building out a shard-based database system... we have > lots of > > >> >> > >shards(12) each of which has a 1TB EBS volume attached to it. > > >> >> > > There's an associated slave, also with a 1TB EBS volume. > > > > >> >> > > Amazon has increased my EBS volume limit to 60, but Scalr.net > doesn't > > >> >> > > seem to pick up on that. I found a place to modify the number > of EC2 > > >> >> > > instances I have, but not EBS volumes. > > > > >> >> > > Is there an issue on Amazon, or is this just an overlooked > field in > > >> >> > > the settings? > > > > >> >> > > Rod > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
