Hello Ilya !
>Hello!
>
>In the test GridDifferentLocalDeploymentSelfTest, I can see that some count
>of internal data structure yanked from a class field is not equal expected
>(without the fix).
GridDifferentLocalDeploymentSelfTest checks that inner deployment machinery are
not «leak» the
As previously agreed, ticket [1], examples of concurrent tests you can find
here GridDifferentLocalDeploymentSelfTest and here
IgniteExplicitImplicitDeploymentSelfTest , TC in progress. Fabric — possibly i
mention incorrect word here, more clear it need to be — factory )
I suppose additional
Zhenya,
Could you clarify what you mean by "one instance is shared between numerous
of fabric"? What is the exact scenario and what are the implications of
running multiple compute tasks in parallel? A code sample demonstrating the
scenario might be helpful as well.
-Val
On Fri, Feb 5, 2021 at
Hi Zhenya,
I don't understand your proposal without a patch.
I see that you want to mark as @Depricate three methods in IgniteCompute
interface, but what will you give instead of?
It seems to me, this interface can invoke some job without contains a class
locally.
How will this be supported in
Hello!
In the test GridDifferentLocalDeploymentSelfTest, I can see that some count
of internal data structure yanked from a class field is not equal expected
(without the fix).
But I don't see why it is a problem. Do you have some reproducer where bad
things (such as task failure, deadlock,
Ilya, as previously agreed, ticket [1], examples of concurrent tests you can
find here GridDifferentLocalDeploymentSelfTest and here
IgniteExplicitImplicitDeploymentSelfTest , TC in progress.
thanks !
[1] https://issues.apache.org/jira/browse/IGNITE-14131
>Hello!
>
>Please publish
Hello!
Please publish it. I don't see why not.
Regards,
--
Ilya Kasnacheev
чт, 28 янв. 2021 г. в 14:28, Zhenya Stanilovsky :
>
>
> Hi Ilya , of course it contains in my PR (i don`t know if it shout be
> published before this discussion will be finished).
> Little changes from single thread
Hi Ilya , of course it contains in my PR (i don`t know if it shout be published
before this discussion will be finished).
Little changes from single thread into multiple, for example here [1] will
highlight a problem, or i can just publish my PR.
[1]
Hello!
Do you have some kind of reproducer which demonstrates the issue?
Regards,
--
Ilya Kasnacheev
чт, 28 янв. 2021 г. в 10:32, Zhenya Stanilovsky :
>
> Hello Igniters !
> In the process of Ignite usage i found that some part of Compute
> functionality are thread unsafe and seems was
Hello Igniters !
In the process of Ignite usage i found that some part of Compute functionality
are thread unsafe and seems was designed with such limitations initially.
Example : one (client, but it doesn`t matter at all) instance is shared between
numerous of fabric, all of them calls
10 matches
Mail list logo
