Folks,
Seems, we've got an agreement that the fix is necessary.
Do we need to do except the following?
>> zero linger as default + warning on SSL enabled on JVM before the fix +
warning at documentation + migration notes
On Tue, Nov 3, 2020 at 2:38 PM Steshin Vladimir wrote:
> Ilya, hi.
>
>
Folks,
Should we perform cleanup work before (r)evolutional changes?
My huge proposal is to get rid of things which we don't need anyway
- local caches,
- strange tx modes,
- code overcomplexity because of RollingUpgrade feature never attended at
AI,
- etc,
before choosing the way.
On Tue, Nov 3,
Stepan Pilschikov created IGNITE-13675:
--
Summary: Devnotes in C++ platforms pointed that windows cmake not
yet supported
Key: IGNITE-13675
URL: https://issues.apache.org/jira/browse/IGNITE-13675
Folks,
What may be the comfortable dates of the 2.10 release to finish all
the related development activities?
I suggest release Apache Ignite 2.10 prior to the end of this year and
focus on the 3.0 activities in 2021 with only bug-fix releases for the
2.10.x.
I suggest the following release date
I'm ok with code freeze dates
чт, 5 нояб. 2020 г. в 12:21, Maxim Muzafarov :
> Folks,
>
> What may be the comfortable dates of the 2.10 release to finish all
> the related development activities?
> I suggest release Apache Ignite 2.10 prior to the end of this year and
> focus on the 3.0 activitie
Maxim,
Should we shift the dates so they are not too close to state holidays in
various countries? I'm concerned we won't be getting much activity around
holidays and people who would otherwise spend some time on testing the
release will not be able to do so.
чт, 5 нояб. 2020 г. в 12:21, Maxim Mu
Folks, Alexey,
Sure, I forgot about the Christmas holidays. I don't think we will be
able to complete our release procedures with-in the next few weeks, so
let's shift the dates a bit late. Let's prepare everything prior to
the holidays and set the TC.Bot for the stabilization period on
holidays t
Aleksey Plekhanov created IGNITE-13676:
--
Summary: Java thin client: Message not fully read by client after
SECURITY_VIOLATION error
Key: IGNITE-13676
URL: https://issues.apache.org/jira/browse/IGNITE-13676
Igniters!
I'd like to help with the 2.9.1 release. The scope of this release includes
following issues:
https://issues.apache.org/jira/browse/IGNITE-13676?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.9.1
Maxim Muzafarov agreed to help me with the process and he will be the
release mana
Taras Ledkov created IGNITE-13677:
-
Summary: Calcite integration. TableSpool
Key: IGNITE-13677
URL: https://issues.apache.org/jira/browse/IGNITE-13677
Project: Ignite
Issue Type: Bug
Hi. I'd suggest to add this issue. This is a usability improvement for zk
discovery, and also this patch incorporates fixes for JMX metrics
concurrency issues
[1] -- https://issues.apache.org/jira/browse/IGNITE-13577
чт, 5 нояб. 2020 г., 16:20 Yaroslav Molochkov :
> Igniters!
>
> I'd like to hel
Sergey Uttsel created IGNITE-13678:
--
Summary: Extend test coverage for persistence files dir and WAL
page snapshot records compression
Key: IGNITE-13678
URL: https://issues.apache.org/jira/browse/IGNITE-13678
Ivan, hi!
Sure.
UPD: i am the release manager and will be doing this with Maxim's help
(since i don't have some user permissions)
On Thu, Nov 5, 2020 at 6:24 PM Ivan Daschinsky wrote:
> Hi. I'd suggest to add this issue. This is a usability improvement for zk
> discovery, and also this patch in
Folks,
In my understanding, you need the archives only for features such as PITR.
Considering, that the PITR functionality is not provided in Ignite why do
we have the archives enabled by default?
How about having this feature disabled by default to prevent the following
issues experienced by our
YuJue Li created IGNITE-13679:
-
Summary: Entryprocessor cannot be hot deployed properly via
UriDeploymentSpi
Key: IGNITE-13679
URL: https://issues.apache.org/jira/browse/IGNITE-13679
Project: Ignite
Stanilovsky Evgeny created IGNITE-13680:
---
Summary: Broken formatting rule for vm.swappiness.
Key: IGNITE-13680
URL: https://issues.apache.org/jira/browse/IGNITE-13680
Project: Ignite
Is
Igniters,
Ignite 2.9 announce blog post is published now: [1]
[1] : https://blogs.apache.org/ignite/entry/apache-ignite-2-9-released
пт, 25 сент. 2020 г. в 11:04, Alex Plehanov :
> Denis,
>
> Ok, I will prepare the text soon.
>
> чт, 24 сент. 2020 г. в 23:36, Denis Magda :
>
>> @Alex Plehanov
Hello, everybody!
As far as I know, WAL archive is used for PITP(GridGain feature) and historical
rebalancing.
Facundo seems to have a problem with running out of directory
(/opt/work/walarchive) space.
Currently, WAL archive is cleared at the end of checkpoint. Potentially long
transaction ma
>> For example, when trying to move a segment to the archive.
We cannot do this, we will lost data. We can truncate archived segment if
and only if it is not required for recovery. If last checkpoint marker
points to segment
with lower index, we cannot delete any segment with higher index. So the
o
Hi, Ivan!
I have only described ideas. But here are a few more details.
We can take care not to go beyond DataStorageConfiguration#maxWalArchiveSize.
Before increasing the size of WAL archive (transferring to archive /rollOver,
compression, decompression), we can make sure that there will be e
20 matches
Mail list logo
