te')); return $arr; } /* 遍历用户所有主题 * @param $uid 用户ID * @param int $page 页数 * @param int $pagesize 每页记录条数 * @param bool $desc 排序方式 TRUE降序 FALSE升序 * @param string $key 返回的数组用那一列的值作为 key * @param array $col 查询哪些列 */ function thread_tid_find_by_uid($uid, $page = 1, $pagesize = 1000, $desc = TRUE, $key = 'tid', $col = array()) { if (empty($uid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('uid' => $uid), array('tid' => $orderby), $page, $pagesize, $key, $col); return $arr; } // 遍历栏目下tid 支持数组 $fid = array(1,2,3) function thread_tid_find_by_fid($fid, $page = 1, $pagesize = 1000, $desc = TRUE) { if (empty($fid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('fid' => $fid), array('tid' => $orderby), $page, $pagesize, 'tid', array('tid', 'verify_date')); return $arr; } function thread_tid_delete($tid) { if (empty($tid)) return FALSE; $r = thread_tid__delete(array('tid' => $tid)); return $r; } function thread_tid_count() { $n = thread_tid__count(); return $n; } // 统计用户主题数 大数量下严谨使用非主键统计 function thread_uid_count($uid) { $n = thread_tid__count(array('uid' => $uid)); return $n; } // 统计栏目主题数 大数量下严谨使用非主键统计 function thread_fid_count($fid) { $n = thread_tid__count(array('fid' => $fid)); return $n; } ?>docker - Hazelcast Cache Issue: Containers Become Unresponsive During Business Instance Restart - Stack Overflow

科技改变生活-雨落星辰 - 所有的伟大,都源于一个勇敢的开始

    最新消息：雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客
    你的位置： 首页>programmer>docker - Hazelcast Cache Issue: Containers Become Unresponsive During Business Instance Restart - Stack Overflow

    docker - Hazelcast Cache Issue: Containers Become Unresponsive During Business Instance Restart - Stack Overflow

    programmeradmin3浏览0评论

    I'm experiencing a functional issue in my application, which is composed of several containers, including 10 business instances for scaling purposes. When I perform requests to /customDumpcacheBDD and /getAllVersions, which interact with the cache using Hazelcast, all other containers become unavailable and do not respond to requests during the restart of a business instance. Is this behavior normal? If not, could you provide some insights or suggestions on how to address this issue?

    During start of new container, in other containers i have some logs telling that the current cluster node is connecting to the new node with IP adress and repartionning of maps over the cluster

    my hazelcast configuration:

    <hazelcast xsi:schemaLocation=" hazelcast-config-3.11.xsd"
       xmlns=";
       xmlns:xsi=";>
<group>

    <name>bl</name>
    <password>bl-pass</password>
</group>
<network>
    <!--        All values here will be overridden by hocon config, but have to exist -->
    <port auto-increment="false">3603</port>
    <join>
        <multicast enabled="false">
            <multicast-group>224.2.2.3</multicast-group>
            <multicast-port>54327</multicast-port>
        </multicast>
        <tcp-ip enabled="true">
            <member>localhost:3603</member>
        </tcp-ip>
    </join>
</network>
<properties>
    <property name="hazelcast.map.cleanup.delay.seconds">1</property>
    <property name="hazelcast.jmx">true</property>
</properties>

<!-- Default configurations -->

<map name="CNG_BL_MAILBOX">
    <backup-count>0</backup-count>
    <async-backup-count>1</async-backup-count>
    <indexes>
        <index ordered="false">pid</index>
    </indexes>
</map>



<!-- COMPONENT -->

<map name="INSTRUCTION_MAP_NAME">
    <backup-count>0</backup-count>
    <async-backup-count>1</async-backup-count>
</map>

<map name="MAP_2">
    <backup-count>0</backup-count>
    <async-backup-count>1</async-backup-count>
    <indexes>
        <index ordered="false">media</index>
        <index ordered="false">spiedUserUuid</index>
        <index ordered="false">spiedEntityUuid</index>
        <index ordered="false">spiedEntityType</index>
        <index ordered="false">spyUserUuid</index>
        <index ordered="false">spyFunction</index>
    </indexes>
</map>

<map name="SUPERVISOR_STATUS">
    <backup-count>0</backup-count>
    <async-backup-count>1</async-backup-count>
    <near-cache>
        <in-memory-format>OBJECT</in-memory-format>
        <invalidate-on-change>true</invalidate-on-change>
        <cache-local-entries>true</cache-local-entries>
    </near-cache>
</map>

<map name="PROCESS">
    <backup-count>0</backup-count>
    <async-backup-count>1</async-backup-count>
    <indexes>
        <index ordered="false">csrUuid</index>
        <index ordered="false">contactConnectionId</index>
        <index ordered="false">csrConnectionId</index>
        <index ordered="false">supervisedTransferUuid</index>
        <index ordered="false">mediaEntryPointUuid</index>
    </indexes>
</map>

<map name="NAME_MAP" >
    <backup-count>0</backup-count>
    <async-backup-count>1</async-backup-count>
</map>

<map>
    <map name="strategies">
    <eviction-policy>LRU</eviction-policy>
    <max-size policy="PER_NODE">10</max-size>
    <time-to-live-seconds>60</time-to-live-seconds>
    <max-idle-seconds>60</max-idle-seconds>
</map>

<map name="spring:session:sessions">
    <attributes>
        <attribute extractor=".springframework.session.hazelcast.PrincipalNameExtractor">principalName</attribute>
    </attributes>
    <indexes>
        <index>principalName</index>
    </indexes>
</map>

<serialization>
    <serializers>
        <serializer class-name=".springframework.session.hazelcast.HazelcastSessionSerializer"
                    type-class=".springframework.session.MapSession"/>
    </serializers>
</serialization>

    与本文相关的文章

    发布评论

    评论列表(0)

    1. 暂无评论