stomp_interface来自哪里?

时间:2016-10-30 16:09:25

标签: datastax-enterprise

为了在OpsCenter和DSE节点之间启用https通信,我必须在每个节点上的/var/lib/datastax-agent/conf/address.yaml中将stomp_interface设置为opscenter.mydomain.com。 (修复之后,我不再需要这样做了。)

每当我从OpsCenter执行配置作业时,它会将此stomp_interface值更改回nn.nn.nn.nn. (在修复之后,它仍然会这样做,但它不再破坏代理HTTP通信。)

此参数来自哪里?我可以在/etc/opscenter/clusters/cluster_name.conf文件的OpsCenter节点上进行设置吗?

它是[agent]部分的一部分吗?

我应该添加什么参数名称和值?

现在

opscenterd(修复是添加incoming_interface行):

# opscenterd.conf
[webserver]
port = 8888
interface = 0.0.0.0

ssl_keyfile = /var/lib/opscenter/ssl/opscenter.key
ssl_certfile = /var/lib/opscenter/ssl/opscenter.pem
ssl_port = 8443

[authentication]
enabled = True

[stat_reporter]

[agents]
use_ssl = true
incoming_interface = opscenter.mydomain.com
修复前的

address.yaml:

use_ssl: 1
stomp_interface: 1.2.3.4 (the opscenter external IP.
                          opscenter.mydomain.com also works)
stomp_port: 61620
local_interface: 2.3.4.5 (the external IP for this cluster node)
agent_rpc_interface: 0.0.0.0
agent_rpc_broadcast_address: 2.3.4.5
poll_period: 60
disk_usage_update_period: 60
rollup_rate: 200
rollup_rate_unit: second
jmx_host: 127.0.0.1
jmx_port: 7199
jmx_user: someuser
jmx_pass: somepassword
status_reporting_interval: 20
ec2_metadata_api_host: 169.254.169.254
metrics_enabled: true
jmx_metrics_threadpool_size: 5
hosts: ["2.3.4.5", "3.4.5.6", "4.5.6.7", "5.6.7.8"]
cassandra_port: 9042
thrift_port: 9160
cassandra_user: someuser
cassandra_pass: somepassword
runs_sudo: true
cassandra_install_location: /usr/share/dse
cassandra-conf: /etc/dse/cassandra/cassandra.yaml
cassandra_binary_location: /usr/bin
cassandra_conf_location: /etc/dse/cassandra
dse_env_location: /etc/dse
dse_binary_location: /usr/bin
dse_conf_location: /etc/dse
spark_conf_location: /etc/dse/spark
monitored_cassandra_user: someuser
monitored_cassandra_pass: somepassword
tcp_response_timeout: 120000
pong_timeout_ms: 120000

cluster_name.conf(我更新了seed_hosts以匹配address.yaml hosts配置中的那些,以满足最佳实践警报 他们应该都是一样的):

[destinations]
active =

[kerberos]
default_service =
opscenterd_client_principal =
opscenterd_keytab_location =
agent_keytab_location =
agent_client_principal =

[agents]
ssl_keystore_password =
ssl_keystore =

[jmx]
password = somepassword
port = 7199
username = someuser

[cassandra]
ssl_truststore_password =
cql_port = 9042
seed_hosts = 2.3.4.5, 3.4.5.6, 4.5.6.7, 5.6.7.8
username = someuser
password = somepassword
ssl_keystore_password =
ssl_keystore =
ssl_truststore =

1 个答案:

答案 0 :(得分:0)

根据你对评论的进一步信息,我想出来了。

我将incoming_interface = opscenter.mydomain.com添加到opscenterd.conf的[agents]部分。 (在Markc评论之前,这还不存在。)

我重启了服务opscenterd。

接下来,我可以返回到OpsCenter LifeCycle Manager并在群集上执行全新的安装和配置,并且所有作业步骤都已成功完成。

(注意:不要更改节点上的机架名称与之前的机架名称,并在配置/安装请求中选择autoBootStrap = true。)

datastax-agents完全Up并且处于活动状态。在配置和安装之后,address.yaml文件包含OpsCenter节点的公共IP地址作为stomp_interface。 (我手动将一个stomp_interface更改为opscenter.mydomain.com,这也有效。)

我还会编辑问题并发布所要求的信息。

谢谢markc!