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

transmission mistake using jxioConnection #7

Open
stevenybw opened this issue Oct 12, 2014 · 5 comments
Open

transmission mistake using jxioConnection #7

stevenybw opened this issue Oct 12, 2014 · 5 comments

Comments

@stevenybw
Copy link

It's very strange. I write two simple programs using jxioConnection module for RDMA communication, one for sending a file, and another for receiving a file. Problem occurs when the file is large: the file received is possibly larger than the original file. According to observation, when the file is less than 512MB, file transfer is always correct. However, if the size is 1GB, there're about 30% attempts where transfer is wrong. But if the size is 2GB, 10% is wrong.

It seems that transfer using JXIO is not guaranteed to be correct, is JXIO is designed to be that?

@dinal
Copy link
Contributor

dinal commented Oct 13, 2014

we found an issue in jxioConnection example code in com.mellanox.jxio.tests.benchmarks.jxioConnection
I will push a fix shortly.

if your code is based on it that may explain the behavior you see. if not, I would like to know more details on what you are doing, Can you share your code?

@cwk32
Copy link

cwk32 commented Oct 14, 2014

worry about that bug, may also affect me.

when can this fix be finished?

@dinal
Copy link
Contributor

dinal commented Oct 14, 2014

I believe it will be fixed during next week

@rosenbaumalex
Copy link
Collaborator

The bug is in JXIO, and happens when ServerSession:close() is called while there are responses being processes (transaction not completed fully completed).
JxioConenction InputStream uses this flow and that is why you experience this issue.

@dinal
Copy link
Contributor

dinal commented Oct 20, 2014

The issue we found is fixed. We’ll appreciate if you can verify

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants