[MTCGA]: new failures in builds [5629902] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New Critical Failure in master Cache (Restarts) 1 https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E No changes in the build

Re: New Ignite Docs: Status and Incomplete Items

You might need to empty the browser cache to see the latest changes such as the "C# and .NET Specific" section that was published today. There is some CSS issue that doesn't invalidate browsing caches. It will be fixed soon. - Denis On Tue, Sep 29, 2020 at 4:12 PM Denis Magda wrote: > Pavel,

Re: New Ignite Docs: Status and Incomplete Items

Pavel, I ported all the .NET-specific pages from readme.io with minor changes. The docs are under the "C# and .NET Specific" section down the navigation tree: https://ignite.apache.org/docs/latest The thin-client related docs are under the "Thin Clients" sections. It all makes things look a bit

[MTCGA]: new failures in builds [5629825, 5624517] needs to be handled

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

RE: [EXTERNAL] Re: cpp thin client vector resize

Hi Igor, Your request to see my Read method made me examine it a little closer. The particular vector resize that's the problem is my own fault. Thanks for making me have a look at that again. Thanks, Brett -Original Message- From: Igor Sapego [mailto:isap...@apache.org] Sent:

[DISCUSSION] User-facing API for managing Maintenance Mode

Hello Ignite dev community, As internal implementation of Maintenance Mode [1] is getting closer to finish I want to discuss one more thing: user-facing API (I will use control utility for examples) for managing it. What should be managed? When a node enters MM, it may start some automatic

Re: [DISCUSSION] Maintenance Mode feature

+1 to make new master key name explicit parameter. > 29 сент. 2020 г., в 16:35, Sergey Chugunov > написал(а): > > Hello Nikolay, > >> AFAIKU There is third use-case for this mode. > > Sorry for the late reply. > > I took a look at the code and maintenance mode indeed looks a good match >

Re: [DISCUSSION] Maintenance Mode feature

Hello Nikolay, > AFAIKU There is third use-case for this mode. Sorry for the late reply. I took a look at the code and maintenance mode indeed looks a good match for changing master key situation. I want to clarify only one thing. In current implementation we pass new master key name via

[jira] [Created] (IGNITE-13499) Reconnected node sends old id as security subject id

Stepachev Maksim created IGNITE-13499: - Summary: Reconnected node sends old id as security subject id Key: IGNITE-13499 URL: https://issues.apache.org/jira/browse/IGNITE-13499 Project: Ignite

[jira] [Created] (IGNITE-13498) Thin client throws "unexpected response id" when timeout is too small

Ilya Kasnacheev created IGNITE-13498: Summary: Thin client throws "unexpected response id" when timeout is too small Key: IGNITE-13498 URL: https://issues.apache.org/jira/browse/IGNITE-13498

Rights to jira issues

Good day colleagues! Would like to get access to perform jira tasks - IGNITE-13489 . My account Mikhail Sviridov. I hope for your help

Re: Rights to jira issues

Hi Mikhail, Welcome to Apache Ignite Community! I see two very similar accounts: Mikhail Sviridov (ponchik) Sviridov Mikhail (Sviridov Mikhail) Which is the correct one? Also it would be great if you can tell an email address used for registration in JIRA to avoid ambiguity. 29.09.2020,

[jira] [Created] (IGNITE-13497) [ML] Tutorial examples fails with serialization error

Alexey Zinoviev created IGNITE-13497: Summary: [ML] Tutorial examples fails with serialization error Key: IGNITE-13497 URL: https://issues.apache.org/jira/browse/IGNITE-13497 Project: Ignite

Rights to jira issues

Good day colleagues! Would like to get access to perform jira tasks - https://issues.apache.org/jira/browse/IGNITE-13489. My account Mikhail Sviridov. I hope for your help УВЕДОМЛЕНИЕ О КОНФИДЕНЦИАЛЬНОСТИ: Это электронное сообщение и любые документы, приложенные к нему, содержат конфиденциальную

[jira] [Created] (IGNITE-13496) Java thin: Use non-blocking socket IO

Pavel Tupitsyn created IGNITE-13496: --- Summary: Java thin: Use non-blocking socket IO Key: IGNITE-13496 URL: https://issues.apache.org/jira/browse/IGNITE-13496 Project: Ignite Issue Type:

Re: cpp thin client vector resize

I believe the vector itself should not be a problem. So there is no point in changing std::vector to anything else. It is possible though that there is a problem with code that deals with the vector. Also it would help though not necessary if you could provide profiling results. Best Regards,

[jira] [Created] (IGNITE-13495) ZookeeperDiscoverySpiMBeanImpl#getCoordinator can return invalid node as coordinator

Ivan Daschinskiy created IGNITE-13495: - Summary: ZookeeperDiscoverySpiMBeanImpl#getCoordinator can return invalid node as coordinator Key: IGNITE-13495 URL: https://issues.apache.org/jira/browse/IGNITE-13495

Re: cpp thin client vector resize

Hi, Can you share your ignite::binary::BinaryType::Read method where reading of the std::vector is going on? Also, are your strings large too or only vectors? Best Regards, Igor On Mon, Sep 28, 2020 at 8:29 PM Brett Elliott wrote: > Hello, > > Tl;dr: I'm doing some profiling, and the cpp

[jira] [Created] (IGNITE-13494) Snapshot and start-stop clients test for ducktape

Sergei Ryzhov created IGNITE-13494: -- Summary: Snapshot and start-stop clients test for ducktape Key: IGNITE-13494 URL: https://issues.apache.org/jira/browse/IGNITE-13494 Project: Ignite

[jira] [Created] (IGNITE-13493) Snapshot and node failures (unstable topology) test for ducktape

Sergei Ryzhov created IGNITE-13493: -- Summary: Snapshot and node failures (unstable topology) test for ducktape Key: IGNITE-13493 URL: https://issues.apache.org/jira/browse/IGNITE-13493 Project:

[jira] [Created] (IGNITE-13492) Basic snapshot test for ducktape

Sergei Ryzhov created IGNITE-13492: -- Summary: Basic snapshot test for ducktape Key: IGNITE-13492 URL: https://issues.apache.org/jira/browse/IGNITE-13492 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-13491) Fix incorrect topology snapshot logger output about coordinator change.

], discPort=0, order=2, intOrder=2, lastExchangeTime=1601365285287, loc=false, ver=2.10.0#20200929-sha1:, *isClient=true*], cur=TcpDiscoveryNode [id=9d90f4b0-1374-4147-b7a7-d821f002, consistentId=127.0.0.1:47501, addrs=ArrayList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47501