Deployment

All deploying files at inlong-dataproxy directory.

Configuration

Configure InLong-Manager URL

configuration file: conf/common.properties:

  1. # manager address
  2. manager.hosts=127.0.0.1:8083
  3. # audit proxy address
  4. audit.proxys=127.0.0.1:10081

run

  1. # Default using Pulsar to cache data, and the dataproxy-pulsar.conf configuration file is loaded.
  2. bash +x bin/dataproxy-start.sh
  3. # or
  4. bash +x bin/dataproxy-start.sh pulsar
  5. # If using Inlong TubeMQ to cache data
  6. # bash +x bin/dataproxy-start.sh tube

check

  1. telnet 127.0.0.1 46801

Add DataProxy configuration to InLong-Manager

After installing the DataProxy, you need to add the IP of the DataProxy service into the InLong-Manager. Modify the following information and execute command:

  1. curl --header "Content-Type: application/json" --request POST http://your_manager_host:8083/api/inlong/manager/openapi/cluster/save --data '
  2. {
  3.    "name": "default_dataproxy",
  4.    "type": "DATA_PROXY",
  5.    "ip": "your_dataproxy_ip",
  6.    "port": 46801,
  7.    "mqSetName": "default_set_name",
  8.    "inCharges": "admin",
  9.    "creator": "admin"
  10. }
  11. '

  • Please modify the ip field to the real IP (or hostname) of the DataProxy, the format is node1:port1,node2:port2, and separate them with ,.

  • If all nodes in the ip field have the same port, you can use node1,node2 and modify the port field to the default port for those nodes.