You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the VFS Lister proxy in the MI cluster, it is necessary to configuretransport.vfs.ClusterAware parameter as per the guidelines outlined in [1]. This parameter should be set as follows:
After configuring the cluster and deploying the VFS proxy, the VFS Lister logs warnings on each node. Here are the warning logs:
2023-10-19 17:18:07,124] WARN {VFSTransportListener} - Although proxy is cluster aware, clustering config are not present, hence running the the polling task in this node
[2023-10-19 17:18:22,403] WARN {VFSTransportListener} - Although proxy is cluster aware, clustering config are not present, hence running the the polling task in this node
[2023-10-19 17:18:37,684] WARN {VFSTransportListener} - Although proxy is cluster aware, clustering config are not present, hence running the the polling task in this node
[2023-10-19 17:18:52,954] WARN {VFSTransportListener} - Although proxy is cluster aware, clustering config are not present, hence running the the polling task in this node
[2023-10-19 17:19:08,239] WARN {VFSTransportListener} - Although proxy is cluster aware, clustering config are not present, hence running the the polling task in this node
[2023-10-19 17:19:23,520] WARN {VFSTransportListener} - Although proxy is cluster aware, clustering config are not present, hence running the the polling task in this node
After few seconds, you will notice a continuous WARNING message in the logs, even if your cluster configuration is correct:
WARN {VFSTransportListener} - Although the proxy is cluster-aware, the required clustering configurations are missing, resulting in the execution of the polling task on this node.
WARN {VFSTransportListener} - Although the proxy is cluster-aware, the required clustering configurations are missing, resulting in the execution of the polling task on this node.
Affected Component
Analytics
Version
MI 4.1.0
Environment Details (with versions)
MI 4.1.0
Relevant Log Output
WARN {VFSTransportListener} - Although the proxy is cluster-aware, the required clustering configurations are missing, resulting in the execution of the polling task on this node.
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered:
veneerac
changed the title
[Patch]-Avoid WARN {VFSTransportListener} -clustering config are not present log when enabling ClusterAware config
[Patch]-Avoid "WARN {VFSTransportListener} -clustering config are not present log when enabling ClusterAware" in MI cluster
Oct 19, 2023
Description
When using the VFS Lister proxy in the MI cluster, it is necessary to configuretransport.vfs.ClusterAware parameter as per the guidelines outlined in [1]. This parameter should be set as follows:
<parameter name="transport.vfs.ClusterAware">true</parameter>
After configuring the cluster and deploying the VFS proxy, the VFS Lister logs warnings on each node. Here are the warning logs:
[1] https://ei.docs.wso2.com/en/7.0.0/micro-integrator/references/synapse-properties/transport-parameters/vfs-transport-parameters/
Steps to Reproduce
Steps to re-produce the issue
Deploy the following proxy configuration in MI nodes :
After few seconds, you will notice a continuous WARNING message in the logs, even if your cluster configuration is correct:
WARN {VFSTransportListener} - Although the proxy is cluster-aware, the required clustering configurations are missing, resulting in the execution of the polling task on this node.
WARN {VFSTransportListener} - Although the proxy is cluster-aware, the required clustering configurations are missing, resulting in the execution of the polling task on this node.
Affected Component
Analytics
Version
MI 4.1.0
Environment Details (with versions)
MI 4.1.0
Relevant Log Output
WARN {VFSTransportListener} - Although the proxy is cluster-aware, the required clustering configurations are missing, resulting in the execution of the polling task on this node.
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered: