没有以群集模式在存储区上发布api -- wso2 api管理器2.0.0

Question

我使用五个VM部署了集群API管理器2.0.0安装：

VM1共享密钥管理器+分析节点：

• 使用/var/wso2am/bin/wso2server.sh -Dprofile=api- key -manager运行的专用密钥管理器
• 使用默认端口偏移(+1)运行/var/ wso2am - analytics /bin/wso2server.sh的wso2am分析

VM2

通过/var/wso2am/bin/wso2server.sh -Dprofile=网关管理器运行默认偏移量(+0)的专用网关节点

VM3

通过/var/wso2am/var/wso2am/bin/wso2server.sh-Dprofile=api存储运行默认偏移量(+0)的专用存储节点

VM4

使用默认偏移量(+0)运行的专用流量管理器节点由/var/wso2am/bin/wso2server.sh-Dprofile=流量管理器运行

VM5

通过/var/wso2am/bin/wso2server.sh -Dprofile=api-publisher运行默认偏移量(+0)的专用发布节点

我在聚类API管理器2.0.0中完成了所有步骤

我使用VM3和VM5设置了两个集群节点，并在存储节点和发布节点上看到/_system/governance/apimgt/applicationdata注册表。我还可以在存储碳管理界面(元数据->list> APIs )上浏览publisher节点中创建的API。

但是在VM3上的专用存储前端(“VM3 3/ store”)中没有出现API。

同时，如果我将在publisher节点上打开"VM5/store“页面，我可以看到已发布的API。

我该查些什么？

UPD:

API被推送到具有错误的生命周期状态的存储节点，而“创建”状态没有相应更新。我尝试在存储节点上手动更改生命周期状态，API在存储模式下发布也不错。

因此，问题似乎在于对存储节点的生命周期状态实时更新。我怎么才能修好它？

UPD2:

下面是我在商店中的axis2.xml配置(ip是x.15)

   <clustering class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent"
                enable="true">
   <parameter name="membershipScheme">wka</parameter>
   <parameter name="domain">wso2.carbon.domain</parameter>
   <parameter name="localMemberHost">x.x.x.15</parameter>
   <parameter name="localMemberPort">4000</parameter>
        <members>
            <member>
                <hostName>x.x.x.17</hostName>
                <port>4000</port>
            </member>
            <member>
                <hostName>x.x.x.15</hostName>
                <port>4000</port>
            </member>            
        </members>

`

下面是我在publisher上的axis2.xml配置(ip是x.17)

    <clustering class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent"
                enable="true">
   <parameter name="membershipScheme">wka</parameter>
   <parameter name="domain">wso2.carbon.domain</parameter>
   <parameter name="localMemberHost">x.x.x.17</parameter>
   <parameter name="localMemberPort">4000</parameter>

        <members>
            <member>
                <hostName>x.x.x.15</hostName>
                <port>4000</port>
            </member>
            <member>
                <hostName>x.x.x.17</hostName>
                <port>4000</port>
            </member>            
        </members>

存储日志文件中的消息

   Cluster domain: wso2.carbon.domain
   Loading hazelcast configuration from axis2 clustering configuration
   Using wka based membership management scheme
   Added member: Host:x.x.x.17, Remote Host:null, Port: 4000, HTTP:-1, HTTPS:-1, Domain: null, Sub-domain:null, Active:true
   Added member: Host:x.x.x.15, Remote Host:null, Port: 4000, HTTP:-1, HTTPS:-1, Domain: null, Sub-domain:null, Active:true
   Hazelcast initialized in 9167ms
   Local member: [3c9c1b66-9ad9-4e4f-8d7e-de2864e8d56d] - Host:x.x.x.15, Remote Host:null, Port: 4000, HTTP:8280, HTTPS:8243, Domain: wso2.carbon.domain, Sub-domain:worker, Active:true
   Cluster initialization completed
   Task service starting in CLUSTERED mode...
   Successfully Initialized Eventing on Registry

发布日志文件中的消息

Cluster domain: wso2.carbon.domain
Loading hazelcast configuration from axis2 clustering configuration
Using wka based membership management scheme
Added member: Host:x.x.x.15, Remote Host:null, Port: 4000, HTTP:-1, HTTPS:-1, Domain: null, Sub-domain:null, Active:true
Added member: Host:x.x.x.17, Remote Host:null, Port: 4000, HTTP:-1, HTTPS:-1, Domain: null, Sub-domain:null, Active:true
Hazelcast initialized in 10380ms
Local member: [094f544b-1cfe-41b1-9a5f-0664aefc1ba5] - Host:x.x.x.17, Remote Host:null, Port: 4000, HTTP:8280, HTTPS:8243, Domain: wso2.carbon.domain, Sub-domain:worker, Active:true
Cluster initialization completed
Error in instantiating class : org.wso2.carbon.apimgt.usage.publisher.APIMgtThrottleUsageHandler
Sequence Deployment from the file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/_throttle_out_handler_.xml : Failed.
Deployment of the Synapse Artifact from file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/_throttle_out_handler_.xml : Failed!
The file has been backed up into : NO_BACKUP_ON_WORKER.INFO
Deployment of synapse artifact failed. Error reading /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/_throttle_out_handler_.xml : Sequence Deployment from the file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/_throttle_out_handler_.xml : Failed.
org.apache.axis2.deployment.DeploymentException: Sequence Deployment from the file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/_throttle_out_handler_.xml : Failed.
Error in instantiating class : org.wso2.carbon.apimgt.usage.publisher.APIMgtFaultHandler
Sequence Deployment from the file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/fault.xml : Failed.
Deployment of the Synapse Artifact from file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/fault.xml : Failed!
The file has been backed up into : NO_BACKUP_ON_WORKER.INFO
Deployment of synapse artifact failed. Error reading /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/fault.xml : Sequence Deployment from the file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/fault.xml : Failed.
org.apache.axis2.deployment.DeploymentException: Sequence Deployment from the file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/fault.xml : Failed.
Task service starting in CLUSTERED mode...
Successfully Initialized Eventing on Registry

Answer 1

这有两个原因。

1)在axis2.xml中使用<localMemberHost>中的主机名和<members>部分的主机名。用IP代替。

2) axis2.xml中的<parameter name="domain">wso2.carbon.domain</parameter>在存储和发布时没有相同的值

更新：附加配置看起来很好。因此，另一种可能是，这是一个注册表索引问题。为此，您可以尝试重新编制索引。

在存储节点中更新<lastAccessTimeLocation>值registry.xml，然后重新启动服务器。

<lastAccessTimeLocation>/_system/local/repository/components/org.wso2.carbon.registry/indexing/lastaccesstime2</lastAccessTimeLocation>