Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

observation : Inconsistent NoLivingConnectionsError while regarding a new application #544

Closed
PrathibaJee opened this issue Jun 16, 2024 · 2 comments
Assignees
Labels
help wanted Extra attention is needed

Comments

@PrathibaJee
Copy link
Collaborator

Noticed the following error inconsistently while regarding an application to the ApplicationLayerTopology.

NoLivingConnectionsError: Given the configuration, the ConnectionPool was not able to find a usable Connection for this request.
    at makeRequest (C:\Users\NQ10024811\Desktop\SDNApplicationLayerVersion2.1.1\ApplicationLayerTopology\server\node_modules\@elastic\elasticsearch\lib\Transport.js:203:43)
    at prepareRequest (C:\Users\NQ10024811\Desktop\SDNApplicationLayerVersion2.1.1\ApplicationLayerTopology\server\node_modules\@elastic\elasticsearch\lib\Transport.js:460:11)
    at Transport.request (C:\Users\NQ10024811\Desktop\SDNApplicationLayerVersion2.1.1\ApplicationLayerTopology\server\node_modules\@elastic\elasticsearch\lib\Transport.js:503:7)
    at Client.searchApi [as search] (C:\Users\NQ10024811\Desktop\SDNApplicationLayerVersion2.1.1\ApplicationLayerTopology\server\node_modules\@elastic\elasticsearch\api\api\search.js:61:25)
    at getLinkOfTheOperationAsync (C:\Users\NQ10024811\Desktop\SDNApplicationLayerVersion2.1.1\ApplicationLayerTopology\server\service\individualServices\LinkServices.js:206:28)
    at async exports.prepareLinkChangeNotificationForwardingsAsync (C:\Users\NQ10024811\Desktop\SDNApplicationLayerVersion2.1.1\ApplicationLayerTopology\server\service\individualServices\LinkServices.js:568:24)
    at async UpdateControlConstructAndLinksInDataBase (C:\Users\NQ10024811\Desktop\SDNApplicationLayerVersion2.1.1\ApplicationLayerTopology\server\service\individualServices\regardApplicationAutomation.js:507:24)
    at async RequestForInquiringTopologyChangeInformationWithDefaultKey (C:\Users\NQ10024811\Desktop\SDNApplicationLayerVersion2.1.1\ApplicationLayerTopology\server\service\individualServices\regardApplicationAutomation.js:115:39)
    at async exports.regardApplication (C:\Users\NQ10024811\Desktop\SDNApplicationLayerVersion2.1.1\ApplicationLayerTopology\server\service\individualServices\regardApplicationAutomation.js:31:14)
    at async exports.regardApplication (C:\Users\NQ10024811\Desktop\SDNApplicationLayerVersion2.1.1\ApplicationLayerTopology\server\service\IndividualServicesService.js:767:20) {
  meta: undefined
}
NewApplicationCausesRequestForTopologyChangeInformation.RequestForInquiringTopologyChangeInformationWithDefaultKey has been triggered with response 200

Issue occurring inconsistently , let me know whether you too observe this issue.

@PrathibaJee PrathibaJee added the help wanted Extra attention is needed label Jun 16, 2024
@PrathibaJee PrathibaJee added this to the ALT v2.1.1_impl milestone Jun 16, 2024
@IswaryaaS
Copy link
Collaborator

we could see, it occurs inconsistently and under different places.
As discussed, we can include a retry mechanism while we are getting this error on connection to ES.

@PrathibaJee PrathibaJee self-assigned this Jun 22, 2024
PrathibaJee added a commit that referenced this issue Jun 22, 2024
@PrathibaJee
Copy link
Collaborator Author

@IswaryaaS , many thanks for helping in resolving this issue.
Issue merged in PR #546 , hence closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants