如何在WINDOW環境下搭建ActivateMQ和zookeeper集羣環境
考慮到使用虛擬機環境搭建環境須要太多內存,因而研究如何使用window版本創建環境.
@echo off REM Licensed to the Apache Software Foundation (ASF) under one or more REM contributor license agreements. See the NOTICE file distributed with REM this work for additional information regarding copyright ownership. REM The ASF licenses this file to You under the Apache License, Version 2.0 REM (the "License"); you may not use this file except in compliance with REM the License. You may obtain a copy of the License at REM REM http://www.apache.org/licenses/LICENSE-2.0 REM REM Unless required by applicable law or agreed to in writing, software REM distributed under the License is distributed on an "AS IS" BASIS, REM WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. REM See the License for the specific language governing permissions and REM limitations under the License. setlocal e: cd E:\git\zookeeper-3.4.12\bin call "%~dp0zkEnv.cmd" set ZOOMAIN=org.apache.zookeeper.server.quorum.QuorumPeerMain echo on call %JAVA% "-Dzookeeper.log.dir=%ZOO_LOG_DIR%" "-Dzookeeper.root.logger=%ZOO_LOG4J_PROP%" -cp "%CLASSPATH%" %ZOOMAIN% "%ZOOCFGDIR%\1.cfg" %* endlocal pause
1.cfg html
# synchronization phase can take initLimit=10 # The number of ticks that can pass between # sending a request and getting an acknowledgement syncLimit=5 # the directory where the snapshot is stored. # do not use /tmp for storage, /tmp here is just # example sakes. dataDir=../data/1 # the port at which the clients will connect clientPort=2181 # the maximum number of client connections. # increase this if you need to handle more clients #maxClientCnxns=60 # # Be sure to read the maintenance section of the # administrator guide before turning on autopurge. # # http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_maintenance # # The number of snapshots to retain in dataDir #autopurge.snapRetainCount=3 # Purge task interval in hours # Set to "0" to disable auto purge feature #autopurge.purgeInterval=1 server.1=127.0.0.1:2181:3881 server.2=127.0.0.1:12181:13881 server.3=127.0.0.1:22181:23881
data中創建 1 2 3 目錄,在其中創建 myid 文件,內容分別爲 1 2 3 .java
如此相似配置3個cmd文件和cfg文件git
分別運行,完成zookeeper 集羣web
正常的zookeeper dos窗口主 從 從spring
uestProcessor@487] - Processed session termination for sessionid: 0x200053f0361 004 2018-05-10 08:54:40,975 [myid:3] - INFO [SessionTracker:ZooKeeperServer@354] - Expiring session 0x200053f03610005, timeout of 4000ms exceeded 2018-05-10 08:54:40,975 [myid:3] - INFO [SessionTracker:ZooKeeperServer@354] - Expiring session 0x100053f00f20005, timeout of 4000ms exceeded 2018-05-10 08:54:40,975 [myid:3] - INFO [ProcessThread(sid:3 cport:-1)::PrepRe uestProcessor@487] - Processed session termination for sessionid: 0x200053f0361 005 2018-05-10 08:54:40,975 [myid:3] - INFO [ProcessThread(sid:3 cport:-1)::PrepRe uestProcessor@487] - Processed session termination for sessionid: 0x100053f00f2 005 2018-05-10 08:54:42,975 [myid:3] - INFO [SessionTracker:ZooKeeperServer@354] - Expiring session 0x300053f07550006, timeout of 4000ms exceeded 2018-05-10 08:54:42,976 [myid:3] - INFO [ProcessThread(sid:3 cport:-1)::PrepRe uestProcessor@487] - Processed session termination for sessionid: 0x300053f0755 006 ----------------------------- 2018-05-10 08:54:34,303 [myid:2] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2 182:ZooKeeperServer@948] - Client attempting to establish new session at /127.0. 0.1:55853 2018-05-10 08:54:34,824 [myid:2] - INFO [CommitProcessor:2:ZooKeeperServer@693] - Established session 0x200053f03610005 with negotiated timeout 4000 for client /127.0.0.1:55853 2018-05-10 08:54:34,824 [myid:2] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2 182:NIOServerCnxn@383] - Exception causing close of session 0x200053f03610005: 您的主機中的軟件停止了一個已創建的鏈接。 2018-05-10 08:54:34,827 [myid:2] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2 182:NIOServerCnxn@1040] - Closed socket connection for client /127.0.0.1:55853 w hich had sessionid 0x200053f03610005 -------------------- 181:NIOServerCnxnFactory@215] - Accepted socket connection from /127.0 2018-05-10 08:54:35,603 [myid:1] - INFO [NIOServerCxn.Factory:0.0.0.0 181:ZooKeeperServer@948] - Client attempting to establish new session 0.1:55857 2018-05-10 08:54:36,129 [myid:1] - INFO [CommitProcessor:1:ZooKeeperS - Established session 0x100053f00f20005 with negotiated timeout 4000 /127.0.0.1:55857 2018-05-10 08:54:36,130 [myid:1] - WARN [NIOServerCxn.Factory:0.0.0.0 181:NIOServerCnxn@383] - Exception causing close of session 0x100053f0 您的主機中的軟件停止了一個已創建的鏈接。 2018-05-10 08:54:36,130 [myid:1] - INFO [NIOServerCxn.Factory:0.0.0.0 181:NIOServerCnxn@1040] - Closed socket connection for client /127.0.0 hich had sessionid 0x100053f00f20005
第二步,配置activateMQ集羣express
copy mq的啓動命令 E:\git\apache-activemq-5.15.3\bin\win64\activemq1.batapache
@echo off REM ------------------------------------------------------------------------ REM Licensed to the Apache Software Foundation (ASF) under one or more REM contributor license agreements. See the NOTICE file distributed with REM this work for additional information regarding copyright ownership. REM The ASF licenses this file to You under the Apache License, Version 2.0 REM (the "License"); you may not use this file except in compliance with REM the License. You may obtain a copy of the License at REM REM http://www.apache.org/licenses/LICENSE-2.0 REM REM Unless required by applicable law or agreed to in writing, software REM distributed under the License is distributed on an "AS IS" BASIS, REM WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. REM See the License for the specific language governing permissions and REM limitations under the License. REM ------------------------------------------------------------------------ rem rem Find the application home. rem if "%OS%"=="Windows_NT" goto nt echo This is not NT, so please edit this script and set _APP_HOME manually set _APP_HOME=.. goto conf :nt rem %~dp0 is name of current script under NT set _APP_HOME=%~dp0 rem rem Find the wrapper1.conf rem :conf set _WRAPPER_CONF=wrapper1.conf rem rem Run the application. rem At runtime, the current directory will be that of Wrapper.exe rem "%_APP_HOME%wrapper.exe" -c %_WRAPPER_CONF% if not errorlevel 1 goto end pause :end set _APP_HOME= set _WRAPPER_CONF=
複製 data和conf目錄爲 data1 conf1json
copy wrapper.conf 爲 wrapper1.conf 並修改api
# wrapper.debug=TRUE set.default.ACTIVEMQ_HOME=../.. set.default.ACTIVEMQ_BASE=../.. set.default.ACTIVEMQ_CONF=%ACTIVEMQ_BASE%/conf1 set.default.ACTIVEMQ_DATA=%ACTIVEMQ_BASE%/data1 wrapper.working.dir=.
修改conf1中的 activate.xml 和 jetty.xmlbash
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- START SNIPPET: example -->
<beans
xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">
<!-- Allows us to use system properties as variables in this configuration file -->
<bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="locations">
<value>file:${activemq.conf}/credentials.properties</value>
</property>
</bean>
<!-- Allows accessing the server log -->
<bean id="logQuery" class="io.fabric8.insight.log.log4j.Log4jLogQuery"
lazy-init="false" scope="singleton"
init-method="start" destroy-method="stop">
</bean>
<!--
The <broker> element is used to configure the ActiveMQ broker.
-->
<broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="${activemq.data}">
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry topic=">" >
<!-- The constantPendingMessageLimitStrategy is used to prevent
slow topic consumers to block producers and affect other consumers
by limiting the number of messages that are retained
For more information, see:
http://activemq.apache.org/slow-consumer-handling.html
-->
<pendingMessageLimitStrategy>
<constantPendingMessageLimitStrategy limit="1000"/>
</pendingMessageLimitStrategy>
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>
<!--
The managementContext is used to configure how ActiveMQ is exposed in
JMX. By default, ActiveMQ uses the MBean server that is started by
the JVM. For more information, see:
http://activemq.apache.org/jmx.html
-->
<managementContext>
<managementContext createConnector="false"/>
</managementContext>
<!--
Configure message persistence for the broker. The default persistence
mechanism is the KahaDB store (identified by the kahaDB tag).
For more information, see:
http://activemq.apache.org/persistence.html
<persistenceAdapter>
<kahaDB directory="${activemq.data}/kahadb"/>
</persistenceAdapter>
-->
<persistenceAdapter>
<replicatedLevelDB
directory="${activemq.data}/leveldb"
replicas="3"
bind="tcp://0.0.0.0:62621"
zkAddress="localhost:2181,localhost:2182,localhost:2183"
hostname="localhost"
zkPath="/activemq/leveldb-stores"/>
</persistenceAdapter>
<!--
The systemUsage controls the maximum amount of space the broker will
use before disabling caching and/or slowing down producers. For more information, see:
http://activemq.apache.org/producer-flow-control.html
-->
<systemUsage>
<systemUsage>
<memoryUsage>
<memoryUsage percentOfJvmHeap="70" />
</memoryUsage>
<storeUsage>
<storeUsage limit="100 gb"/>
</storeUsage>
<tempUsage>
<tempUsage limit="50 gb"/>
</tempUsage>
</systemUsage>
</systemUsage>
<!--
The transport connectors expose ActiveMQ over a given protocol to
clients and other brokers. For more information, see:
http://activemq.apache.org/configuring-transports.html
-->
<transportConnectors>
<!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB -->
<transportConnector name="openwire" uri="tcp://0.0.0.0:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
<transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
<transportConnector name="stomp" uri="stomp://0.0.0.0:61613?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
<transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
<transportConnector name="ws" uri="ws://0.0.0.0:61614?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
</transportConnectors>
<!-- destroy the spring context on shutdown to stop jetty -->
<shutdownHooks>
<bean xmlns="http://www.springframework.org/schema/beans" class="org.apache.activemq.hooks.SpringContextHook" />
</shutdownHooks>
</broker>
<!--
Enable web consoles, REST and Ajax APIs and demos
The web consoles requires by default login, you can disable this in the jetty.xml file
Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details
-->
<import resource="jetty.xml"/>
</beans>
<!-- END SNIPPET: example -->
jetty.xml
<bean id="jettyPort" class="org.apache.activemq.web.WebConsolePort" init-method="start">
<!-- the default port number for the web console -->
<property name="host" value="0.0.0.0"/>
<property name="port" value="8161"/>
</bean>
bind="tcp://0.0.0.0:62621"
<transportConnectors
<property name="port" value="8161"/>
如此3個目錄中 上述端口不要重複
而後分別啓動 3個mq的bat.
th jvm 3 | INFO | ActiveMQ WebConsole available at http://0.0.0.0:8163/ jvm 3 | INFO | ActiveMQ Jolokia REST API available at http://0.0.0.0:8163/ap i/jolokia/ jvm 3 | INFO | Initializing Spring FrameworkServlet 'dispatcher' jvm 3 | INFO | No Spring WebApplicationInitializer types detected on classpa th jvm 3 | INFO | jolokia-agent: Using policy access restrictor classpath:/jolo kia-access.xml jvm 3 | INFO | Connector vm://localhost started
jvm 1 | INFO | Socket connection established to han-PC/0:0:0:0:0:0:0:1:21 initiating session jvm 1 | INFO | Session establishment complete on server han-PC/0:0:0:0:0: :1:2183, sessionid = 0x300053f07550007, negotiated timeout = 4000 jvm 1 | INFO | Using the pure java LevelDB implementation. jvm 1 | INFO | Attaching to master: tcp://localhost:62623 jvm 1 | INFO | Slave started jvm 1 | INFO | Slave skipping download of: log/0000000000000000.log jvm 1 | INFO | Slave requested: 000000000000080b.index/CURRENT jvm 1 | INFO | Slave requested: 000000000000080b.index/MANIFEST-000002 jvm 1 | INFO | Slave requested: 000000000000080b.index/000003.log jvm 1 | INFO | Attaching... Downloaded 0.02/1.37 kb and 1/3 files jvm 1 | INFO | Attaching... Downloaded 0.06/1.37 kb and 2/3 files jvm 1 | INFO | Attaching... Downloaded 1.37/1.37 kb and 3/3 files jvm 1 | INFO | Attached
jvm 2 | INFO | Slave stopped jvm 2 | WARN | listeners are taking too long to process the events jvm 2 | WARN | listeners are taking too long to process the events jvm 2 | INFO | Using the pure java LevelDB implementation. jvm 2 | INFO | Attaching to master: tcp://localhost:62623 jvm 2 | INFO | Slave started jvm 2 | INFO | Slave skipping download of: log/0000000000000000.log jvm 2 | INFO | Slave requested: 000000000000080b.index/000003.log jvm 2 | INFO | Slave requested: 000000000000080b.index/CURRENT jvm 2 | INFO | Slave requested: 000000000000080b.index/MANIFEST-000002 jvm 2 | INFO | Attaching... Downloaded 1.31/1.37 kb and 1/3 files jvm 2 | INFO | Attaching... Downloaded 1.32/1.37 kb and 2/3 files jvm 2 | INFO | Attaching... Downloaded 1.37/1.37 kb and 3/3 files jvm 2 | INFO | Attached
查看zookeeper
[zk: localhost:2181(CONNECTED) 9] get /activemq/leveldb-stores/00000000010
{"id":"localhost","container":null,"address":null,"position":-1,"weight":1,"elec
ted":null}
cZxid = 0x20000004c
ctime = Wed May 09 17:17:54 CST 2018
mZxid = 0x300000013
mtime = Thu May 10 08:54:26 CST 2018
pZxid = 0x20000004c
cversion = 0
dataVersion = 3
aclVersion = 0
ephemeralOwner = 0x20001a36c630002
dataLength = 90
numChildren = 0
[zk: localhost:2181(CONNECTED) 10] get /activemq/leveldb-stores/00000000009
{"id":"localhost","container":null,"address":"tcp://localhost:62623","position":
tcp://localhost:62623 對應的第3個activatemq的leveldb綁定的端口
<persistenceAdapter>
<replicatedLevelDB
directory="${activemq.data}/leveldb"
replicas="3"
bind="tcp://0.0.0.0:62623"
zkAddress="localhost:2181,localhost:2182,localhost:2183"
hostname="localhost"
zkPath="/activemq/leveldb-stores"/>
</persistenceAdapter>
代碼:
package han;
/**
* Created by han on 2018/5/7.
*/
import org.apache.activemq.ActiveMQConnectionFactory;
import javax.jms.*;
public class ZkSend {
//鏈接帳號
private String userName = "admin";
//鏈接密碼
private String password = "admin";
//鏈接地址
private String brokerURL = "failover:(tcp://127.0.0.1:61616,tcp://127.0.0.1:62616,tcp://127.0.0.1:63616)?randomize=false";
//connection的工廠
private ConnectionFactory factory;
//鏈接對象
private Connection connection;
//一個操做會話
private Session session;
//目的地，其實就是鏈接到哪一個隊列，若是是點對點，那麼它的實現是Queue，若是是訂閱模式，那它的實現是Topic
private Destination destination;
//生產者，就是產生數據的對象
private MessageProducer producer;
public static void main(String[] args) throws JMSException {
ZkSend send = new ZkSend();
send.start();
}
public void start() throws JMSException {
try {
//根據用戶名，密碼，url建立一個鏈接工廠
factory = new ActiveMQConnectionFactory(userName, password, brokerURL);
//從工廠中獲取一個鏈接
connection = factory.createConnection();
//測試過這個步驟不寫也是能夠的，可是網上的各個文檔都寫了
connection.start();
//建立一個session
//第一個參數:是否支持事務，若是爲true，則會忽略第二個參數，被jms服務器設置爲SESSION_TRANSACTED
//第二個參數爲false時，paramB的值可爲Session.AUTO_ACKNOWLEDGE，Session.CLIENT_ACKNOWLEDGE，DUPS_OK_ACKNOWLEDGE其中一個。
//Session.AUTO_ACKNOWLEDGE爲自動確認，客戶端發送和接收消息不須要作額外的工做。哪怕是接收端發生異常，也會被看成正常發送成功。
//Session.CLIENT_ACKNOWLEDGE爲客戶端確認。客戶端接收到消息後，必須調用javax.jms.Message的acknowledge方法。jms服務器纔會看成發送成功，並刪除消息。
//DUPS_OK_ACKNOWLEDGE容許副本的確認模式。一旦接收方應用程序的方法調用從處理消息處返回，會話對象就會確認消息的接收；並且容許重複確認。
session = connection.createSession(true, Session.AUTO_ACKNOWLEDGE);
//建立一個到達的目的地，其實想一下就知道了，activemq不可能同時只能跑一個隊列吧，這裏就是鏈接了一個名爲"text-msg"的隊列，這個會話將會到這個隊列，固然，若是這個隊列不存在，將會被建立
destination = session.createQueue("text-msg");
//從session中，獲取一個消息生產者
producer = session.createProducer(destination);
//設置生產者的模式，有兩種可選
//DeliveryMode.PERSISTENT 當activemq關閉的時候，隊列數據將會被保存
//DeliveryMode.NON_PERSISTENT 當activemq關閉的時候，隊列裏面的數據將會被清空
producer.setDeliveryMode(DeliveryMode.PERSISTENT);
//建立一條消息，固然，消息的類型有不少，如文字，字節，對象等,能夠經過session.create..方法來建立出來
TextMessage textMsg = session.createTextMessage(String.valueOf( System.currentTimeMillis())+"ZooKeeper!");
// BytesMessage bytesMessage=session.createBytesMessage( );
// bytesMessage.setByteProperty("a",Byte.parseByte("01"));
for(int i = 0 ; i < 3 ; i ++){
//發送一條消息
producer.send(textMsg );
// producer.send(bytesMessage);
}
session.commit();
System.out.println("發送消息成功");
//即使生產者的對象關閉了，程序還在運行哦
producer.close();
} catch (JMSException e) {
session.rollback(); // rollback when exception happens
e.printStackTrace();
}
}
}
package han;
/**
* Created by han on 2018/5/7.
*/
import org.apache.activemq.ActiveMQConnectionFactory;
import javax.jms.*;
public class ZkReceive {
//鏈接帳號
private String userName = "admin";
//鏈接密碼
private String password = "admin";
//鏈接地址
private String brokerURL = "failover:(tcp://127.0.0.1:61616,tcp://127.0.0.1:62616,tcp://127.0.0.1:63616)?randomize=false";
//connection的工廠
private ConnectionFactory factory;
//鏈接對象
private Connection connection;
//一個操做會話
private Session session;
//目的地，其實就是鏈接到哪一個隊列，若是是點對點，那麼它的實現是Queue，若是是訂閱模式，那它的實現是Topic
private Destination destination;
//消費者，就是接收數據的對象
private MessageConsumer consumer;
public static void main(String[] args) throws JMSException {
ZkReceive receive = new ZkReceive();
receive.start();
}
public void start() throws JMSException {
try {
//根據用戶名，密碼，url建立一個鏈接工廠
factory = new ActiveMQConnectionFactory(userName, password, brokerURL);
//從工廠中獲取一個鏈接
connection = factory.createConnection();
//測試過這個步驟不寫也是能夠的，可是網上的各個文檔都寫了
connection.start();
//建立一個session
//第一個參數:是否支持事務，若是爲true，則會忽略第二個參數，被jms服務器設置爲SESSION_TRANSACTED
//第二個參數爲false時，paramB的值可爲Session.AUTO_ACKNOWLEDGE，Session.CLIENT_ACKNOWLEDGE，DUPS_OK_ACKNOWLEDGE其中一個。
//Session.AUTO_ACKNOWLEDGE爲自動確認，客戶端發送和接收消息不須要作額外的工做。哪怕是接收端發生異常，也會被看成正常發送成功。
//Session.CLIENT_ACKNOWLEDGE爲客戶端確認。客戶端接收到消息後，必須調用javax.jms.Message的acknowledge方法。jms服務器纔會看成發送成功，並刪除消息。
//DUPS_OK_ACKNOWLEDGE容許副本的確認模式。一旦接收方應用程序的方法調用從處理消息處返回，會話對象就會確認消息的接收；並且容許重複確認。
session = connection.createSession(true, Session.AUTO_ACKNOWLEDGE);
//建立一個到達的目的地，其實想一下就知道了，activemq不可能同時只能跑一個隊列吧，這裏就是鏈接了一個名爲"text-msg"的隊列，這個會話將會到這個隊列，固然，若是這個隊列不存在，將會被建立
destination = session.createQueue("text-msg");
//根據session，建立一個接收者對象
consumer = session.createConsumer(destination);
//實現一個消息的監聽器
//實現這個監聽器後，之後只要有消息，就會經過這個監聽器接收到
consumer.setMessageListener(new MessageListener() {
public void onMessage(Message message) {
try {
//獲取到接收的數據
String text = ((TextMessage)message).getText();
System.out.println(text);
} catch (JMSException e) {
e.printStackTrace();
try {
session.rollback();
} catch (JMSException e1) {
e1.printStackTrace();
}
}
}
});
//關閉接收端，也不會終止程序哦
session.commit();
// consumer.close();
} catch (JMSException e) {
session.rollback(); // rollback when exception happens
e.printStackTrace();
} finally {
// consumer.close();
//http://localhost:8161/api/message/text-msg?type=queue&clientId=han-PC-57632-1525743389712-1%3A1%3A1%3A1%3A1&json=true
}
}
}
http://127.0.0.1:8163/admin/queues.jsp 查看隊列
Home | Queues | Topics | Subscribers | Connections | Network | Scheduled | Send Support Queue Name Queue Name Filter Queues: Name Number Of Pending Messages Number Of Consumers Messages Enqueued Messages Dequeued Views Operations text-msg 6 1 3 0 Browse Active Consumers Active Producers Send To Purge Delete
相關文章
- 1. window環境搭建zookeeper,kafka集羣
- 2. Zookeeper搭建集羣環境
- 3. Zookeeper集羣環境搭建
- 4. zookeeper集羣環境搭建
- 5. ZOOKEEPER 集羣環境搭建(在WINDOWS環境下)
- 6. ElasticSearch Window環境下搭建集羣
- 7. ZooKeeper系列（二）—— Zookeeper 單機環境和集羣環境搭建
- 8. ZooKeeper 系列（二）—— Zookeeper單機環境和集羣環境搭建
- 9. Windows環境下搭建ZooKeeper僞集羣
- 10. zookeeper集羣搭建（windows環境下）
- 更多相關文章...
- • Swift 環境搭建 - Swift 教程
- • Rust 環境搭建 - RUST 教程
- • TiDB 在摩拜單車在線數據業務的應用和實踐
- • 適用於PHP初學者的學習線路和建議
相關標籤/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
最新文章
- 1. 融合阿里雲，牛客助您找到心儀好工作
- 2. 解決jdbc(jdbctemplate)在測試類時不報錯在TomCatb部署後報錯
- 3. 解決PyCharm GoLand IntelliJ 等 JetBrains 系列 IDE無法輸入中文
- 4. vue+ant design中關於圖片請求不顯示的問題。
- 5. insufficient memory && Native memory allocation (malloc) failed
- 6. 解決IDEA用Maven創建的Web工程不能創建Java Class文件的問題
- 7. [已解決] Error: Cannot download ‘https://start.spring.io/starter.zip?
- 8. 在idea讓java文件夾正常使用
- 9. Eclipse啓動提示「subversive connector discovery」
- 10. 帥某-技巧-快速轉帖博主文章（article_content）
歡迎關注本站公眾號,獲取更多信息
相關文章