t; > >
> > https://repository.apache.org/content/repositories/orgapacheignite-1556/
> > > > Tag: https://github.com/apache/ignite-3/tree/3.0.0-beta1-rc2
> > > >
> > > > +1 - accept Apache Ignite 3.0.0-beta1 RC2
> > > > 0 - don't care either way
> > > > -1 - DO NOT accept Apache Ignite 3.0.0-beta1 RC2 (explain why)
> > > >
> > > > Voting guidelines: https://www.apache.org/foundation/voting.html
> > > > How to verify the release:
> > https://www.apache.org/info/verification.html
> > > >
> > > > The vote will be closed on Wednesday, 16 November 2022, 18:00:00 (UTC
> > > time)
> > > >
> > > >
> > >
> > https://www.timeanddate.com/countdown/generic?iso=20221116T18=1440=Apache+Ignite+3.0.0-beta1+RC2=cursive=1
> > > >
> > > > Thanks,
> > > > S.
> > > >
> > >
> >
--
Vladislav Pyatkov
3 - related to
> >> >>>> support
> >> >>>>>> indexes by SQL
> >> >>>>>> https://issues.apache.org/jira/browse/IGNITE-17655 - related to
> >> >>>> support
> >> >>>>>> indexes by SQL
> >> >>>>>>
> >> >>>>>> ср, 19 окт. 2022 г. в 12:11, Вячеслав Коптилин <
> >> >>>> slava.kopti...@gmail.com
> >> >>>>>> :
> >> >>>>>>
> >> >>>>>>> Hello Alexander,
> >> >>>>>>>
> >> >>>>>>> Thank you for pointing this out. I fully support including RO
> >> >>>>>> transactions
> >> >>>>>>> into the scope of Ignite 3.0.0-beta1 release.
> >> >>>>>>>
> >> >>>>>>> Thanks,
> >> >>>>>>> S.
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>> ср, 19 окт. 2022 г. в 11:42, Alexander Lapin <
> lapin1...@gmail.com
> >> >:
> >> >>>>>>>
> >> >>>>>>>> Igniters,
> >> >>>>>>>>
> >> >>>>>>>> I would like to add following tickets to ignite-3.0.0-beta1
> >> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-17806
> >> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-17759
> >> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-17637
> >> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-17263
> >> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-17260
> >> >>>>>>>>
> >> >>>>>>>> It's all about read-only transactions.
> >> >>>>>>>>
> >> >>>>>>>> Best regards,
> >> >>>>>>>> Alexander
> >> >>>>>>>>
> >> >>>>>>>> пт, 14 окт. 2022 г. в 19:45, Andrey Gura :
> >> >>>>>>>>
> >> >>>>>>>>> Igniters,
> >> >>>>>>>>>
> >> >>>>>>>>> The 'ignite-3.0.0-beta1' branch was created (the latest commit
> >> is
> >> >>>>>>>>> 8160ef31ecf8d49f227562b6f0ab090c6b4438c1).
> >> >>>>>>>>>
> >> >>>>>>>>> The scope for the release is frozen.
> >> >>>>>>>>>
> >> >>>>>>>>> It means the following:
> >> >>>>>>>>>
> >> >>>>>>>>> - Any issue could be added to the release (fixVersion ==
> >> >>>>> 3.0.0-beta1)
> >> >>>>>>>>> only after discussion with the community and a release manager
> >> in
> >> >>>>>> this
> >> >>>>>>>>> thread.
> >> >>>>>>>>> - Any commit to the release branch must be also applied to the
> >> >>>>> 'main'
> >> >>>>>>>>> branch.
> >> >>>>>>>>>
> >> >>>>>>>>
> >> >>>>>>>
> >> >>>>>>
> >> >>>>>>
> >> >>>>>> --
> >> >>>>>> Живи с улыбкой! :D
> >> >>>>>>
> >> >>>>>
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>> Живи с улыбкой! :D
> >> >>>>
> >> >>
> >> >>
> >>
> >>
>
--
Vladislav Pyatkov
Architect-Consultant "GridGain Rus" Llc.
+7-929-537-79-60
I am sure the shorter, the better.
+1 to option 4.
On Thu, Jan 13, 2022 at 2:06 PM ткаленко кирилл
wrote:
> +1 to option 2
>
--
Vladislav Pyatkov
all will
> have
> > a
> > > configurable default timeout and can complete with timeout error if a
> > > computation is not finished in time, for example if a response has not
> > been
> > > yet received.
> > > I suggest to complete the async op future with TimeoutException in this
> > > case to make it on par with synchronous execution using future.get,
> which
> > > will throw java.util.concurrent.TimeoutException on timeout.
> > > For reference, see java.util.concurrent.CompletableFuture#orTimeout
> > > No special error code should be used for this scenario.
> > >
> > > *Internal exceptions hierarchy.*
> > >
> > > All internal exceptions should extend
> > > org.apache.ignite.internal.lang.IgniteInternalException for checked
> > > exceptions and
> > > org.apache.ignite.internal.lang.IgniteInternalCheckedException for
> > > unchecked exceptions.
> > >
> > > Thoughts ?
> > >
> > > [1] https://docs.oracle.com/cd/B10501_01/server.920/a96525/preface.htm
> > >
> > > --
> > >
> > > Best regards,
> > > Alexei Scherbakov
> > >
> >
> >
> > --
> > Best regards,
> > Alexey
> >
>
>
> --
>
> Best regards,
> Alexei Scherbakov
>
--
Vladislav Pyatkov
t;
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 12 апр. 2021 г. в 11:44, Vladislav Pyatkov :
>
> > Hi, igniters!
> > Please grant me access to Ignite Wiki to help with editing and updating
> > info.
> > It is my JIRA account v.pyatkov
> >
> > --
> > Vladislav Pyatkov
> >
>
--
Vladislav Pyatkov
Hi, igniters!
Please grant me access to Ignite Wiki to help with editing and updating
info.
It is my JIRA account v.pyatkov
--
Vladislav Pyatkov
Vladislav Pyatkov created IGNITE-14476:
--
Summary: Get rid of using storage implementation explicitly in
ConfigurationRoot annotation
Key: IGNITE-14476
URL: https://issues.apache.org/jira/browse/IGNITE-14476
Vladislav Pyatkov created IGNITE-14419:
--
Summary: SPI suite hangs sporadically on private TC
Key: IGNITE-14419
URL: https://issues.apache.org/jira/browse/IGNITE-14419
Project: Ignite
Vladislav Pyatkov created IGNITE-14185:
--
Summary: Synchronous checkpoints on several nodes greatly increase
a latency of distributed transaction
Key: IGNITE-14185
URL: https://issues.apache.org/jira/browse
Vladislav Pyatkov created IGNITE-14140:
--
Summary: Checkpointer thread holds write lock too long
Key: IGNITE-14140
URL: https://issues.apache.org/jira/browse/IGNITE-14140
Project: Ignite
Vladislav Pyatkov created IGNITE-14139:
--
Summary: Incorrect initialize checkpoint-runner-cpu thread pool
Key: IGNITE-14139
URL: https://issues.apache.org/jira/browse/IGNITE-14139
Project: Ignite
Vladislav Pyatkov created IGNITE-14138:
--
Summary: Historical rebalance kills cluster
Key: IGNITE-14138
URL: https://issues.apache.org/jira/browse/IGNITE-14138
Project: Ignite
Issue Type
ull} if not deployed.
> > >>>> */
> > >>>> public DeploymentResource findResource(String rsrcName);
> > >>>> is thread unsafe by default, no guarantee that concurrent call of
> > >>>> localDeployTask and execute will bring expected result.
> > >>>> My proposal is to deprecate (or probably annotate [2], as a minimal
> > >>>> — additionally document it) this methods and to append additional :
> > >>>> public DeploymentResource findResource(String rsrcName, ClassLoader
> > >>>> clsLdr);
> > >>>> Only one problem i can observe here, if someone creates new class
> > loaders
> > >>>> and appropriate class instances in loop (i don`t know the purpose)
> and
> > >>>> doesn`t undeploy them then he will get possibly OOM here.
> > >>>>
> > >>>> Such approach will give a possibility to use compute in concurrent
> > >>>> scenario. If there is no objections here i will mark this methods
> and
> > >>>> publish my PR, of course with additional tests.
> > >>>>
> > >>>> What do you think ?
> > >>>>
> > >>>>
> > >>>> [1]
> > >>>>
> > https://ignite.apache.org/docs/latest/code-deployment/peer-class-loading
> > >>>> [2]
> > >>>>
> > https://jcip.net/annotations/doc/net/jcip/annotations/NotThreadSafe.html
> > >>>>
> > >>>>
> > >>
> > >>
> > >>
> > >>
>
--
Vladislav Pyatkov
Vladislav Pyatkov created IGNITE-14073:
--
Summary: False alarm to lose all transaction nodes
Key: IGNITE-14073
URL: https://issues.apache.org/jira/browse/IGNITE-14073
Project: Ignite
Vladislav Pyatkov created IGNITE-13977:
--
Summary: Code enhancement after review of encryption persistent
storage
Key: IGNITE-13977
URL: https://issues.apache.org/jira/browse/IGNITE-13977
Project
Vladislav Pyatkov created IGNITE-13866:
--
Summary: Validate index does not stop after process of control.sh
was interrupted
Key: IGNITE-13866
URL: https://issues.apache.org/jira/browse/IGNITE-13866
Vladislav Pyatkov created IGNITE-13864:
--
Summary: Assertion error happens on stale latch's acknowledge
Key: IGNITE-13864
URL: https://issues.apache.org/jira/browse/IGNITE-13864
Project: Ignite
Vladislav Pyatkov created IGNITE-13594:
--
Summary: Model classes require manual deserialization if used
inside Job loaded by p2p
Key: IGNITE-13594
URL: https://issues.apache.org/jira/browse/IGNITE-13594
Vladislav Pyatkov created IGNITE-13593:
--
Summary:
IgniteClientCacheStartFailoverTest.testRebalanceStateConcurrentStart (Cache 2)
is flaky
Key: IGNITE-13593
URL: https://issues.apache.org/jira/browse/IGNITE
;>>>>>>>>>>>>> to measurement error and I think such a drop is not a
> >> >>>>>>>>>>>> showstopper. Guys,
> >> >>>>>>>>>>>>>>>>> WDYT?
&g
Vladislav Pyatkov created IGNITE-13501:
--
Summary: AssertionError: Invalid value in testMergeServersFail1_8
Key: IGNITE-13501
URL: https://issues.apache.org/jira/browse/IGNITE-13501
Project
Vladislav Pyatkov created IGNITE-13417:
--
Summary: Cache Interceptors deserialization on client nodes
Key: IGNITE-13417
URL: https://issues.apache.org/jira/browse/IGNITE-13417
Project: Ignite
Vladislav Pyatkov created IGNITE-13402:
--
Summary: [Suite] PDS 3 flaky failed on TC
Key: IGNITE-13402
URL: https://issues.apache.org/jira/browse/IGNITE-13402
Project: Ignite
Issue Type
> >> >
> > >> > 1. Node has failed in the middle of checkpoint when WAL is
> disabled
> > >> > for
> > >> > a particular cache -> data files of the cache are potentially
> > >> corrupted.
> > >> > 2. On next startup node detects this situation, creates
> Maintenance
> > >> > Record on disk and shuts down.
> > >> > 3. On next startup node sees Maintenance Record, enters
> Maintenance
> > >> Mode
> > >> > and waits for user to do specific actions: clean potentially
> > >> > corrupted
> > >> PDS.
> > >> > 4. When user has done necessary actions he/she removes Maintenance
> > >> > Record using Maintenance Mode API exposed via control.{sh|bat}
> > script
> > >> or
> > >> > JMX.
> > >> > 5. On next startup node goes to normal operations as maintenance
> > >> > reason
> > >> > is fixed.
> > >> >
> > >> >
> > >> > I prepared a PR [3] for ticket [1] with draft implementation. It is
> > not
> > >> > ready to be merged to master branch but is already fully functional
> > and
> > >> can
> > >> > be reviewed.
> > >> >
> > >> > Hope you'll share your feedback on the feature and/or any thoughts
> on
> > >> > implementation.
> > >> >
> > >> > Thank you!
> > >> >
> > >> > [1] https://issues.apache.org/jira/browse/IGNITE-13366
> > >> > [2]
> > >> >
> > >>
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-47:+Native+persistence+defragmentation
> > >> > [3] https://github.com/apache/ignite/pull/8189
> > >>
> > >>
> > >
> >
> >
> > --
> >
> > Best regards,
> > Ivan Pavlukhin
> >
>
--
Vladislav Pyatkov
Vladislav Pyatkov created IGNITE-13379:
--
Summary: Exception occur on SQL caches when client reconnect
Key: IGNITE-13379
URL: https://issues.apache.org/jira/browse/IGNITE-13379
Project: Ignite
gt;get sensitive information about server configuration, such as it's
> > version,
> > >version of the underlying database, frameworks etc.. This information
> may
> > >help attacker to apply some version-specific attacks. This is precise
> > >reason why default
Vladislav Pyatkov created IGNITE-13377:
--
Summary:
WalModeChangeAdvancedSelfTest.testServerRestartNonCoordinator
Key: IGNITE-13377
URL: https://issues.apache.org/jira/browse/IGNITE-13377
Project
AR, VARCHAR,
> VARCHAR,
> >VARCHAR, VARCHAR) default index size will be only 64. Same for the columns
> >with defined length: by default VARCHAR(100) column will create index only
> >with size equal to 64.
> >
> >Please tell if you have any concerns. Update can be found at
> >https://github.com/apache/ignite/pull/8161
> >
> >Best regards,
> >Evgeniy
> >
>
>
>
>
--
Vladislav Pyatkov
Vladislav Pyatkov created IGNITE-13265:
--
Summary: Historical iterator for atomic group should transfer few
more rows than required
Key: IGNITE-13265
URL: https://issues.apache.org/jira/browse/IGNITE-13265
accepts a side of heuristics above.
On Thu, Jul 16, 2020 at 12:09 AM Vladislav Pyatkov
wrote:
> Ivan,
>
> I agree with a combined approach: threshold for small partitions and count
> of update for partition that outgrew it.
> This helps to avoid partitions that update not frequent
don't track skipped updates for atomic caches. As a result, detection of
> the absence of updates between two checkpoint markers with the same
> partition counter can be false positive.
>
> --
> Best Regards,
> Ivan Rakov
>
> On Tue, Jul 14, 2020 at 3:03 PM Vladislav Pyatkov
&g
tps://issues.apache.org/jira/browse/IGNITE-13253
[2]: https://issues.apache.org/jira/browse/IGNITE-13254
--
Vladislav Pyatkov
Vladislav Pyatkov created IGNITE-13254:
--
Summary: Historical rebalance iterator may skip checkpoint if it
not contains updates
Key: IGNITE-13254
URL: https://issues.apache.org/jira/browse/IGNITE-13254
Vladislav Pyatkov created IGNITE-13253:
--
Summary: Advanced heuristics for historical rebalance
Key: IGNITE-13253
URL: https://issues.apache.org/jira/browse/IGNITE-13253
Project: Ignite
Vladislav Pyatkov created IGNITE-13245:
--
Summary: Rebalance future might hangs in no final state though all
partitions are owned
Key: IGNITE-13245
URL: https://issues.apache.org/jira/browse/IGNITE-13245
Vladislav Pyatkov created IGNITE-13191:
--
Summary: Public-facing API for "waiting for backups on shutdown"
Key: IGNITE-13191
URL: https://issues.apache.org/jira/browse/IGNITE-13191
Proje
Vladislav Pyatkov created IGNITE-13168:
--
Summary: Retrigger historical rebalance if it was cancelled in
case WAL history is still available
Key: IGNITE-13168
URL: https://issues.apache.org/jira/browse/IGNITE
down did not configure all be worked as before according to
IMMEDIATE behavior.
All other close method will be marked as deprecated.
I will be waiting for your opinions.
--
Vladislav Pyatkov
Vladislav Pyatkov created IGNITE-13072:
--
Summary: Synchronization problems when different classloaders are
used for deployment of same class
Key: IGNITE-13072
URL: https://issues.apache.org/jira/browse
Vladislav Pyatkov created IGNITE-12935:
--
Summary: Disadvantages in log of historical rebalance
Key: IGNITE-12935
URL: https://issues.apache.org/jira/browse/IGNITE-12935
Project: Ignite
objections would be here, i plan to inform about moving states as
> not OK exit code too.
>
>
--
Vladislav Pyatkov
Architect-Consultant "GridGain Rus" Llc.
+7-929-537-79-60
Vladislav Pyatkov created IGNITE-12818:
--
Summary: SoLinger is not set for reader-sockets in discovery
Key: IGNITE-12818
URL: https://issues.apache.org/jira/browse/IGNITE-12818
Project: Ignite
Vladislav Pyatkov created IGNITE-12780:
--
Summary: Deadlock between db-checkpoint-thread and
checkpoint-runner
Key: IGNITE-12780
URL: https://issues.apache.org/jira/browse/IGNITE-12780
Project
Vladislav Pyatkov created IGNITE-12689:
--
Summary: Partitions should become owned after a checkpoint,
regardless of a topology change. Nevertheless a rebalance is not required.
Key: IGNITE-12689
URL: https
Vladislav Pyatkov created IGNITE-12671:
--
Summary: Update of partition's states can stuck when rebalance
completed during exchange
Key: IGNITE-12671
URL: https://issues.apache.org/jira/browse/IGNITE-12671
Vladislav Pyatkov created IGNITE-12522:
--
Summary: Extend test coverage [IGNITE-12104] Check deployment from
cache before to load it from local or version storage
Key: IGNITE-12522
URL: https
Vladislav Pyatkov created IGNITE-12290:
--
Summary: Re-balance fully restart for case when WAL disabled
Key: IGNITE-12290
URL: https://issues.apache.org/jira/browse/IGNITE-12290
Project: Ignite
Vladislav Pyatkov created IGNITE-12104:
--
Summary: Check deployment from cache before to load it from local
or version storage
Key: IGNITE-12104
URL: https://issues.apache.org/jira/browse/IGNITE-12104
Vladislav Pyatkov created IGNITE-11844:
--
Summary: Should to filtered indexes by cache name instead of
validate all caches in group
Key: IGNITE-11844
URL: https://issues.apache.org/jira/browse/IGNITE-11844
Vladislav Pyatkov created IGNITE-11834:
--
Summary: Confusing message on rebalance
Key: IGNITE-11834
URL: https://issues.apache.org/jira/browse/IGNITE-11834
Project: Ignite
Issue Type
Vladislav Pyatkov created IGNITE-11763:
--
Summary: GridP2PComputeWithNestedEntryProcessorTest failed on TC
Key: IGNITE-11763
URL: https://issues.apache.org/jira/browse/IGNITE-11763
Project: Ignite
Vladislav Pyatkov created IGNITE-11734:
--
Summary: IgniteCache.replace(k, v, nv) requires classes when
element is null or old value - null
Key: IGNITE-11734
URL: https://issues.apache.org/jira/browse/IGNITE
Vladislav Pyatkov created IGNITE-11698:
--
Summary: Issue with P2P class loader
Key: IGNITE-11698
URL: https://issues.apache.org/jira/browse/IGNITE-11698
Project: Ignite
Issue Type: Bug
page formats that we need to support.
> 2) Once we release version 1.0, we would like TBLignite to be added to the
> Ignite "3rd party binary" page. Who decides what gets on this page?
> 3) And are there any acceptance criteria or tests that need to be passed?
>
> We would like to hear from you.
> Pascal Schuchhard
> TBLcore
>
>
--
Vladislav Pyatkov
Vladislav Pyatkov created IGNITE-11643:
--
Summary: Optimize GC pressure on
GridDhtPartitionTopologyImpl#updateRebalanceVersion
Key: IGNITE-11643
URL: https://issues.apache.org/jira/browse/IGNITE-11643
Vladislav Pyatkov created IGNITE-11474:
--
Summary: Add possibility to run idle_verify in not idle cluster
Key: IGNITE-11474
URL: https://issues.apache.org/jira/browse/IGNITE-11474
Project: Ignite
Vladislav Pyatkov created IGNITE-11425:
--
Summary: Log information about inaccessible nodes through
Communication
Key: IGNITE-11425
URL: https://issues.apache.org/jira/browse/IGNITE-11425
Project
Vladislav Pyatkov created IGNITE-11291:
--
Summary: Assertion error in time of rebalance completion lead to
to critical failure node
Key: IGNITE-11291
URL: https://issues.apache.org/jira/browse/IGNITE-11291
we need such tool? (Or perhaps we already have something and
> there is no need to reinvent the wheel.)
> 2. What is the best way for us to implement the tool?
>
> [1] https://github.com/apache/ignite/pull/6076
> [2] https://wiki.jenkins.io/display/JENKINS/Parameterized+Build
>
> --
> Best regards,
> Ivan Pavlukhin
>
--
Vladislav Pyatkov
Vladislav Pyatkov created IGNITE-11270:
--
Summary: Batch join to topology
Key: IGNITE-11270
URL: https://issues.apache.org/jira/browse/IGNITE-11270
Project: Ignite
Issue Type
Vladislav Pyatkov created IGNITE-11269:
--
Summary: Optimize node join to topology
Key: IGNITE-11269
URL: https://issues.apache.org/jira/browse/IGNITE-11269
Project: Ignite
Issue Type
Vladislav Pyatkov created IGNITE-11262:
--
Summary: Compression on Discovery data bag
Key: IGNITE-11262
URL: https://issues.apache.org/jira/browse/IGNITE-11262
Project: Ignite
Issue Type
Vladislav Pyatkov created IGNITE-11120:
--
Summary: Remove static fields from GridDhtLockFuture
Key: IGNITE-11120
URL: https://issues.apache.org/jira/browse/IGNITE-11120
Project: Ignite
Vladislav Pyatkov created IGNITE-11023:
--
Summary: Processing data bag on GridMarshallerMappingProcessor
consume many time
Key: IGNITE-11023
URL: https://issues.apache.org/jira/browse/IGNITE-11023
Vladislav Pyatkov created IGNITE-10933:
--
Summary: Node may hang on join to topology and not move forward
Key: IGNITE-10933
URL: https://issues.apache.org/jira/browse/IGNITE-10933
Project: Ignite
Vladislav Pyatkov created IGNITE-10108:
--
Summary: Non-static class is passed between cluster nodes
Key: IGNITE-10108
URL: https://issues.apache.org/jira/browse/IGNITE-10108
Project: Ignite
Vladislav Pyatkov created IGNITE-10092:
--
Summary: Race in partition state when checkpoint started at the
middle of starts caches
Key: IGNITE-10092
URL: https://issues.apache.org/jira/browse/IGNITE-10092
Vladislav Pyatkov created IGNITE-10028:
--
Summary: Incorrect handling of page on replacement
Key: IGNITE-10028
URL: https://issues.apache.org/jira/browse/IGNITE-10028
Project: Ignite
Vladislav Pyatkov created IGNITE-9934:
-
Summary: Improve logging on partition map exchange
Key: IGNITE-9934
URL: https://issues.apache.org/jira/browse/IGNITE-9934
Project: Ignite
Issue
D.Govoruchin,
I tried to correct all your comments and TC in correct state.
Please, review my changes.
--
Vladislav Pyatkov
Vladislav Pyatkov created IGNITE-9885:
-
Summary: Issue in termination of GridWorkerFuture
Key: IGNITE-9885
URL: https://issues.apache.org/jira/browse/IGNITE-9885
Project: Ignite
Issue
Vladislav Pyatkov created IGNITE-9738:
-
Summary: Client node can suddenly fail on start
Key: IGNITE-9738
URL: https://issues.apache.org/jira/browse/IGNITE-9738
Project: Ignite
Issue Type
Vladislav Pyatkov created IGNITE-9707:
-
Summary: TouchedExpiryPolicy with persistent on atomic cache,
update TTL without lock
Key: IGNITE-9707
URL: https://issues.apache.org/jira/browse/IGNITE-9707
Vladislav Pyatkov created IGNITE-9448:
-
Summary: Change ZooKeeper version to 3.4.13
Key: IGNITE-9448
URL: https://issues.apache.org/jira/browse/IGNITE-9448
Project: Ignite
Issue Type
Vladislav Pyatkov created IGNITE-8965:
-
Summary: Add logs in SegmentReservationStorage on exchange process
Key: IGNITE-8965
URL: https://issues.apache.org/jira/browse/IGNITE-8965
Project: Ignite
Vladislav Pyatkov created IGNITE-8913:
-
Summary: Uninformative SQL query cancellation message
Key: IGNITE-8913
URL: https://issues.apache.org/jira/browse/IGNITE-8913
Project: Ignite
Vladislav Pyatkov created IGNITE-8866:
-
Summary: Need attempt to upload class until node leave or fail
topology by discovery SPI
Key: IGNITE-8866
URL: https://issues.apache.org/jira/browse/IGNITE-8866
Vladislav Pyatkov created IGNITE-8829:
-
Summary: Some configuration properties of TcpCommunicationSpi does
not annotated appropriately
Key: IGNITE-8829
URL: https://issues.apache.org/jira/browse/IGNITE-8829
Vladislav Pyatkov created IGNITE-8754:
-
Summary: Node outside of baseline does not start when service
configured
Key: IGNITE-8754
URL: https://issues.apache.org/jira/browse/IGNITE-8754
Project
Vladislav Pyatkov created IGNITE-8710:
-
Summary: Applying WAL works long time or fail at all, when *.wal
files been removed
Key: IGNITE-8710
URL: https://issues.apache.org/jira/browse/IGNITE-8710
Vladislav Pyatkov created IGNITE-8606:
-
Summary: Node hangs on next exchange, when no access to
marshaller's folder
Key: IGNITE-8606
URL: https://issues.apache.org/jira/browse/IGNITE-8606
Vladislav Pyatkov created IGNITE-8458:
-
Summary: AffinityAssigment absorbs a lot of java heap
Key: IGNITE-8458
URL: https://issues.apache.org/jira/browse/IGNITE-8458
Project: Ignite
Vladislav Pyatkov created IGNITE-8440:
-
Summary: Transaction may hangs on node in PREPARED state
Key: IGNITE-8440
URL: https://issues.apache.org/jira/browse/IGNITE-8440
Project: Ignite
Vladislav Pyatkov created IGNITE-8348:
-
Summary: Debug information about discovery messages in
TcpDiscoverySpiMBean
Key: IGNITE-8348
URL: https://issues.apache.org/jira/browse/IGNITE-8348
Project
Vladislav Pyatkov created IGNITE-8136:
-
Summary: Discovery service wrong works if node stopping by
segmentation and hangs
Key: IGNITE-8136
URL: https://issues.apache.org/jira/browse/IGNITE-8136
Vladislav Pyatkov created IGNITE-8087:
-
Summary: Assertion error in time to rebalancing
Key: IGNITE-8087
URL: https://issues.apache.org/jira/browse/IGNITE-8087
Project: Ignite
Issue Type
Vladislav Pyatkov created IGNITE-8030:
-
Summary: Cluster hangs on deactivation process in time stopping
indexed cache
Key: IGNITE-8030
URL: https://issues.apache.org/jira/browse/IGNITE-8030
Vladislav Pyatkov created IGNITE-8021:
-
Summary: Destroyed caches can be return to life by restart grid
Key: IGNITE-8021
URL: https://issues.apache.org/jira/browse/IGNITE-8021
Project: Ignite
Vladislav Pyatkov created IGNITE-8006:
-
Summary: Starting multiple caches inhibits exchange process on
joining node
Key: IGNITE-8006
URL: https://issues.apache.org/jira/browse/IGNITE-8006
Project
Vladislav Pyatkov created IGNITE-7930:
-
Summary: Partition map hang in incorrect state when backup filter
is assigned
Key: IGNITE-7930
URL: https://issues.apache.org/jira/browse/IGNITE-7930
Vladislav Pyatkov created IGNITE-7896:
-
Summary: Files of evicted partitions do not removed from disk
storage
Key: IGNITE-7896
URL: https://issues.apache.org/jira/browse/IGNITE-7896
Project
Vladislav Pyatkov created IGNITE-7703:
-
Summary: Add a method gets caches in batch
Key: IGNITE-7703
URL: https://issues.apache.org/jira/browse/IGNITE-7703
Project: Ignite
Issue Type: Bug
Vladislav Pyatkov created IGNITE-6991:
-
Summary: SharedDeploymentTest.testDeploymentFromSecondAndThird
Test fails in 100 percentage cases
Key: IGNITE-6991
URL: https://issues.apache.org/jira/browse/IGNITE
Vladislav Pyatkov created IGNITE-6922:
-
Summary: Class can not undeploy from grid in some specific cases
Key: IGNITE-6922
URL: https://issues.apache.org/jira/browse/IGNITE-6922
Project: Ignite
Vladislav Pyatkov created IGNITE-6799:
-
Summary: Check of starvation in striped thread pool
Key: IGNITE-6799
URL: https://issues.apache.org/jira/browse/IGNITE-6799
Project: Ignite
Issue
Hi,
I have added PR for this issue:
https://issues.apache.org/jira/browse/IGNITE-6737
and this fix passed in TC.
This is serious issue witch can loop nodes from cluster.
--
Vladislav Pyatkov
Vladislav Pyatkov created IGNITE-6737:
-
Summary: GridDeploymentPerVersionStore retries loading class
infinitely
Key: IGNITE-6737
URL: https://issues.apache.org/jira/browse/IGNITE-6737
Project
Vladislav Pyatkov created IGNITE-6589:
-
Summary: Encountered incompatible class loaders for cache
Key: IGNITE-6589
URL: https://issues.apache.org/jira/browse/IGNITE-6589
Project: Ignite
Vladislav Pyatkov created IGNITE-6579:
-
Summary: WAL history does not used when node returns to cluster
again
Key: IGNITE-6579
URL: https://issues.apache.org/jira/browse/IGNITE-6579
Project
network message from primary node to
> local backup, which doesn't make much sense to me and looks like
> unnecessary performance overhead.
>
> Is it possible to update local backup synchronously in this scenario?
>
> -Val
>
--
Vladislav Pyatkov
1 - 100 of 146 matches
Mail list logo
