Use Restrictions

Pay attention to the following restrictions before you use CloudTable.

• CloudTable clusters must be created in VPC subnets.
• You are advised to use one of the following browsers to log in to the CloudTable management console.
  • Chrome 36.0 or later
  • Mozilla Firefox 35.0 or later
  • Internet Explorer 9.0 or later

    If you use Internet Explorer 9.0, you may fail to log in to the CloudTable management console because user Administrator is disabled by default in some Windows systems, such as Windows 7 Ultimate. The Internet Explorer automatically selects a system user for installation. As a result, the Internet Explorer cannot access the management console. Reinstall Internet Explorer 9.0 or later (recommended) or run Internet Explorer 9.0 as user Administrator.

  • Edge: 13.0 or later
• When you create a CloudTable cluster, the system will create a default security group. Do not delete or change the default security group. Deleting or changing the default security group may cause a cluster exception and affect the use of CloudTable clusters.
• Do not assign the access permission for security groups used by CloudTable to prevent malicious access.
• CloudTable does not save the initial password you set for logging in to a node. Please set and keep the password. To prevent malicious attacks, you are advised to set a password with a high complexity.
• Cluster nodes are used only for running CloudTable clusters. You are advised to apply for an independent ECS to deploy your other client applications and business applications.
• Currently, CloudTable does not have a security authentication mechanism. If HBase with an authentication mechanism is required, you are advised to use the HBase component in MRS.
• When creating a table in ClickHouse, it is advised to employ the Replicated series engines to enhance data reliability. Again, cloud services disclaim liability for any data loss or damage arising from a single backup.
• Do not enable the MOB feature for the HBase service in the CloudTable cluster. Using this feature may lead to table data read failure and JVM crash.

  For existing HBase tables, run the following command in the command line hbase shell to check whether the table description contains the keyword MOB. If it is contained, contact O&M engineers to set the table non-MOB.

  desc 'Table name'

  For example, if the value of IS_MOB is true in the following command output, the HBase MOB feature is enabled:

  hbase:009:0> desc 't3'
  t3
  COLUMN FAMILIES DESCRIPTION
  {NAME => 'd', MOB_THRESHOLD => '102400', VERSIONS => '1', KEEP_DELETED_CELLS => 'FALSE', DATA_BLOCK_ENCODING => 'NONE', TTL => 'FOREVER', MIN_VERSIONS => '0', REPLICATION_SCOPE => '0', BLOO
  MFILTER => 'ROW', IN_MEMORY => 'false', IS_MOB => 'true', COMPRESSION => 'NONE', BLOCKCACHE => 'true', BLOCKSIZE => '65536'}

• In the cold and hot data separation scenario, hot disks do not support scale-in.
• ClickHouse does not support the JSON and Object('json') data types.