Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to finalize
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to finalize
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to finalize
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to finalize
I'm -1 for creating a new repo.
Also I support Maxim's plan for 3.0
пт, 13 нояб. 2020 г. в 15:50, Maxim Muzafarov :
> Val,
>
>
> Why *creating a new repo* is the main point we faced with? Would it be
> better to discuss the components design approach and scope management
> first suggested by Serg
Ilya Kasnacheev created IGNITE-13706:
Summary: Thin Client Put_All uses LinkedHashMap, causes warning
and may deadlock
Key: IGNITE-13706
URL: https://issues.apache.org/jira/browse/IGNITE-13706
Pro
Hi Ilya! You can see the meeting link after RVSP on meetup.com
https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/273935662/
This mailing list is open and to announce the zoom link is not the best
thing to do. I can not understand why it's fun to interrupt zoom calls, but
some people (and b
Val,
Why *creating a new repo* is the main point we faced with? Would it be
better to discuss the components design approach and scope management
first suggested by Sergey Chugunov? I doubt that new repo will solve
move us forward.
Currently, I'm -1 to create a new repo with the inputs above.
I
=8331a61c-ea93-4bf5-bc8c-b24c032068d0,
consistentId=tkles-pprb00188.vm.esrt.cloud.sbrf.ru, addrs=ArrayList
[10.53.125.160], sockAddrs=HashSet
[tkles-pprb00188.vm.esrt.cloud.sbrf.ru/10.53.125.160:47500], discPort=47500,
order=1, intOrder=1, lastExchangeTime=1605268203598, loc=false,
ver=2.10.0#20201113
Igniters, hello!
I think the scope of 2.9.1 is finalized.
> On 9 Nov 2020, at 12:04, Yaroslav Molochkov wrote:
>
> Ivan, thanks!
>
> Added it to the list.
>
>> On 8 Nov 2020, at 14:13, Ivan Daschinsky wrote:
>>
>> Yaroslav, there is another bug for 2.9.1 release
>> https://issues.apach
Vladimir Steshin created IGNITE-13704:
-
Summary: Try failuredetectionTimeout==500 in ducktape integration
test.
Key: IGNITE-13704
URL: https://issues.apache.org/jira/browse/IGNITE-13704
Project: I
>> b. Implement IEP-61 - Common Replication Infrastructure
I suppose, that this is the main cause of the current discussion.
I hardly believe that this activity can be done without at least creating a
completely new branch.
пт, 13 нояб. 2020 г. в 11:12, Nikolay Izhikov :
> My suggestion:
>
> 1. R
Anton Vinogradov created IGNITE-13703:
-
Summary: Check difference between TcpDiscovery and
ZookeeperDiscovery at Cellular switch
Key: IGNITE-13703
URL: https://issues.apache.org/jira/browse/IGNITE-13703
My suggestion:
1. Reduce Ignite3 scope to the following:
a. Delete all deprecated API and support of obsolete internal protocols.
b. Implement IEP-61 - Common Replication Infrastructure
c. Implement new Ignite management tool ignitectl as suggested during
Ignite3 discussio
14 matches
Mail list logo
