集群中沒有以集群模式在商店中發布的API-WSO2 API Manager 2.0.0

Question

我已部署具有五個VM的Clustered API Manager 2.0.0安裝：

VM1共享密鑰管理器+分析節點：

• 使用/var/wso2am/bin/wso2server.sh -Dprofile = api-key-manager運行的專用密鑰管理器
• 由/var/wso2am-analytics/bin/wso2server.sh使用默認端口偏移（+1）運行的wso2am Analytics

虛擬機2

/var/wso2am/bin/wso2server.sh -Dprofile = gateway-manager以默認偏移量（+0）運行的專用網關節點

虛擬機3

/var/wso2am/var/wso2am/bin/wso2server.sh -Dprofile = api-store以默認偏移（+0）運行的專用存儲節點

虛擬機4

/var/wso2am/bin/wso2server.sh以默認偏移量（+0）運行的專用流量管理器節點-sh -Dprofile = traffic-manager

虛擬機5

/var/wso2am/bin/wso2server.sh -Dprofile = api-publisher以默認偏移量（+0）運行的專用發布者節點

我完成了Clustering API Manager 2.0.0的所有步驟

我使用VM3和VM5設置了兩個群集節點，並且在存儲和發布者節點上都看到/ _system / governance / apimgt / applicationdata注冊表。 我還可以瀏覽商店Carbon Admin界面上的發布者節點中創建的API（元數據->列表> API）

但是在VM3的專用存儲葉端（“ VM3 /存儲”）中沒有API。

同時如果我將在發布者節點上打開“ VM5 / store”頁面，我可以看到發布的API很好

我應該檢查什么？

UPD：

這些API被推送到具有錯誤“創建”的生命周期狀態的商店節點，該狀態沒有相應更新。 我嘗試在商店節點上手動更改Lifecycle Status，並且API以商店模式發布就很好了。

看來生命周期狀態實時更新到存儲節點存在問題。 我該如何解決？

UPD2：

這是我在商店的axis2.xml配置（IP為xxx15）

   <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>

`

這是我在發布服務器上的axis2.xml配置（IP為xxx17）

    <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>