forked from docs/doc-exports
DMS DEVG 20230612 version
Reviewed-by: Antonova, Ekaterina <ekantono@noreply.gitea.eco.tsi-dev.otc-service.com> Co-authored-by: Chen, Junjie <chenjunjie@huawei.com> Co-committed-by: Chen, Junjie <chenjunjie@huawei.com>
This commit is contained in:
parent
c7cf8ac24f
commit
5bb11b7c7f
File diff suppressed because it is too large
Load Diff
@ -1,6 +1,6 @@
|
||||
[
|
||||
{
|
||||
"desc":"Kafka instances are compatible with Apache Kafka and can be accessed using open-source Kafka clients. To access an instance in SASL mode, you will also need certificates.",
|
||||
"desc":"Kafka instances are compatible with Apache Kafka and can be accessed using open-source Kafka clients. In addition, if Security Protocol is set to SASL_SSL, use the DMS ce",
|
||||
"product_code":"dms",
|
||||
"title":"Overview",
|
||||
"uri":"Kafka-summary.html",
|
||||
@ -9,7 +9,7 @@
|
||||
"code":"1"
|
||||
},
|
||||
{
|
||||
"desc":"Instance connection address and portAfter an instance is created, you can obtain the IP address from the Basic Information tab page of the instance. You can configure all",
|
||||
"desc":"Before accessing a Kafka instance for message production and consumption, obtain the following information of the instance.Obtain them from the Basic Information page on ",
|
||||
"product_code":"dms",
|
||||
"title":"Collecting Connection Information",
|
||||
"uri":"Kafka-config.html",
|
||||
@ -45,7 +45,7 @@
|
||||
"code":"5"
|
||||
},
|
||||
{
|
||||
"desc":"This section describes how to access a Kafka premium instance using a Kafka client in Python on the Linux CentOS, including how to install the client, and produce and con",
|
||||
"desc":"This section takes Linux CentOS as an example to describe how to access a Kafka instance using a Kafka client in Python, including how to install the client, and produce ",
|
||||
"product_code":"dms",
|
||||
"title":"Python",
|
||||
"uri":"kafka-python.html",
|
||||
@ -54,7 +54,7 @@
|
||||
"code":"6"
|
||||
},
|
||||
{
|
||||
"desc":"This section describes how to access a Kafka instance using Go 1.16.5 on the Linux CentOS, how to obtain the demo code, and how to produce and consume messages.Before get",
|
||||
"desc":"This section takes Linux CentOS as an example to describe how to access a Kafka instance using a Kafka client in Go 1.16.5, including how to obtain the demo code, and pro",
|
||||
"product_code":"dms",
|
||||
"title":"Go",
|
||||
"uri":"kafka-go.html",
|
||||
@ -71,15 +71,6 @@
|
||||
"p_code":"",
|
||||
"code":"8"
|
||||
},
|
||||
{
|
||||
"desc":"Producer parametersAllow for retries in cases where messages fail to be sent.For example, allow for three retries by setting the value of retries to 3.The producer cannot",
|
||||
"product_code":"dms",
|
||||
"title":"Recommendations on Client Usage",
|
||||
"uri":"Kafka-client-optimize.html",
|
||||
"doc_type":"devg",
|
||||
"p_code":"",
|
||||
"code":"9"
|
||||
},
|
||||
{
|
||||
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
|
||||
"product_code":"dms",
|
||||
@ -87,6 +78,6 @@
|
||||
"uri":"kafka-devg-0407002.html",
|
||||
"doc_type":"devg",
|
||||
"p_code":"",
|
||||
"code":"10"
|
||||
"code":"9"
|
||||
}
|
||||
]
|
||||
@ -1,12 +0,0 @@
|
||||
<a name="Kafka-client-optimize"></a><a name="Kafka-client-optimize"></a>
|
||||
|
||||
<h1 class="topictitle1">Recommendations on Client Usage</h1>
|
||||
<div id="body1557191333110"><ul id="Kafka-client-optimize__ul7334191715103"><li id="Kafka-client-optimize__li43351517121017">Producer parameters<ul id="Kafka-client-optimize__ul121954495102"><li id="Kafka-client-optimize__li1339714478102">Allow for retries in cases where messages fail to be sent.<p id="Kafka-client-optimize__p795816580101"><a name="Kafka-client-optimize__li1339714478102"></a><a name="li1339714478102"></a>For example, allow for three retries by setting the value of <strong id="Kafka-client-optimize__b1971168159">retries</strong> to <strong id="Kafka-client-optimize__b6993682158">3</strong>.</p>
|
||||
</li><li id="Kafka-client-optimize__li1539924710108">The producer cannot block on callback functions. Otherwise, messages may fail to be sent.<p id="Kafka-client-optimize__p07020319112"><a name="Kafka-client-optimize__li1539924710108"></a><a name="li1539924710108"></a>For messages that need to be send immediately, set <strong id="Kafka-client-optimize__b33311229194017">linger.ms</strong> to <strong id="Kafka-client-optimize__b19217163434014">0</strong>.</p>
|
||||
<p id="Kafka-client-optimize__p1871183181111">Ensure that the producer has sufficient JVM memory to avoid blockages.</p>
|
||||
</li></ul>
|
||||
</li><li id="Kafka-client-optimize__li4335161791019">Consumer parameters<ul id="Kafka-client-optimize__ul26161759131318"><li id="Kafka-client-optimize__li92602582134">Ensure that the owner thread does not exit abnormally. Otherwise, the client may fail to initiate consumption requests and the consumption will be blocked.</li><li id="Kafka-client-optimize__li122631358121310">Use long polling to consume messages and do not close the consumer connection immediately after the consumption is completed. Otherwise, rebalancing will take place frequently, blocking consumption.</li><li id="Kafka-client-optimize__li22642588136">Ensure that the consumer polls at regular intervals (for example, every 200 ms) for it to keep sending heartbeats to the server. If the consumer stops sending heartbeats for long enough, the consumer session will time out and the consumer will be considered to have stopped. This will also block consumption.</li><li id="Kafka-client-optimize__li16760112812218">Always close the consumer before exiting. Otherwise, consumers in the same group may block the <strong id="Kafka-client-optimize__b340034102420">session.timeout.ms</strong> time.</li><li id="Kafka-client-optimize__li1544613423127">Set the timeout time for the consumer session to a reasonable value. For example, set <strong id="Kafka-client-optimize__b5870173510464">session.timeout.ms</strong> to <strong id="Kafka-client-optimize__b15502174034613">30000</strong> so that the timeout time is 30s.</li><li id="Kafka-client-optimize__li9266115819132">The number of consumers cannot be greater than the number of partitions in the topic. Otherwise, some consumers may fail to poll for messages.</li><li id="Kafka-client-optimize__li278445032117">Commit messages after they have been processed. Otherwise, the messages may fail to be processed and cannot be polled for again.</li><li id="Kafka-client-optimize__li4267185821316">Ensure that there is a maximum limit on the size of messages buffered locally to avoid an out-of-memory (OOM) situation.</li><li id="Kafka-client-optimize__li526911586132">Kafka supports the exactly-once delivery. Therefore, ensure the idempotency of processing messages for services.</li></ul>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div></div>
|
||||
|
||||
@ -1,10 +1,23 @@
|
||||
<a name="Kafka-config"></a><a name="Kafka-config"></a>
|
||||
|
||||
<h1 class="topictitle1">Collecting Connection Information</h1>
|
||||
<div id="body1552118864471"><div class="section" id="Kafka-config__section1838010271245"><h4 class="sectiontitle">Required Kafka Instance Information</h4><ul id="Kafka-config__ul4401145543917"><li id="Kafka-config__li17401145515394">Instance connection address and port<p id="Kafka-config__p204638583020"><a name="Kafka-config__li17401145515394"></a><a name="li17401145515394"></a>After an instance is created, you can obtain the IP address from the <strong id="Kafka-config__b6424535757">Basic Information</strong> tab page of the instance. You can configure all IP addresses on the client. For example, as shown in the following figure, a 100 MB/s instance has three addresses. Instances of other specifications may have a different number of brokers, so the number of addresses vary.</p>
|
||||
<p id="Kafka-config__p72113348403">For public network access, you can use the public network addresses displayed on the <strong id="Kafka-config__b732165725115">Basic Information</strong> tab page.</p>
|
||||
<div class="fignone" id="Kafka-config__fig426811519812"><span class="figcap"><b>Figure 1 </b>Viewing the connection addresses and ports of brokers of a Kafka instance</span><br><span><img id="Kafka-config__image152681651788" src="en-us_image_0000001337490645.png"></span></div>
|
||||
</li><li id="Kafka-config__li144011355103915">Topic name<p id="Kafka-config__p187435453419"><a name="Kafka-config__li144011355103915"></a><a name="li144011355103915"></a>Obtain the topic name from the <strong id="Kafka-config__b1601948192412">Topics</strong> page of the instance.</p>
|
||||
<div id="body1552118864471"><p id="Kafka-config__p1330823020346">Before accessing a Kafka instance for message production and consumption, obtain the following information of the instance.</p>
|
||||
<div class="section" id="Kafka-config__section539013221352"><h4 class="sectiontitle">Instance Connection Address and Port</h4><p id="Kafka-config__p14733142285020">Obtain them from the <strong id="Kafka-config__b2078511598232">Basic Information</strong> page on the Kafka console.</p>
|
||||
<p id="Kafka-config__p204638583020">For a cluster Kafka instance that has at least three connection addresses, you are advised to configure all of the connection addresses on the client for high reliability.</p>
|
||||
<p id="Kafka-config__p72113348403">For public network access, you can use the public network addresses displayed on the <strong id="Kafka-config__b732165725115">Basic Information</strong> page.</p>
|
||||
<div class="fignone" id="Kafka-config__fig426811519812"><span class="figcap"><b>Figure 1 </b>Viewing the connection addresses and ports of brokers of a Kafka instance</span><br><span><img id="Kafka-config__image1595564310019" src="en-us_image_0000001949896476.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="Kafka-config__section10322144512489"><h4 class="sectiontitle">Topic name</h4><p id="Kafka-config__p187435453419">Obtain the topic name from the <strong id="Kafka-config__b1601948192412">Topics</strong> page of the Kafka instance console.</p>
|
||||
<div class="note" id="Kafka-config__note898162205419"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="Kafka-config__p109832235417">If <strong id="Kafka-config__b88602425515">Automatic Topic Creation</strong> is disabled, a topic must be created first. Then a Kafka instance can be accessed from a client for message production and consumption.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
<div class="section" id="Kafka-config__section7834639164915"><h4 class="sectiontitle">Ciphertext Access</h4><p id="Kafka-config__p5360123575015">If ciphertext access is enabled for the instance, obtain the instance username and password, SASL mechanism, and security protocol. In addition, obtain the SSL certificate if the security protocol is set to <strong id="Kafka-config__b1886516841510">SASL_SSL</strong>.</p>
|
||||
<ul id="Kafka-config__ul19762115465215"><li id="Kafka-config__li576217546523">Obtain the username on the <strong id="Kafka-config__b1696374711162">Users</strong> page on the Kafka console. If you forget your password, obtain it again by <a href="https://docs.otc.t-systems.com/en-us/usermanual/dms/kafka-ug-0003.html" target="_blank" rel="noopener noreferrer">resetting the password</a>.<div class="fignone" id="Kafka-config__fig107621654205212"><span class="figcap"><b>Figure 2 </b>Obtaining the SASL_SSL username</span><br><span><img id="Kafka-config__image87621954105211" src="en-us_image_0000001980576777.png"></span></div>
|
||||
</li><li id="Kafka-config__li6762195415219">Obtain the SASL mechanism from the <strong id="Kafka-config__b961812242457">Basic Information</strong> page on the Kafka console.<div class="p" id="Kafka-config__p2762654195213">If both SCRAM-SHA-512 and PLAIN are enabled, use either of them in connection configurations. For instances that were created much earlier, if <strong id="Kafka-config__b3713111918">SASL Mechanism</strong> is not displayed on the instance details page, PLAIN is used by default.<div class="fignone" id="Kafka-config__fig1376315417529"><span class="figcap"><b>Figure 3 </b>SASL mechanism in use</span><br><span><img id="Kafka-config__image37631954125215" src="en-us_image_0000001980456929.png"></span></div>
|
||||
</div>
|
||||
</li><li id="Kafka-config__li276319540522">Obtain the security protocol from the <strong id="Kafka-config__b861993811456">Basic Information</strong> page on the Kafka console. For Kafka instances that were created much earlier, if <strong id="Kafka-config__b10493184582217">Security Protocol</strong> is not displayed on the instance details page, SASL_SSL is used by default.<div class="fignone" id="Kafka-config__fig1763105412524"><span class="figcap"><b>Figure 4 </b>Security protocol</span><br><span><img id="Kafka-config__image5763195425218" src="en-us_image_0000001980576785.png"></span></div>
|
||||
</li><li id="Kafka-config__li14762125465211">If <strong id="Kafka-config__b46467312350">Security Protocol</strong> is set to <strong id="Kafka-config__b1375502414338">SASL_SSL</strong>, download the certificate from the <strong id="Kafka-config__b151421999352">Basic Information</strong> page on the Kafka console.<p id="Kafka-config__p1076211549522">JKS certificates are used for accessing instances in Java. CRT certificates are used for accessing instances in Python.</p>
|
||||
<div class="fignone" id="Kafka-config__fig8662201513266"><span class="figcap"><b>Figure 5 </b>Downloading the SSL certificate</span><br><span><img id="Kafka-config__image9662151572612" src="en-us_image_0000001950565600.png"></span></div>
|
||||
</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,15 +1,13 @@
|
||||
<a name="Kafka-summary"></a><a name="Kafka-summary"></a>
|
||||
|
||||
<h1 class="topictitle1">Overview</h1>
|
||||
<div id="body1557133871089"><p id="Kafka-summary__p17962777142">Kafka instances are compatible with Apache Kafka and can be accessed using <a href="https://cwiki.apache.org/confluence/display/KAFKA/Clients" target="_blank" rel="noopener noreferrer">open-source Kafka clients</a>. To access an instance in SASL mode, you will also need certificates.</p>
|
||||
<p id="Kafka-summary__p1432673361615">This document describes how to collect instance connection information, such as the instance connection address, certificate required for SASL connection, and information required for public access. It also provides examples of accessing an instance in Java and Python.</p>
|
||||
<div id="body1557133871089"><p id="Kafka-summary__p17962777142">Kafka instances are compatible with Apache Kafka and can be accessed using <a href="https://cwiki.apache.org/confluence/display/KAFKA/Clients" target="_blank" rel="noopener noreferrer">open-source Kafka clients</a>. In addition, if <strong id="Kafka-summary__b1247443819360">Security Protocol</strong> is set to <strong id="Kafka-summary__b41607428365">SASL_SSL</strong>, use the DMS certificate.</p>
|
||||
<p id="Kafka-summary__p1432673361615">This document describes how to collect instance connection information, such as the instance connection address and topic name. It also provides examples of accessing an instance in Java, Python, and Go.</p>
|
||||
<p id="Kafka-summary__p1624111012409">The examples only demonstrate how to invoke Kafka APIs for producing and consuming messages. For more information about the APIs provided by Kafka, visit the <a href="https://kafka.apache.org/documentation/#api" target="_blank" rel="noopener noreferrer">Kafka official website</a>.</p>
|
||||
<div class="section" id="Kafka-summary__section101221025563"><h4 class="sectiontitle">Client Network Environment</h4><p id="Kafka-summary__p2863171712224">A client can access a Kafka instance in any of the following modes:</p>
|
||||
<ol id="Kafka-summary__ol197311830103116"><li id="Kafka-summary__li11137644183112">Within a Virtual Private Network (VPC)<p id="Kafka-summary__p1258944416312"><a name="Kafka-summary__li11137644183112"></a><a name="li11137644183112"></a>If the client runs an Elastic Cloud Server (ECS) and is in the same region and VPC as the Kafka instance, the client can access the instance using an IP address within a subnet in the VPC.</p>
|
||||
</li><li id="Kafka-summary__li4767204612311">Using a VPC peering connection<p id="Kafka-summary__p68941721325"><a name="Kafka-summary__li4767204612311"></a><a name="li4767204612311"></a>If the client runs an ECS and is in the same region but not the same VPC as the Kafka instance, the client can access the instance using an IP address within a subnet in the VPC after a VPC peering connection has been established.</p>
|
||||
</li><li id="Kafka-summary__li17887278327">Over public networks<p id="Kafka-summary__p82261284329"><a name="Kafka-summary__li17887278327"></a><a name="li17887278327"></a>If the client is not in the same network environment or region as the Kafka instance, the client can access the instance using a public network IP address.</p>
|
||||
<p id="Kafka-summary__p234917355163">For public access, modify the inbound rules of the security group configured for the Kafka instance, allowing access over port 9094 or 9095.</p>
|
||||
</li></ol>
|
||||
<ul id="Kafka-summary__ul956754555215"><li id="Kafka-summary__li85671345185211">If the client runs an Elastic Cloud Server (ECS) and is in the same region and VPC as the Kafka instance, the client can access the instance using a private network IP address.</li><li id="Kafka-summary__li2538202115313">If the client runs an ECS, and is in the same region but not in the same VPC as the Kafka instance, the client can access the instance using one of the following methods:<ul id="Kafka-summary__ul25402153533"><li id="Kafka-summary__en-us_topic_0000001096588567_li5721515171018">Establish a VPC peering connection to allow two VPCs to communicate with each other. For details, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/vpc/vpc_peering_0000.html" target="_blank" rel="noopener noreferrer">VPC Peering Connection</a>. Modify the security group of your Kafka instance as required: Allow external access over port 9092 (in plaintext) or 9093 (in ciphertext).</li><li id="Kafka-summary__en-us_topic_0000001096588567_li113217487569">Access a Kafka instance on a Kafka client over a private network across VPCs using a VPC endpoint. For details, see <a href="https://docs.otc.t-systems.com/en-us/usermanual/dms/kafka-ug-0001.html" target="_blank" rel="noopener noreferrer">Accessing Kafka Across VPCs Using VPCEP</a>. Modify the security group to allow port 9011 for external access.</li></ul>
|
||||
</li><li id="Kafka-summary__li11298485533">If the client is not in the same network environment or region as the Kafka instance, the client can access the instance using a public network IP address.<p id="Kafka-summary__p42999170544"><a name="Kafka-summary__li11298485533"></a><a name="li11298485533"></a>To use public access, modify the security group of your Kafka instance as required: Allow external access over port 9094 (in plaintext) or 9095 (in ciphertext).</p>
|
||||
</li></ul>
|
||||
<div class="note" id="Kafka-summary__note270270114713"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="Kafka-summary__p022134701514">The three modes differ only in the connection address for the client to access the instance. This document takes intra-VPC access as an example to describe how to set up the development environment.</p>
|
||||
<p id="Kafka-summary__p127028015479">If the connection times out or fails, check the network connectivity. You can use telnet to test the connection address and port of the instance.</p>
|
||||
</div></div>
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 9.5 KiB |
BIN
docs/dms/dev/en-us_image_0000001949896476.png
Normal file
BIN
docs/dms/dev/en-us_image_0000001949896476.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 9.6 KiB |
BIN
docs/dms/dev/en-us_image_0000001950565600.png
Normal file
BIN
docs/dms/dev/en-us_image_0000001950565600.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
BIN
docs/dms/dev/en-us_image_0000001980456929.png
Normal file
BIN
docs/dms/dev/en-us_image_0000001980456929.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
BIN
docs/dms/dev/en-us_image_0000001980576777.png
Normal file
BIN
docs/dms/dev/en-us_image_0000001980576777.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 5.1 KiB |
BIN
docs/dms/dev/en-us_image_0000001980576785.png
Normal file
BIN
docs/dms/dev/en-us_image_0000001980576785.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
@ -46,11 +46,11 @@
|
||||
<td class="cellrowborder" valign="top" width="41.83418341834184%" headers="mcps1.3.3.2.1.2.2.2.4.1.3 "><p id="how-to-connect-kafka__p138994094715">Configuration information for producing messages</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="how-to-connect-kafka__row1189970194712"><td class="cellrowborder" valign="top" width="26.49264926492649%" headers="mcps1.3.3.2.1.2.2.2.4.1.1 "><p id="how-to-connect-kafka__p889930184714">client.truststore.jks</p>
|
||||
<tr id="how-to-connect-kafka__row1189970194712"><td class="cellrowborder" valign="top" width="26.49264926492649%" headers="mcps1.3.3.2.1.2.2.2.4.1.1 "><p id="how-to-connect-kafka__p889930184714">client.jks</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="31.67316731673167%" headers="mcps1.3.3.2.1.2.2.2.4.1.2 "><p id="how-to-connect-kafka__p1789980124713">.\src\main\resources</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="41.83418341834184%" headers="mcps1.3.3.2.1.2.2.2.4.1.3 "><p id="how-to-connect-kafka__p589940154713">SSL certificate, used for SASL connection</p>
|
||||
<td class="cellrowborder" valign="top" width="41.83418341834184%" headers="mcps1.3.3.2.1.2.2.2.4.1.3 "><p id="how-to-connect-kafka__p589940154713">SSL certificate, used for SASL_SSL connection</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="how-to-connect-kafka__row1623641494915"><td class="cellrowborder" valign="top" width="26.49264926492649%" headers="mcps1.3.3.2.1.2.2.2.4.1.1 "><p id="how-to-connect-kafka__p9237191484920">DmsConsumerTest.java</p>
|
||||
@ -86,37 +86,7 @@
|
||||
<p id="how-to-connect-kafka__p185285103610"><span><img id="how-to-connect-kafka__image18982152463710" src="en-us_image_0171660939.png"></span></p>
|
||||
</p></li><li id="how-to-connect-kafka__li54701543155512"><span>Configure Maven.</span><p><p class="MsoNormal" id="how-to-connect-kafka__p1256543315148">Choose <strong id="how-to-connect-kafka__b3285165201814">Files</strong> > <strong id="how-to-connect-kafka__b1159718138181">Settings</strong>, set <strong id="how-to-connect-kafka__b11644172152210">Maven home directory</strong> correctly, and select the required <strong id="how-to-connect-kafka__b155112732216">settings.xml</strong> file.</p>
|
||||
<p id="how-to-connect-kafka__p201751061418"><span><img id="how-to-connect-kafka__image38584015142" src="en-us_image_0171660970.png"></span></p>
|
||||
</p></li><li id="how-to-connect-kafka__li10470164310559"><span>Specify Kafka configurations.</span><p><p id="how-to-connect-kafka__p278910111468">The following is a configuration example for producing messages. Replace the information in bold with the actual values.</p>
|
||||
<pre class="screen" id="how-to-connect-kafka__screen25135224477">#The information in bold is specific to different Kafka instances and must be modified. Other parameters can also be added.
|
||||
#The topic name is in the specific production and consumption code.
|
||||
#######################
|
||||
#Information about Kafka brokers. <strong id="how-to-connect-kafka__b1333422317215">ip:port</strong> are the connection addresses and ports used by the instance. The values can be obtained by referring to the "Collecting Connection Information" section. Example: bootstrap.servers=100.xxx.xxx.87:909x,100.xxx.xxx.69:909x,100.xxx.xxx.155:909x
|
||||
bootstrap.servers=<strong id="how-to-connect-kafka__b13819311161719">ip1:port1,ip2:port2,ip3:port3</strong>
|
||||
#Producer acknowledgement
|
||||
acks=all
|
||||
#Method of turning the key into bytes
|
||||
key.serializer=org.apache.kafka.common.serialization.StringSerializer
|
||||
#Method of turning the value into bytes
|
||||
value.serializer=org.apache.kafka.common.serialization.StringSerializer
|
||||
#Memory available to the producer for buffering
|
||||
buffer.memory=33554432
|
||||
#Number of retries
|
||||
retries=0
|
||||
#######################
|
||||
#Comment out the following parameters if SASL access is not enabled.
|
||||
#######################
|
||||
#Configure the JAAS username and password. <em id="how-to-connect-kafka__i393707281"><strong id="how-to-connect-kafka__b19318014283">username</strong></em> and <em id="how-to-connect-kafka__i6944052814"><strong id="how-to-connect-kafka__b13936012287">password</strong></em> are set when you enable Kafka SASL_SSL during instance creation or when you create a SASL_SSL user.
|
||||
sasl.jaas.config=org.apache.kafka.common.security.plain.PlainLoginModule required \
|
||||
username="<strong id="how-to-connect-kafka__b1381921119175">username</strong>" \
|
||||
password="<strong id="how-to-connect-kafka__b381911113171">password</strong>";
|
||||
#SASL mechanism
|
||||
sasl.mechanism=PLAIN
|
||||
#Encryption protocol. Currently, only SASL_SSL is supported.
|
||||
security.protocol=SASL_SSL
|
||||
#Location of ssl.truststore
|
||||
ssl.truststore.location=<strong id="how-to-connect-kafka__b5820911111714">E:\\temp\\client.truststore.jks</strong>
|
||||
#Password of ssl.truststore, which must be set to dms@kafka and cannot be changed.
|
||||
ssl.truststore.password=dms@kafka</pre>
|
||||
</p></li><li id="how-to-connect-kafka__li10470164310559"><span>Specify Kafka configurations.</span><p><p id="how-to-connect-kafka__p278910111468">This section uses the example of producing messages. For details, see <a href="Kafka-java-demo.html#Kafka-java-demo__li106711612652">Producer configuration file</a>.</p>
|
||||
</p></li><li id="how-to-connect-kafka__li153111734619"><span>In the down left corner of IDEA, click <strong id="how-to-connect-kafka__b323811566572">Terminal</strong>. In terminal, run the <strong id="how-to-connect-kafka__b181421630141516">mvn test</strong> command to see how the demo project goes.</span><p><div class="fignone" id="how-to-connect-kafka__fig13579842143916"><span class="figcap"><b>Figure 4 </b>Opening terminal in IDEA</span><br><span><img id="how-to-connect-kafka__image1567249144013" src="en-us_image_0171660984.png"></span></div>
|
||||
<p id="how-to-connect-kafka__p93961749163812">The following information is displayed for the producer:</p>
|
||||
<pre class="screen" id="how-to-connect-kafka__screen1396174914381">-------------------------------------------------------
|
||||
|
||||
@ -8,7 +8,13 @@
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="kafka-devg-0407002__row18642161514216"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.1.1.3.1.1 "><p id="kafka-devg-0407002__p364241552119">2022-10-30</p>
|
||||
<tbody><tr id="kafka-devg-0407002__row1280912195214"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.1.1.3.1.1 "><p id="kafka-devg-0407002__p980201205214">2024-07-12</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.1.1.3.1.2 "><p id="kafka-devg-0407002__p8808124522">This issue incorporates the following change:</p>
|
||||
<ul id="kafka-devg-0407002__ul4653113385219"><li id="kafka-devg-0407002__li1465313305215">Kafka instances supported security and SASL authentication mechanisms, involving modification to the sample code for connecting to an instance with SASL enabled.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="kafka-devg-0407002__row18642161514216"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.1.1.3.1.1 "><p id="kafka-devg-0407002__p364241552119">2022-10-30</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.1.1.3.1.2 "><p id="kafka-devg-0407002__p11642121514213">This issue incorporates the following changes:</p>
|
||||
<ul id="kafka-devg-0407002__ul187113335219"><li id="kafka-devg-0407002__li1471223392114">Removed the developer guide for Kafka queues.</li><li id="kafka-devg-0407002__li154721347115315">Added <a href="kafka-go.html">Go</a> and <a href="kafka-connect-other.html">Obtaining Kafka Clients</a>.</li></ul>
|
||||
@ -17,13 +23,13 @@
|
||||
<tr id="kafka-devg-0407002__row05321311067"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.1.1.3.1.1 "><p id="kafka-devg-0407002__p417243817421">2020-02-20</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.1.1.3.1.2 "><p id="kafka-devg-0407002__p137041320434">This issue incorporates the following changes:</p>
|
||||
<ul id="kafka-devg-0407002__ul1810511248437"><li id="kafka-devg-0407002__li51051524134312">Upgraded Kafka premium compatibility from Kafka 2.3.0 to 2.3.1.</li></ul>
|
||||
<ul id="kafka-devg-0407002__ul1810511248437"><li id="kafka-devg-0407002__li51051524134312">Upgraded Kafka compatibility from Kafka 2.3.0 to 2.3.1.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="kafka-devg-0407002__row3335153684717"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.1.1.3.1.1 "><p id="kafka-devg-0407002__p9483208112517">2019-11-08</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="75%" headers="mcps1.3.1.1.3.1.2 "><p id="kafka-devg-0407002__p26591850182816">This issue incorporates the following changes:</p>
|
||||
<ul id="kafka-devg-0407002__ul18291949172814"><li id="kafka-devg-0407002__li18291749202819">Added Kafka premium features and developer guide.</li></ul>
|
||||
<ul id="kafka-devg-0407002__ul18291949172814"><li id="kafka-devg-0407002__li18291749202819">Added Kafka features and developer guide.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="kafka-devg-0407002__row8512195623819"><td class="cellrowborder" valign="top" width="25%" headers="mcps1.3.1.1.3.1.1 "><p id="kafka-devg-0407002__p106057164018">2018-02-03</p>
|
||||
@ -41,4 +47,5 @@
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
<div></div>
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
Loading…
x
Reference in New Issue
Block a user