Amelchev Nikita created IGNITE-13861:
Summary: Add logical/physical reads checks to existing tests
Key: IGNITE-13861
URL: https://issues.apache.org/jira/browse/IGNITE-13861
Project: Ignite
Amelchev Nikita created IGNITE-13860:
Summary: Provide the tool to build cluster performance report
Key: IGNITE-13860
URL: https://issues.apache.org/jira/browse/IGNITE-13860
Project: Ignite
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
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
Kirill,
thanks for adding motivation to the issue description.
On Wed, Dec 9, 2020 at 5:24 PM Andrey Gura wrote:
>
> Kiriill,
>
> Issue description contains the following:
>
> > At the moment, WAL archive is cleared at the end of the checkpoint, which
> > does not seem correct and needs to be
Thanks, Sergey! Looks good to me.
-Val
On Tue, Dec 15, 2020 at 12:12 AM Sergey Chugunov
wrote:
> Val,
>
> Your comments make total sense to me, I've fixed them and updated pull
> request. Please take a look at my code when you have time.
>
> I also added a port range configuration to enable
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-nightly MVCC Cache 7
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_MvccCache7?branch=%3Cdefault%3E
No changes in the build
Hi Yaroslav,
Do we need to update documentation?
-
Denis
On Mon, Dec 14, 2020 at 11:34 PM Yaroslav Molochkov
wrote:
> Dear Community,
>
> I have uploaded release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/2.9.1-rc1/
>
Pavel Tupitsyn created IGNITE-13859:
---
Summary: .NET: Build scripts and instructions cleanup
Key: IGNITE-13859
URL: https://issues.apache.org/jira/browse/IGNITE-13859
Project: Ignite
Issue
Igniters, JFYI
According to discussion [1] there are no any objections to usage of
Java 11 for Ignite 3 development as target Java language and platform
version. So pom.xml for Ignite 3 is already updated.
1.
Vyacheslav Koptilin created IGNITE-13858:
Summary: Enabling near cache on a client node may lead to blocking
eviction on server nodes
Key: IGNITE-13858
URL:
I don't believe Java 7 was LTS, and I hope that others will have upgraded long
before that. If that is the release timeframe for 3.0, then I suppose that
would makes sense, I would still doubt that people would be going newer than
java 11, just my opinion of what I'm seeing.
Regards
~adam
Hello!
+1 (binding)
Checked that dotnet & C++ build from source.
(NB it's not obvious what to do next when dotnet node is built, but it's
the same in 2.9.0)
Checked that dotnet & C++ node starts from a slim binary.
Checked that deb package installs & service starts. Checked sqlline from
slim
+1 (binding)
(Built Ignite.NET from sources, started from binary package, checked
examples)
On Tue, Dec 15, 2020 at 10:34 AM Yaroslav Molochkov
wrote:
> Dear Community,
>
> I have uploaded release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/2.9.1-rc1/
>
kgusakov opened a new pull request #8:
URL: https://github.com/apache/ignite-3/pull/8
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
Kirill Gusakov created IGNITE-13857:
---
Summary: Update Ignite-3.0 java to 11 version
Key: IGNITE-13857
URL: https://issues.apache.org/jira/browse/IGNITE-13857
Project: Ignite
Issue Type:
Ilya Kazakov created IGNITE-13856:
-
Summary: Superlinear performance of
DirectByteBufferStreamImplV2.writeMessage(msg, writer)
Key: IGNITE-13856
URL: https://issues.apache.org/jira/browse/IGNITE-13856
Tanmay Ambre created IGNITE-13855:
-
Summary: Integration with micrometer.io as part of integration
with spring-boot
Key: IGNITE-13855
URL: https://issues.apache.org/jira/browse/IGNITE-13855
Project:
Hello!
I guess Ignite 3.0 will be ready for production use somewhere in 2022,
realistically. By that time, Java 8 will be long enough out of support so
that most companies will actually forbid its use, WRT vulnerabilities et
all.
After all we have managed to upgrade from Java 7 to Java 8 and
Val,
Your comments make total sense to me, I've fixed them and updated pull
request. Please take a look at my code when you have time.
I also added a port range configuration to enable starting multiple
instances of ignite without specifying port manually for each instance.
--
Best Regards,
+1
Best regards,
Alexander
вт, 15 дек. 2020 г. в 10:59, Konstantin Orlov :
> +1
>
> --
> Regards,
> Konstantin Orlov
> Software Engineer, St. Petersburg
> +7 (921) 445-65-75
> https://www.gridgain.com
> Powered by Apache® Ignite™
>
>
>
>
21 matches
Mail list logo
