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.apache.org/jira/browse/IGNITE-13572
>
> чт, 5 нояб. 2020 г., 19:23 Yaroslav Molochkov :
>
>> Ivan, hi!
>> Sure.
>>
>> UPD: i am the re
Hello!
I believe that we have broken this test suite by merging volatile data
region ticket. I hope that we will fix it promptly.
https://issues.apache.org/jira/browse/IGNITE-13658
Currently, Disk Page Compression only runs in Nightly. I think we should
add it to Run All since the suite may easi
Alexand Polyakov created IGNITE-13687:
-
Summary: Improvement of human-readable format of WAL records
(StandaloneWalRecordsIterator)
Key: IGNITE-13687
URL: https://issues.apache.org/jira/browse/IGNITE-13687
+1 for using GridNioServer as java thin client communication layer.
вс, 8 нояб. 2020 г. в 19:12, Pavel Tupitsyn :
> Igniters,
>
> This is a continuation of "Use Netty for Java thin client" [1],
> I'm starting a new thread for better visibility.
>
> The problems with current Java thin client are:
Sounds like a good idea to me.
Best Regards,
Igor
On Mon, Nov 9, 2020 at 3:32 PM Alex Plehanov
wrote:
> +1 for using GridNioServer as java thin client communication layer.
>
> вс, 8 нояб. 2020 г. в 19:12, Pavel Tupitsyn :
>
> > Igniters,
> >
> > This is a continuation of "Use Netty for Java th
PR's merged.
Please make sure that users who use SSL will be notified to set linger at
2.10 migration doc.
On Fri, Nov 6, 2020 at 1:01 PM Steshin Vladimir wrote:
> The tickets are: [1] disables linger by default and [2] is the doc.
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-1364
I suppose that the best variant -- ability to switch to netty if this lib
is in classpath
пн, 9 нояб. 2020 г. в 15:58, Igor Sapego :
> Sounds like a good idea to me.
>
> Best Regards,
> Igor
>
>
> On Mon, Nov 9, 2020 at 3:32 PM Alex Plehanov
> wrote:
>
> > +1 for using GridNioServer as java thin
YuJue Li created IGNITE-13688:
-
Summary: Ignite Docs: Port Checkpointing&Continuous Mapping from
readme.io
Key: IGNITE-13688
URL: https://issues.apache.org/jira/browse/IGNITE-13688
Project: Ignite
I enforced a lazy flag in DELETE code for tesing, but it is stil running very
slow. I mean that "Lazy" flag cannot solve the problem of running too slow.
On 2020/11/06 09:50:15, Юрий wrote:
> Hi Frank!
>
> There is an old ticket [1] - We will try to prioritize it to finish before
> the end of
Frank,
The ticket doesn't suggest the lazy flag as a workaround. The flag is
supposed to be used to address the performance issue.
How about a workaround on your application side while you're waiting for
this improvement?
- Query all the records for a deletion - "SELECT record_primary_key
Hi Nikolay,
Thank you for reviewing the changes. I have made changes only in the
README.txt file and updated the artifactId so that it matches with pom.xml.
I have also updated the version details in the PR so that it matches with
our release version.
https://github.com/apache/ignite-extensions/
Alexand Polyakov created IGNITE-13689:
-
Summary: Extend test coverage [IGNITE-11512] Add counter left
partition for index rebuild in CacheGroupMetricsMXBean
Key: IGNITE-13689
URL: https://issues.apache.org/jir
Hello guys again!
Does anyone know why we are doing any calculation here
IgniteUtils#adjustedWalHistorySize at all?
Would it be easier to always take the
DataStorageConfiguration#maxWalArchiveSize? It seems that the user can easily
do this himself by changing the value by 1 byte.
06.11.2020, 1
13 matches
Mail list logo
