Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Remove necessity for gossip router aka group-of-nodes approach

#6

If we run nodes without gossip router — communication between nodes fails, and each node would try to connect to gossip route which doesn't exists.

Invent some approach to have group-of-nodes instead of cluster-of-nodes if the gossip router isn't available. Maybe other JBoss configuration?

Reported by Deleted User · January 15th, 2009 @ 08:07 AM

State: resolved
Milestone: 1.0.0.Beta2
Assigned to: Deleted User Deleted User

Activity

  1. Deleted User
    Deleted User
    • State changed from new to open

    January 15th, 2009 @ 08:08 AM

  2. Deleted User
    Deleted User

    We can put two JBoss configurations to achieve this:

    • clustered,
    • non-clustered.

    Selection could be done via:

    1. Building two preconfigured RPMs,
    2. Using a tool to select run configuration at first boot (e.g. FirstBoot),
    3. Selecting a default configuration in RPMs, and allow change in configuration file (/etc/jboss-as5.conf).

    1st approach would create double RPMs for JBoss AS.

    2nd approach forces configuration for each node in the cluster for first time boot.

    3rd approach is simplest to do. Reasonable default configuration should be clustered, because this would be the most common use case for jboss-cloud.

    We can also remove other configurations to decrease appliance size.

    January 16th, 2009 @ 12:03 AM

  3. bob (at oddthesis)
    bob (at oddthesis)
    • Tag changed from gossip router, task to gossip router, clustering, jgroups, task

    With (1), we could still create a single RPM, it would just have additional profiles. server/all, server/all-clustered, server/default, server/default-clustered. That's still a lot of duplication of .jars and such under each profile. But AS 5.1 or 5.2 is supposed really cut down on that duplication.

    Either way, though, we still have to select the right config, so I don't know if that helps. At least we'd only have to have 1 jboss-as5-appliance.vmx, perhaps. Else, 2 RPMs == 2 spins of the appliance, too.

    (2) I think is right out, since it doesn't allow for lights-out booting up of a cluster. Adjusting jboss-as5.conf manually means we've failed.

    (3) I like, perhaps mixed with (1). Right now, for the cluster to form up, we have to pass boot metadata (via the VM2 or EC2 style of injection) to set the PROXY_LIST and GOSSIP_HOST sort of things.

    So I'm thinking /etc/jboss-as5.init should react appropriately to the existance or lack of GOSSIP_HOST. If GOSSIP_HOST is set, run -c all-clustered to use the clustering configuration. If GOSSIP_HOST is unset, run -c all, without the clustering.

    I'd also think of (4), which might be patches to things (like you did with mod_cluster proxyList) to allow for safe "failure" if things are not provided. ie, running with -c all should cluster if jboss.mod_cluster.proxyList and jboss.jgroups.host are set (or some reasonable properties). And should be a group-of-nodes, but still 100% functional, if one or both of those Java properties are not set.

    January 16th, 2009 @ 07:34 AM

  4. Deleted User
    Deleted User

    Reaction of /etc/init.d/jboss-as5 for GOSSIP_HOST sounds good.

    So, we make two profiles (is there need for more?). Name proposal:

    • cluster (aka all) with gossip router, cluster-of-nodes,
    • group (aka default) without gossip router, group-of-nodes.

    JBoss init script will check for existence GOSSIP_HOST variable and run appropriate profile.

    Ad 4. I don't know if this would be an good approach, because (if I understand it right) in that case we should patch JBoss AS. The mod_cluster patch is something other than that — mod_cluster is running in a selected and started profile. In that case problem is to select the right profile. Editing /etc/init.d/jboss-as5 and checking for variables would be better I think.

    January 16th, 2009 @ 08:12 AM

  5. bob (at oddthesis)
    bob (at oddthesis)
    • Tag changed from gossip router, clustering, jgroups, task to gossip router, clustering, jgroups, profiles, task

    Yep, cluster/group profiles sound good. Let's leave the all/minimal/default/web for now, so they're available if anyone wants them. But copying 'all' and modifying for our two configs sounds wise.

    January 16th, 2009 @ 08:14 AM

  6. bob (at oddthesis)
    bob (at oddthesis)

    (from [dec923de448f8483807d65aedc4f63fe281de558]) [#6] first steps in removing neccesity for gossip router, added jboss-as5-profiles spec file, modified patches http://github.com/bobmcwhirter/j...

    January 16th, 2009 @ 12:02 PM

  7. Deleted User
    Deleted User
    • Milestone set to 1.0.0.Beta2

    February 3rd, 2009 @ 12:46 AM

  8. Deleted User
    Deleted User
    • State changed from open to resolved

    Created a rpm for profiles called jboss-as5-cloud-profiles which holds jboss cloud profiles (cluster and group). Other JBoss AS are untouched. Selecting which profile is used is done in jboss as5 init script. Closing.

    February 3rd, 2009 @ 06:00 AM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.