Change Password

Please enter the password.
Please enter the password. Between 8-64 characters. Not identical to your email address. Contain at least 3 of: uppercase, lowercase, numbers, and special characters.
Please enter the password.
Submit

Change Nickname

Current Nickname:
Submit

Apply New License

License Detail

Please complete this required field.

  • Ultipa Graph V4

Standalone

Please complete this required field.

Please complete this required field.

The MAC address of the server you want to deploy.

Please complete this required field.

Please complete this required field.

Cancel
Apply
ID
Product
Status
Cores
Applied Validity Period(days)
Effective Date
Excpired Date
Mac Address
Apply Comment
Review Comment
Close
Profile
  • Full Name:
  • Phone:
  • Company:
  • Company Email:
  • Country:
  • Language:
Change Password
Apply

You have no license application record.

Apply
Certificate Issued at Valid until Serial No. File
Serial No. Valid until File

Not having one? Apply now! >>>

Product Created On ID Amount (USD) Invoice
Product Created On ID Amount (USD) Invoice

No Invoice

v5.0
Search
    English
    v5.0

      Shard Servers

      Overview

      The Shard Servers is a crucial component of the Ultipa Powerhouse (v5) architecture, typically comprising multiple servers dedicated to distributed graph storage and computation. This design enables horizontal scaling while delivering highly competitive performance.

      Each shard supports multi-replica data storage. In the three-shard setup below, shards 1 and 2 each have three replicas, while shard 3 has two replicas. Graphsets are distributed across these shards, with Graph_1 stored in all three shards, Graph_2 and Graph_3 partially stored across the three shards, and Graph_4 located in a single shard.

      You can project graphsets from the physical storage of the shard servers into their memory, resulting in what are known as distributed projections. These projections allow graph algorithms to execute with improved performance.

      Showing Shard Servers

      Retrieves information about all shard servers:

      show().shard()
      

      The details returned for each shard server include:

      Field
      Description
      shardId The unique identifier, typically numbered sequentially (1, 2, 3, ...), of each shard server.
      shardStatus Current state of the shard server, which can be ACTIVE or DEAD.
      replicas The replicas of the shard server. Each replica includes:
      • status: The current status of the replica, which can be ACTIVE or DEAD.
      • addr: The IP address and port of the replica.
      • streamAddr: The IP address and port of the stream service of replica.
      • lastHeartbeatTime: The timestamp of the last heartbeat sent to the meta servers by the replica.

      Adding a Shard Server

      After successfully deploying a new shard server, it must be registered with the meta servers using the alter().shard().add() statement before it can be utilized. This process ensures that the new shard server is recognized within the system.

      The following example adds a shard server 4 with three replicas:

      alter().shard().add({
        shardId: 4,
        replicas: [
          {addr: "127.0.0.1:40061", streamAddr: "127.0.0.1:40023"},
          {addr: "127.0.0.2:40061", streamAddr: "127.0.0.2:40023"},
          {addr: "127.0.0.3:40061", streamAddr: "127.0.0.3:40023"}
        ]
      })
      

      Deleting a Shard Server

      You can unregister an inactive or obsolete shard server from the meta servers using the alter().shard().delete() statement.

      The following example deletes the shard server with the shardId 1:

      alter().shard().delete({shardId: 1})
      
      Please complete the following information to download this book
      *
      公司名称不能为空
      *
      公司邮箱必须填写
      *
      你的名字必须填写
      *
      你的电话必须填写