For more information, see Monitor content you distribute. To verify that the content files for a package are available on the content-enabled CMG, go to the Content Status node in the Monitoring workspace. When you select a package, you can redistribute or remove the content files. See how much space each package uses in the storage account. View the packages that are assigned to the cloud storage account for this CMG. For more information, see Monitor the CMG: Set up outbound traffic alerts. Reconfigure the alerts at any time after you create the CMG. If you plan on targeting deployments with content to clients, you need to configure the CMG to serve content. For more information, see How to enable TLS 1.2.Īllow CMG to function as a cloud distribution point and serve content from Azure storage: The CMG enables this option by default. Starting in version 2107 with the update rollup, this setting also applies to the CMG storage account. Require it to use the TLS 1.2 encryption protocol. For more information, see Publish the certificate revocation list.Įnforce TLS 1.2: The CMG enables this option by default. Verify Client Certificate Revocation: If you didn't originally enable this setting when you created the CMG, you can enable it afterwards after you publish the CRL. This option is useful when adding new CAs, or retiring expired certificates. This setting allows you to dynamically scale the service up or down based on usage or cost considerations.Ĭertificates: Add or remove trusted root or intermediate CA certificates. VM Instance: Change the number of virtual machines that the service uses in Azure. For example, changing the organization name on the certificate.ĭescription: Specify an optional description to further identify this CMG in the Configuration Manager console. If you make significant changes to the certificate, you may need to Redeploy the service. The wizard won't accept a certificate with the CN. For example, if the CN of the current certificate is, create the new certificate with the same lowercase CN. # List all the topics whether they are replicated or notīash /usr/hdp/current/kafka-broker/bin/kafka-topics.sh -zookeeper $KAFKAZKHOSTS -listīash /usr/hdp/current/kafka-broker/bin/kafka-console-consumer.When you renew the server authentication certificate for the CMG, the FQDN that you specify for the certificate's common name (CN) is case-sensitive. 現在,在 中啟動取用者 SECONDARYCLUSTER export clusterName='secondary-kafka-cluster' 現在開始製作者 PRIMARYCLUSTER export clusterName='primary-kafka-cluster'īash /usr/hdp/current/kafka-broker/bin/kafka-console-producer.sh -broker-list $KAFKABROKERS -topic $TOPICNAME 在 中 SECONDARYCLUSTER 啟動 Mirror Maker2,它應該會正常執行 /usr/hdp/current/kafka-broker Secondary-kafka-cluster->primary-kafka-cluster.topics =. Primary-kafka-cluster->secondary-kafka-cluster.topics =. Secondary-kafka-cluster->primary-kafka-cluster.enabled = true Primary-kafka-cluster->secondary-kafka-cluster.enabled = true "A_host1:9092, A_host2:9092, A_host3:9092" and you can see the exact host name on Ambari -> Hosts 變更之後的最終組態檔看起來應該像這樣 # specify any number of cluster aliasesĬlusters = primary-kafka-cluster, secondary-kafka-cluster # Setting replication factor of newly created remote topics # regex which defines which topics gets replicated. # enable and configure individual replication flows # This is a comma separated host:port pairs for each cluster # connection information for each cluster 屬性檔看起來像這樣。 # specify any number of cluster aliases
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |