Open topic with navigation

TIBCO ActiveSpaces® - Enterprise Edition 5.0.0

# Administrative Concepts

These concepts and definitions pave the way to a more detailed understanding of ActiveSpaces administration.

Data Grid

A set of cooperating processes that distribute data across a set of host computers.

Three kinds of cooperating processes implement a data grid: nodes, proxies, and state keepers.

Copyset

A data grid partitions the complete set of data into copysets. Each copyset contains a portion of the full data set.

Each table row resides within only one copyset.

Partitioning

The data grid horizontally partitions the rows of a table across copysets. So, a query or a transaction can span many copysets.

Node

Nodes are processes that implement a copyset. Administrators define nodes and assign them to copysets.

Each copyset requires a primary node. Secondary nodes can provide optional backup protection.

Each node of a copyset maintains one copy of the data (that is, one copy of all the rows in that copyset).

Each node is part of only one copyset.

Replica
The number of replicas in a copyset is identical to the number of nodes that implement that copyset. Replicas provide fault tolerance and protect data against hardware failures. More replicas yield greater protection.

- In a prototyping or testing environment, you can implement a copyset using only one node.
- In most production environments, two nodes provide adequate protection.
- For even stronger fault tolerance, you can use three nodes.

Replication

The replication feature, when used, provides fault tolerance by preventing data loss when a node (or the computer running the node) fails and cannot be accessed.

All nodes in a given copyset are replicas of each other and they all have the same set of data.

There is a single primary replica in a copyset and the other nodes in that copyset are secondary replicas.

Every copyset in the data grid is organized to ensure that the slice of data owned by that copyset is stored on as many replicas as desired.

Reconciling Nodes of a Copyset

When a node of a copyset is brought back online, the data for the node is reconciled with the primary node. After reconciliation, the node being brought back online resumes as a secondary node of the copyset.

For more information, see Copysets.

Using Multiple Nodes
There are several reasons for using multiple nodes:

- Nodes in different copysets are created with the goal of scaling horizontally.

  As a result, multiple copysets are created, each with a slice of the data.

- Nodes in the same copyset are created to provide multiple replicas for fault tolerance.

  These contain identical copies of the data.

- In a product environment, a combination of the previously described use cases can be used.

  For example, you might choose to have two replicas per copyset and multiple copysets (say three) to scale horizontally.

  In this example, your environment would have a total of six nodes.

Proxy
Proxies are processes that mediate data grid operations on behalf of application programs.

Application programs connect to proxies, which in turn connect to nodes.

Proxy processes are independent of one another and do not require persistent state, so you can share the load of operations among multiple proxies.

State Keeper

Fault-tolerant state keeper processes determine and record the data grid's run time state information by which a data grid operates, and supply this information to the proxies and copyset nodes.

A set of fault-tolerant state keeper processes protect this crucial information and ensure nonstop access to it. One of the state keepers is designated the lead state keeper and supplies this information to the proxies and copyset nodes. If the lead state keeper goes down, one of the secondary state keepers takes over as the lead. In a fault-tolerant set of three state keepers, a quorum of two state keepers must always be running to ensure data consistency in split brain scenarios. If a state keeper is restarted when a quorum is running, one of the running state keepers updates the state of the restarted state keeper. If the number of running state keepers falls below the quorum and the state of a copyset changes (for example, a node goes down), operations on the data grid continue to fail until a quorum of state keepers are running again. Until a copyset state change occurs, live operations may still continue working. However, it is critical that a quorum of state keepers is running to provide the full grid functionality.

For more information, see State Keeper.

Service

You can configure a TIBCO FTL server to run one or more processes as services. When a process is run as a service, the TIBCO FTL server is responsible for starting and stopping the process when the TIBCO FTL server starts up and shuts down. The TIBCO FTL server continuously monitors the liveness of the process and restarts it if the process is not running. On starting, the YAML configuration file of the TIBCO FTL server provides the parameters to a service. For a standalone process, you add the process parameters by using command line. For the processes running as a service, add those parameters to the YAML configuration file of TIBCO FTL server. For example, if you used the following command to start a standalone state keeper:

    tibgdkeeper --name k1

When the state keeper is running as a service, add the following parameters to the YAML configuration file of the TIBCO FTL server:

    - tibdgkeeper:
    name: k1

You can run state keeper, administration service, and proxy as services.

ActiveSpaces Core Server

When you configure a TIBCO FTL server to run one or more ActiveSpaces processes, it is known as an ActiveSpaces Core Server.

Subtopics

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO ActiveSpaces® - Enterprise Edition

Copyright © 2009-2025. Cloud Software Group, Inc. All Rights Reserved.