Closed AntonyLittle closed 2 weeks ago
Hey @AntonyLittle,
Thank you for your issue and interest of Streamiz. I will try to reproduce the issue and fix it as soon as possible.
Quick question : If you have a large amount of data, why not choosing RocksDb as a persistent layer of storage ?
Best regards,
@AntonyLittle ,
Are you able to test with this specific branch ? https://github.com/LGouellec/streamiz/tree/fix/concurrent-issue-window
Thanks,
Certainly! We've had some success with adding mutex locking also, but we are still testing it. Hopeful that your fix will do the job :)
@LGouellec Appologies for the delay, we've had some urgent issues. We should be able to report back on the status of your fix today or tomorrow.
@AntonyLittle No worries at all ;)
Can confirm that your changes have fixed the issue. Thank you! Are you able to provide a nuget release?
Awesome @AntonyLittle ! This fix will be part the 1.7.0 release, coming soon.
Awesome @AntonyLittle ! This fix will be part the 1.7.0 release, coming soon.
Do you know roughly how soon "soon" might be? Is there any chance of you doing a 1.6.1 release with just the fix added?
@AntonyLittle Will be before end of November, I'll publish a 1.7.0-RC1 which will contains this fix in 1 week.
Description
I am seeing the following exception when using Windowed KTables in Streamiz 1.6.0:
How to reproduce
Create materializer thusly:
Topology is created like so:
Access store thusly:
The issue does not occur every time, but only with large volumes of data. I suspect the issue is due to the Streamiz framework calling Fetch() at the same time as our code.
Checklist
Please provide the following information: