反馈已提交

网络繁忙

You are viewing 5.1 help doc. More details are displayed in the latest help doc.

Web cluster environment preparation

  • Recent Updates: October 20, 2022
  • 1. System Requirements

    It is known that load balancing Nginx does not support high concurrency on Windows Server, so for solutions that use Nginx as load balancing, if the concurrency demand is below 300, the cluster can be deployed normally on both Linux systems and Windows Server, and if the concurrency demand is above 300, it is not recommended to deploy the cluster on Windows Server, otherwise concurrency problems will occur.

    Type

    Operating System

    Verified version 

    LinuxCentos6  Centos 6.5、Centos 6.6、Centos 6.7、Centos 6.8、Centos 6.9
    Centos7Centos 7.0、Centos 7.1、Centos 7.2、Centos 7.3、Centos 7.4
    RedHat6RedHat 6.5、RedHat 6.6、RedHat 6.7、RedHat 6.8、RedHat 6.9
    RadHat7RedHat 7.0、RedHat 7.1、RedHat 7.2、RedHat 7.3、RedHat 7.4
    Ubuntu10Ubuntu 10.04.4
    Amazon LinuxAmazon Linux AMI release 2018.03
    windowsWindows ServerWindows Server 2008、Windows Server 2012

    (1) JDK version requirements: JDK 1.8 and minor versions need to be above JDK8u102.

    (2) A set of clusters does not support a server to deploy multiple clusters of node projects.

    (3) Need to confirm that the projects communicate properly with each other and with the external database.

    Notes.

    • Linux system users: you can use the cluster environment detection tool to automatically detect the system environment, or use the ping statement to detect.

    • Windows system users: use ping or telenet statement to detect.

    2.ROOT authorization

    Linux systems require the top user (root) to install FTP, otherwise it cannot be done, but this requirement can be ignored if FTP is not installed.

    3. GCC Compilers

    Both Redis and Nginx rely on the GCC compiler for deployment on Linux systems, so please note that if you choose a Linux server, please ensure that your system has a GCC compiler environment

    Query command: gcc -v, if you do not have a gcc environment, you need to install it yourself, network installation command:yum install gcc gcc-c++

    4. Network requirements

    Clusters can be deployed in both public and intranet environments, although a good communication environment between the servers in the cluster is required, as follows.

    TypeBandwidthNetwork segmentNote
    Public Network10M or moreSame network segment/
    IntranetNo requirementSame network segmentThe intranet is generally 100 gigabit/gigabit bandwidth, so there is no requirement for bandwidth

    5. Machine Requirements

    Currently, a two-node cluster base solution (Nginx+Tomcat+Redis+ftp) is more commonly used, and we use this as an example to illustrate the requirements for the server.

    5.1 Number of Servers

    For a cluster scenario with two nodes deployed, it is recommended to prepare three servers with the following architecture.

    Application Server 1Web containers (Tomcat, WebLogic, WAS)
    Application Server 2Web containers(Tomcat、WebLogic、WAS)

    Load Balancing (Nginx)
    State Server (Redis)
    File Server (FTP)

    5.2 Memory Configuration

    Server
    System MemoryAllocated to Web container JVM memory
    Application Server16G or more recommended

    Recommend 8G or more, not more than 32G, too big will cause the system FullGC time is too long长

    Component Server8G or more recommended/

    5.3 Disk Space

    Deploying a cluster project requires at least 40G of free space in the root directory of each machine, and if the template resource file is large, choose a server with larger disk space according to the actual situation.

    MachineRoleHardwareConfigurationDescription
    Application Server 1Deployment Projects/(Root directory)Guaranteed free space of at least 40GTemporary cache address in use by the system
    Application Server 2/usrGuaranteed free space of at least 15GDefault log storage path
    Component Server 3Deploying Cluster Components/(Root directory) Guaranteed free space of at least 40GTemporary cache address in use by the system
    /usrGuaranteed free space of at least 15GInstall the various components of the cluster and store the log files
    /homeGuaranteed free space of at least 10GFile server storage directory for resource files such as templates

    6. Port Preparation

    CategoryContentPortNote
    Loading BalancingNginx80or443The external port, which must be open to the public, can be modified (nginx.conf) and is the entry port for the cluster system, please configure the other load balancing ports yourself
    web containerTomcat8080External ports, not open to the public, can be modified (server.xml), SSL, short addresses, etc. configured at the load balancing level
    WebLoigc7001
    WebSphere9080
    Message NotificationWebsocket port["48888", "49888"]

    For more information, please see: Cluster Configuration WebSocket Port

    Websocket Forwarding port48889
    File ServerFTP20、21Internal port, modifiable (self-operated)
    SFTP22Internal port, not modifiable
    HDFS
    9000Internal port, modifiable (self-operated)
    Status Serverredis standalone6379Internal port, modifiable (redis.conf)
    redis cluster/Internal port, modify it yourself according to the configuration (redis.conf)

    Notes:

    • 1) Web container, file server and state server contain many kinds, please open the ports by yourself according to the selection.

    • 2)If the default port conflicts with other projects, you need to modify the port first, and then open the corresponding port.

    • 3) Open port 21 and any port larger than 1024, and then open ftp passive mode through passive.

    • 4) For docker containers, or environments with strict port restrictions between servers, you need to open ports between servers of nodes for inter-node communication.

    • Select TCP protocol is 7800/7810/7820/7830/7840/7850/7860/7870 eight ports

    • Select UDP protocol is 45588~65536 random ports

    7. Direct connection configuration recommendations

    CPUOrder of magnitudeMemoryEdit user concurrencyTotal user concurrency
    Number of physical coresNumber of logical coresNumber of cells in the result set (rows*columns)Complete machineJVMStand-aloneDual NodeTripleNodeStand-aloneDual NodeTriple Node
    8165 million128204050150250300
    81610 million3216305060200250
    163210million3216405060300500800
    163250 million6432405060300500800

    Notes:

    A large number of calculations are done by the database, and BI memory consumption is mainly related to result set size and concurrent performance.

    If virtual machines are used, the number of cores and logical cores are kept consistent.

    The number of nodes increases concurrent performance improvement is more obvious, support expansion nodes, the bottleneck of maximum concurrency is mainly in the configuration read.

    Edit user concurrency: users who do datasets/dashboards.

    Total user concurrency: editing + preview users. ( For example, 150 concurrent users under 8 cores and 16G memory. Means maximum 150 users of which editing users are maximum 20 other are preview users )



    Attachment List


    Theme: Deployment Integration
    Already the First
    Already the Last
    • Helpful
    • Not helpful
    • Only read

    售前咨询电话

    400-811-8890转1

    在线技术支持

    在线QQ:800049425

    热线电话:400-811-8890转2

    总裁办24H投诉

    热线电话:173-1278-1526

    文 档反 馈

    鼠标选中内容,快速反馈问题

    鼠标选中存在疑惑的内容,即可快速反馈问题,我们将会跟进处理。

    不再提示

    10s后关闭