Vertx集羣配置

時間 2019-11-16

原文原文鏈接

vertx集羣配置

1. pom文件中引入vertx-hazelcast jar

<dependency>
    <groupId>io.vertx</groupId>
    <artifactId>vertx-hazelcast</artifactId>
    <version>${vertx-version}</version>
</dependency>

目前是3.3.3版本java

2. resources內加入hazelcast的配置文件cluster.xml

默認vertx會去找vertx-hazelcast.jar內的default-cluster.xmlnode

若是須要自定義配置文件，須要將其放在classpath下，而且命名爲cluster.xml，即打成fat包後在主目錄下面。nginx

eclipse的java項目只需將default-cluster.xml文件copy一份到resources目錄內，並修更名字爲cluster.xml，打包的時候就會打到classpath的主目錄下。web

3. cluster.xml配置

hazelcast的集羣有3種方式服務器

1. 廣播multicast模式

<multicast enabled="true">
  <multicast-group>224.2.2.3</multicast-group>
  <multicast-port>54327</multicast-port>
</multicast>

若是爲true，同一個網段內的vertx實例會自動發現，並集羣負載均衡

2. ip地址tcp-ip模式

<tcp-ip enabled="true">
  <interface>192.168.1.28</interface>
  <interface>192.168.1.27</interface>
  <interface>192.168.1.26</interface>
</tcp-ip>

須要把要集羣的ip地址列在這裏eclipse

3. aws亞馬遜雲集羣模式

<aws enabled="false">
  <access-key>my-access-key</access-key>
  <secret-key>my-secret-key</secret-key>
  <!--optional, default is us-east-1 -->
  <region>us-west-1</region>
  <!--optional, default is ec2.amazonaws.com. If set, region shouldn't be set as it will override this property -->
  <host-header>ec2.amazonaws.com</host-header>
  <!-- optional, only instances belonging to this group will be discovered, default will try all running instances -->
  <security-group-name>hazelcast-sg</security-group-name>
  <tag-key>type</tag-key>
  <tag-value>hz-nodes</tag-value>
</aws>

通常採用第二種ip地址tcp-ip模式，將其它模式置爲false。總體的cluster.xml文件：socket

<?xml version="1.0" encoding="UTF-8"?>
<hazelcast xsi:schemaLocation="http://www.hazelcast.com/schema/config hazelcast-config-3.2.xsd"
           xmlns="http://www.hazelcast.com/schema/config"
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <properties>
    <property name="hazelcast.mancenter.enabled">false</property>
    <property name="hazelcast.memcache.enabled">false</property>
    <property name="hazelcast.rest.enabled">false</property>
    <property name="hazelcast.wait.seconds.before.join">0</property>
  </properties>

  <group>
    <name>dev</name>
    <password>dev-pass</password>
  </group>
  <management-center enabled="false">http://localhost:8080/mancenter</management-center>
  <network>
    <port auto-increment="true" port-count="10000">5701</port>
    <outbound-ports>
      <!--
      Allowed port range when connecting to other nodes.
      0 or * means use system provided port.
      -->
      <ports>0</ports>
    </outbound-ports>
    <join>
      <multicast enabled="false">
        <multicast-group>224.2.2.3</multicast-group>
        <multicast-port>54327</multicast-port>
      </multicast>
      <tcp-ip enabled="true">
        <interface>192.168.1.28</interface>
        <interface>192.168.1.27</interface>
        <interface>192.168.1.26</interface>
      </tcp-ip>
      <aws enabled="false">
        <access-key>my-access-key</access-key>
        <secret-key>my-secret-key</secret-key>
        <!--optional, default is us-east-1 -->
        <region>us-west-1</region>
        <!--optional, default is ec2.amazonaws.com. If set, region shouldn't be set as it will override this property -->
        <host-header>ec2.amazonaws.com</host-header>
        <!-- optional, only instances belonging to this group will be discovered, default will try all running instances -->
        <security-group-name>hazelcast-sg</security-group-name>
        <tag-key>type</tag-key>
        <tag-value>hz-nodes</tag-value>
      </aws>
    </join>
    <interfaces enabled="false">
      <interface>10.10.1.*</interface>
    </interfaces>
    <ssl enabled="false"/>
    <socket-interceptor enabled="false"/>
    <symmetric-encryption enabled="false">
      <!--
         encryption algorithm such as
         DES/ECB/PKCS5Padding,
         PBEWithMD5AndDES,
         AES/CBC/PKCS5Padding,
         Blowfish,
         DESede
      -->
      <algorithm>PBEWithMD5AndDES</algorithm>
      <!-- salt value to use when generating the secret key -->
      <salt>thesalt</salt>
      <!-- pass phrase to use when generating the secret key -->
      <password>thepass</password>
      <!-- iteration count to use when generating the secret key -->
      <iteration-count>19</iteration-count>
    </symmetric-encryption>
  </network>
  <partition-group enabled="false"/>
  <executor-service name="default">
    <pool-size>16</pool-size>
    <!--Queue capacity. 0 means Integer.MAX_VALUE.-->
    <queue-capacity>0</queue-capacity>
  </executor-service>

  <multimap name="__vertx.subs">

    <!--
        Number of backups. If 1 is set as the backup-count for example,
        then all entries of the map will be copied to another JVM for
        fail-safety. 0 means no backup.
    -->
    <backup-count>1</backup-count>
  </multimap>

  <map name="__vertx.haInfo">

    <!--
        Number of backups. If 1 is set as the backup-count for example,
        then all entries of the map will be copied to another JVM for
        fail-safety. 0 means no backup.
    -->
    <backup-count>1</backup-count>
    <!--
  Maximum number of seconds for each entry to stay in the map. Entries that are
  older than <time-to-live-seconds> and not updated for <time-to-live-seconds>
  will get automatically evicted from the map.
  Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. Default is 0.
