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

[BUG] RAG processor throws null pointer exception #2983

Open
ylwu-amzn opened this issue Sep 25, 2024 · 3 comments · May be fixed by #3057
Open

[BUG] RAG processor throws null pointer exception #2983

ylwu-amzn opened this issue Sep 25, 2024 · 3 comments · May be fixed by #3057
Assignees
Labels
bug Something isn't working

Comments

@ylwu-amzn
Copy link
Collaborator

What is the bug?
Run RAG processor on multi-node cluster without dedicated master node. Can see such error

Cannot invoke "java.lang.Integer.intValue()" because "this.interactionSize" is null

How can one reproduce the bug?
Steps to reproduce the behavior:

  1. Set up multi-node cluster with 3 nodes, all nodes have master and data role
  2. Run RAG processor

What is the expected behavior?
Should not throw exception

What is your host/environment?

  • OS: Linux
  • Version 2.15

Do you have any screenshots?
No

Do you have any additional context?
Log

java.lang.NullPointerException: Cannot invoke "java.lang.Integer.intValue()" because "this.interactionSize" is null
    at org.opensearch.searchpipelines.questionanswering.generative.ext.GenerativeQAParameters.writeTo(GenerativeQAParameters.java:197)
    at org.opensearch.searchpipelines.questionanswering.generative.ext.GenerativeQAParamExtBuilder.writeTo(GenerativeQAParamExtBuilder.java:75)
@ylwu-amzn ylwu-amzn added bug Something isn't working untriaged labels Sep 25, 2024
@ylwu-amzn ylwu-amzn self-assigned this Sep 25, 2024
@pyek-bot
Copy link

Can you assign this to me?

@ylwu-amzn ylwu-amzn assigned pyek-bot and unassigned ylwu-amzn Sep 25, 2024
@ylwu-amzn
Copy link
Collaborator Author

Sure, assigned to you @pyek-bot

@pyek-bot
Copy link

pyek-bot commented Oct 1, 2024

Bug is currently not reproduceable on 2.16 or 2.17. It has been fixed, so this should not be a blocker for the new version. However, determining the exact change will require further investigation to backport to 2.15.

*Edit: bug appears to be flaky and intermittent in nature on all versions, will require further investigation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
2 participants