-->
    <time-to-live-seconds>0</time-to-live-seconds>
    <!--
  Maximum number of seconds for each entry to stay idle in the map. Entries that are
  idle(not touched) for more than <max-idle-seconds> will get
  automatically evicted from the map. Entry is touched if get, put or containsKey is called.
  Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. Default is 0.
-->
    <max-idle-seconds>0</max-idle-seconds>
    <!--
        Valid values are:
        NONE (no eviction),
        LRU (Least Recently Used),
        LFU (Least Frequently Used).
        NONE is the default.
    -->
    <eviction-policy>NONE</eviction-policy>
    <!--
        Maximum size of the map. When max size is reached,
        map is evicted based on the policy defined.
        Any integer between 0 and Integer.MAX_VALUE. 0 means
        Integer.MAX_VALUE. Default is 0.
    -->
    <max-size policy="PER_NODE">0</max-size>
    <!--
        When max. size is reached, specified percentage of
        the map will be evicted. Any integer between 0 and 100.
        If 25 is set for example, 25% of the entries will
        get evicted.
    -->
    <eviction-percentage>25</eviction-percentage>
    <!--
        While recovering from split-brain (network partitioning),
        map entries in the small cluster will merge into the bigger cluster
        based on the policy set here. When an entry merge into the
        cluster, there might an existing entry with the same key already.
        Values of these entries might be different for that same key.
        Which value should be set for the key? Conflict is resolved by
        the policy set here. Default policy is PutIfAbsentMapMergePolicy

        There are built-in merge policies such as
        com.hazelcast.map.merge.PassThroughMergePolicy; entry will be added if there is no existing entry for the key.
        com.hazelcast.map.merge.PutIfAbsentMapMergePolicy ; entry will be added if the merging entry doesn't exist in the cluster.
        com.hazelcast.map.merge.HigherHitsMapMergePolicy ; entry with the higher hits wins.
        com.hazelcast.map.merge.LatestUpdateMapMergePolicy ; entry with the latest update wins.
    -->
    <merge-policy>com.hazelcast.map.merge.LatestUpdateMapMergePolicy</merge-policy>

  </map>

  <!-- Used internally in Vert.x to implement async locks -->
  <semaphore name="__vertx.*">
    <initial-permits>1</initial-permits>
  </semaphore>

</hazelcast>

4. 集羣方式運行fat.jar包

java -jar F:\work\i5xwxpro\target\i5xwxpro.jar -cluster

分別在對應的服務器上執行命令便可。async

-cluster便是表明集羣方式啓動

5. nginx負載均衡

upstream web{
        server 192.168.1.28:8080;
        server 192.168.1.27:8080;
        server 192.168.1.26:8080;
    }

nginx將請求負載到不一樣的vertx服務器便可tcp

相關標籤/搜索

每日一句

每一个你不满意的现在，都有一个你没有努力的曾经。