LGTM. Merged to master.
Thank you for your contribution!
On Fri, Nov 26, 2021 at 12:20 PM Maxim Muzafarov wrote:
> Folks,
>
> This is a friendly reminder :-)
> PR [1] is ready for review. Will anyone take a look?
>
> [1] https://github.com/apache/ignite/pull/9577/files
>
> On Sat, 20 Nov 2021
Alex, congrats!
ср, 18 нояб. 2020 г. в 13:39, Вячеслав Коптилин :
> Hooray!
>
> Congratulations, Alex! Well deserved achievement!
>
> Thanks,
> S.
>
> ср, 18 нояб. 2020 г. в 03:26, Denis Magda :
>
> > Igniters,
> >
> > The Project Management Committee (PMC) for Apache Ignite
> > has invited Alex
Mikhail, I merged your changes.
Thanks for your contribution!
On Tue, May 12, 2020 at 8:01 PM Vyacheslav Daradur
wrote:
> Hi Mikhail, proposed changes make sense to me.
> I left some comments to the pr.
> Thank you!
>
> On Wed, May 6, 2020 at 2:28 PM Mikhail Petrov
>
/7771
>
> On 30.12.2019 13:03, Alexey Goncharuk wrote:
> > Agree, sounds like a plan, thanks for taking over!
> >
> > пн, 30 дек. 2019 г. в 13:00, Vyacheslav Daradur :
> >
> >> Alexey,
> >>
> >> I would not make it default in the current implem
Great job! My congratulations!
чт, 7 мая 2020 г. в 16:09, Alex Plehanov :
> Maxim, congratulations!
>
>
> чт, 7 мая 2020 г. в 15:12, Denis Garus :
>
> > Maxim, Congrats!
> > Great job!
> >
> > чт, 7 мая 2020 г. в 15:02, Nikita Amelchev :
> >
> > > Maxim, congrats!
> > >
> > > чт, 7 мая 2020 г. в
Now I see.
Your parent class (called Test in your example) *should implement
'Serializable' interface*, this will help for your case.
We changed default marshaller for services in 2.8, because they have to
be 'Serializable' according to API. 'JdkMarshaller' is default marshaller
for services
Sorry, wrong link in previous email.
Here is an example:
https://github.com/apache/ignite/blob/master/modules/spring/src/test/java/org/apache/ignite/spring/injection/spring-bean.xml
On Tue, Apr 21, 2020 at 8:02 PM Vyacheslav Daradur
wrote:
> Hi, I looked through your example and ca
Hi, I looked through your example and can't reproduce it.
Properties injection works fine.
I suppose that you have run Ignite out of Spring context.
Please check your Spring context configuration file once again.
Here is an example:
. 2020 г. в 12:56, Vladimir Steshin :
> >
> > > Denis, Vyacheslav, hi.
> > >
> > > What if we just provide an option to disable service metrics at all? It
> > > would keep direct references for local services. Also, we can make
> > service
> > >
ce invocations work through a
> proxy in Ignite 3.
> For now though the best thing we can do is to calculate remote invocations
> only, since all of them go through a proxy.
> Another option is to provide a simple way for a user to account the
> service invocations themsel
февр. 2020 г. в 16:17, Vyacheslav Daradur :
>
>> {IgniteServices#service(String name)} returns direct reference in the
>> current implementation.
>>
>> So, class casting should work for your example:
>> ((MyServiceImpl)ignite.services().service(“myService”)
e? What if I need to wrap it? This would be local service
> working via proxy or null.
>
> вт, 25 февр. 2020 г. в 16:03, Vyacheslav Daradur :
>
>> Hi, Vladimir
>>
>> The answer is in API docs: "Gets *locally deployed service* with
>> specified name."
Hi, Vladimir
The answer is in API docs: "Gets *locally deployed service* with specified
name." [1]
That means {IgniteServices#service(String name)} returns only locally
deployed instance or null.
{IgniteServices#serviceProxy(…)} returns proxy to call instances across the
cluster. Might be used
Hi, Alexei!
CacheConfiguration#getRebalanceDelay was extremely useful for the
caches backed by @CacheLocalStore to prevent rebalancing during full
cluster startup/shutdown.
But @CacheLocalStore annotation is deprecated also.
I think "rebalancing delay" stuff might be useful for replicated
cached
+1 Allow, because once the community has made a decision to introduce
new APIs instead of an old one - stabilization is just a matter of
time.
On Mon, Feb 10, 2020 at 11:02 AM Alexey Goncharuk wrote:
>
> Dear Apache Ignite community,
>
> We would like to conduct a formal vote on the subject of
if multiple nodes deploy it concurrently.
> Most likely users will end up always calling the second option of the proxy
> (with the timeout), so, perhaps, make it default?
>
> вс, 29 дек. 2019 г. в 21:05, Vyacheslav Daradur :
>
> > Alexey,
> >
> > I've prepared pr [1]
Alexey,
I've prepared pr [1] to show our proxy invocation guarantees and to
avoid misunderstanding.
Please, let me know if you think that we should improve our guaranties
in some cases.
[1] https://github.com/apache/ignite/pull/7213
On Tue, Dec 24, 2019 at 7:27 PM Vyacheslav Daradur wrote
cal deployment looks broken: if a compute job
> is sent to a remote node after the service deployment, the job execution
> may fail due to this error.
>
> Should we schedule this ticket for the further work on Services IEP?
>
> вт, 24 дек. 2019 г. в 18:49, Vyacheslav Daradur :
>
hould wait? - deployment of "heavy"
service may take a while
On Tue, Dec 24, 2019 at 6:19 PM Alexey Goncharuk
wrote:
>
> What should be the user fallback in this case? Retry infinitely? Is there a
> way to wait for the proper deployment?
>
> вт, 24 дек. 2019 г. в 12:41, V
proxy is created on node B, and "service not found" exception gets thrown
> to a user anyway. Perhaps, the retry happens too fast?
>
> Created a ticket [1].
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12490
>
> пн, 23 дек. 2019 г. в 22:08, Vyacheslav Daradur :
>
Hi, Alexey
Please attach a reproducer to the ticket.
As far as I remember we have the following behaviour for the proxies:
Let's assume you have deployed service from node A, then:
* if you invoke service locally from node A - it is guaranteed to
service to be deployed and ready to work
* if
Igniters, I'd suggest 2 candidates who perfectly fit this role, in my opinion:
Nickolay Izhikov - one of the most active community member with the
significant contributions, Ignite's evangelist and tech-speaker.
Alexey Goncharuk - Ignite's veteran, one of the Ignite's code-base
expert with the
Hi, Alexey,
I agree that Map-Reduce on demand looks more promising solution.
We can use Compute tasks for implementation.
'Map' phase can be tunned to process data by some trigger (dataset
update?) on ContiniousQuery manner and call 'Reduce' (with some
cache?) on demand.
On Tue, Sep 10, 2019 at
Good job Maxim, congratulations!
On Thu, Aug 29, 2019 at 9:59 AM Anton Vinogradov wrote:
>
> Welcome aboard :)
>
> On Thu, Aug 29, 2019 at 3:35 AM Roman Shtykh
> wrote:
>
> > Maxim, congratulations!
> >
> > -- Roman
> >
> >
> > On Thursday, August 29, 2019, 12:11:29 a.m. GMT+9, Dmitriy
I agree that useless comments look weird in the codebase.
But, identical distance/padding/margin between fields in a class - is
really cool, and helps read the class very fast.
On Wed, Aug 7, 2019 at 12:26 PM Nikolay Izhikov wrote:
>
> Hello, Denis.
>
> Thanks for starting this discussion.
>
>
Ilya, congratulations!
On Wed, Aug 7, 2019 at 8:41 AM Павлухин Иван wrote:
>
> Ilya, my congratulations!
>
> вт, 6 авг. 2019 г. в 23:12, Dmitriy Pavlov :
> >
> > Ilya, congratulations!
> >
> > вт, 6 авг. 2019 г. в 22:58, Denis Magda :
> >
> > > The Project Management Committee (PMC) for Apache
Hi Denis.
I think it is fine to extract security tests in a separate build plan on TC.
BTW, if you are going to write a lot of Sandbox's tests pay attention
to 'extdata' module and an approach of P2P tests
(IgniteP2PSelfTestSuite) - this may help you to avoid Maven's
classloading issues.
On
I think all agreed items should be marked @Deprecated in the code
base, so we will be able to remove them transparently for the
end-users.
On Mon, Jul 22, 2019 at 9:32 AM Павлухин Иван wrote:
>
> Alex,
>
> I already added a couple of items to wishlist [1].
>
> Yes, I agree that the process
Ivan,
* About Service Grid:
Yes, we discussed that old service grid implementation
(GridServiceProcessor) should be removed in 3.0, now it is marked as
obsolete.
This was in the list, maybe it was lost during formatting.
Also, a class `ServiceConfiguration` should be moved to common package
of
+1 for moving to a separate branch from the master
On Thu, Jun 20, 2019 at 11:54 AM Nikita Amelchev wrote:
>
> +1
>
> чт, 20 июн. 2019 г. в 11:28, Anton Vinogradov :
> >
> > +1 (binding)
> >
> > On Thu, Jun 20, 2019 at 10:08 AM Dmitriy Pavlov wrote:
> >
> > > +1
> > >
> > > чт, 20 июн. 2019 г.
; > And thank you for advice on how to check examples.
> >
> > Sincerely
> > Dmitriy Pavlov
> >
> > чт, 6 июн. 2019 г. в 22:37, Vyacheslav Daradur :
> >
> > > +1 from me. Built from sources and run several examples.
> > >
> > > Ivan,
+1 from me. Built from sources and run several examples.
Ivan, try to clean local repo (~/m2) and rebuild the project once
again according to DEVNOTES.txt
On Thu, Jun 6, 2019 at 7:37 PM Павлухин Иван wrote:
>
> I spent a while running examples for RC from bin package. I did the following:
> 1.
of
> > build Apache Ignite procedure.
> >
> > Also, I'd suggest going deeper. We can try to merge `Licenses Header`
> > into the `Code style checker` [1]. This will simplify the code
> > checking process.
> >
> > [1] http://checkstyle.sourceforge.net/config_
Hi, Nikolay,
I looked through PR and IEP, and I have some comments:
It would be better to implement it as a separate module, I can't say
if it is possible for the main part of monitoring or not, but I
believe that HttpExposer with Jetty's dependencies should be detached
from the core module.
I
are not they? Do you suggest to combine
> mentioned 4 jobs into one? How long will it run in a such case?
>
> чт, 25 апр. 2019 г. в 10:50, Vyacheslav Daradur :
> >
> > Hi Igniters,
> >
> > At the moment we have several separated test suites:
> > * ~Build Apache Igni
Hi, Sergey,
Makes sense to me in case of performance issues, but may lead to losing data.
>> *by the new option *syncPartitions=N* (not best name just for referring)
Seems similar to "Write Concern"[1] in MongoDB. It is used in the same
way as you described.
On the other hand, if you have such
Hi Igniters,
At the moment we have several separated test suites:
* ~Build Apache Ignite~ _ ~10..20mins
* [Javadocs] _ ~10mins
* [Licenses Headers] _ ~1min
* [Check Code Style] _ ~7min
The most time of each build (except Licenses Headers) is taken by
dependency resolving.
Their main goal is a
>
> > Also, please pass TC build for review next time and do not add to Run All
> > without it.
> >
> > Thanks!
> >
> >
> >> On 23 Apr 2019, at 11:53, Vyacheslav Daradur wrote:
> >>
> >> This is quite strange error, in case of &qu
ldLog=tree=debug=all=3677858&_focus=288
>
>
> On 23 Apr 2019, at 00:25, Vyacheslav Daradur wrote:
>
> Maxim, I merged your changes to master.
>
> Also, I've created a new build plan "Check Code Style" on TC [1] and
> included in RunAll build.
> The report of
Also, I excluded "IntelliJ IDEA Inspections" from RunAll and marked it
as "~[Excluded]".
On Tue, Apr 23, 2019 at 12:25 AM Vyacheslav Daradur wrote:
>
> Maxim, I merged your changes to master.
>
> Also, I've created a new build plan "Check Code Style"
quirements in a separate thread to avoid confusion of community.
cc Petr, Pavel (JFYI)
[1]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_CheckCodeStyle=buildTypeBranches
On Sun, Apr 21, 2019 at 10:18 PM Vyacheslav Daradur wrote:
>
> Maxim,
>
> I left some comments
E level inspection configuration (the Project_Default.xml config);
> - add a new checkstyle plugin configuration file (checkstyle.xml
> config) which will be used simultaneously for checking code style on
> build procedure and for the IDE-checkstyle plugin;
>
> On Wed, 17 Apr 2019 at 21
Hi, Nikolay,
>From my point of view, this is one of the most useful IEP for Ignite
end-users. I often face with a case when Ignite is a black-box for
administrators and devops engineers.
I'd like to have a feature to monitor PME's queue, to view its size
and events type. The same is actual for
Maxim,
I looked through the PR and it looks good to me in general.
The only question how it's planned to maintain check styles in 2
different configurations, for IDEA and check style plugin?
On Mon, Mar 25, 2019 at 12:30 PM Maxim Muzafarov wrote:
>
> Igniters,
>
> The issue [1] with enabled
>
> > > Dear Ignite Developers,
> > >
> > > The Project Management Committee (PMC) for Apache Ignite has invited
> > > Vyacheslav Daradur to become a committer and we are pleased to announce
> > > that he has accepted. Apache Ignite PMC appreciat
In general I agree with Andrey, the handler is very usefull itself. It
allows us to become know that ‘GridDhtInvalidPartitionException’ is not
processed properly in PME process by worker.
Nikolay, look at the code, if Failure Handler hadles an exception - this
means that while-true loop in
Vyacheslav Daradur created IGNITE-11539:
---
Summary: Document services hot redeployment via DeploymentSpi
Key: IGNITE-11539
URL: https://issues.apache.org/jira/browse/IGNITE-11539
Project: Ignite
Denis,
>> After this release, let's introduce a practice of maintenance
>> releases
What a reason of waiting for 2.8 to introduce maintenance release?
Let's prepare 2.7.1 with Java 11 fixes?
Look like this is the safest and fastest way to deliver Java 11
related improvements to our end-users.
Hi, Andrey!
>> 6. ServiceGrid.
>> We can use Metastore and drop old-services later.
As you mentioned new Service Grid does not use system cache.
Legacy implementation (GridServiceProcessor), uses system cache
WITHOUT persistence since 2.3 release and does not restore services
state at node
Hi, Alexey!
>> If we can use multi JVM test with
>> different classpaths I will use them - such approach is more convenient
>> from TC point of view.
There is not such ability at the moment, you are only able to specify
additional JVM arguments in
'GridAbstractTest#additionalRemoteJvmArgs'.
; Such tasks aggregation makes sense for me. If to range by priority I would
> focus on hot redeployment, metrics and failover.
>
>
> -
> Denis
>
>
> On Thu, Feb 7, 2019 at 12:48 PM Vyacheslav Daradur
> wrote:
>
> > Igniters,
> >
> > While working o
mistakes,
> > > some
> > > > of
> > > > > > the
> > > > > > > > test suites can be missed and nobody will know about it before
> > > real
> > > > > > > > compatibility problem appears.
>
Vyacheslav Daradur created IGNITE-11384:
---
Summary: Introduce an opportunity of services hot redeployment via
DeploymentSpi
Key: IGNITE-11384
URL: https://issues.apache.org/jira/browse/IGNITE-11384
Hi, Pavel!
First of all, I'd like to clarify that the Compatibility Testing
Framework was designed to work with a cluster of multi-version nodes.
The main idea is to run a test to verify backward compatibility or do
some kind of rolling upgrades.
It's not about persistence compatibility, but
I'd recommend move the IgniteReproducingSuite to separate module to be
able use it for all modules.
For example, at the moment, we are not able use the suite to run tests
from 'indexing' module because of lack dependency.
On Thu, Feb 14, 2019 at 10:38 AM Павлухин Иван wrote:
>
> Ed,
>
> Thank
with some new Ignite API.
> >> The only requirement for classes - they should be available
> >> locally(on client node or thin client host).
> >>
> >> 3. User deploy the service with some Ignite API.
> >>
> >> 4. After depoyment
Igniters,
While working on the redesign of the Service Grid component I've
looked at the component as end-user and I've faced with usability
issues.
I'd suggest updating IEP-17 [1] or create a new one to specify streams
of improvements:
--- Features
- IGNITE-8367 Implement hot redeployment of
Denis, thank you for driving of Service Grid's development!
Sounds like a good plan. Does it mean that a user will have to
register a classloader for service's class explicitly in case of using
the feature?
On Mon, Feb 4, 2019 at 4:38 PM Denis Mekhanikov wrote:
>
> Igniters,
>
> I'd like to
oing to start working on the services hot redeployment next?
>
>
> -
> Denis
>
>
> On Wed, Jan 16, 2019 at 1:36 AM Vyacheslav Daradur
> wrote:
>
> > The wiki's article [1] has been updated according to the merged solution
> > [2].
> >
> > [1]
> >
>
Hi, Prehistoricpenguin!
It would be great if you will be able to finish a solution [1]. But
I'm not sure that it's a good ticket to start contributing because of
interplatform complexity. Anyway, feel free to contact me in case of
working on the task.
[1]
The wiki's article [1] has been updated according to the merged solution [2].
[1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95654584
[2] https://issues.apache.org/jira/browse/IGNITE-9607
On Fri, Dec 28, 2018 at 1:10 PM Vyacheslav Daradur wrote:
>
> Igniters,
>
The fix was merged to master. Related tests were unmuted.
On Thu, Jan 10, 2019 at 7:03 PM Vyacheslav Daradur wrote:
>
> Looks like the test "ServicesTest.TestGetServiceProxy(False)" became
> flaky after IGNITE-9607.
>
> I muted the test on TC and filled Jira issue as
Vyacheslav Daradur created IGNITE-10910:
---
Summary: GridTaskProcessor#onKernalStop may lead to a deadlock and
execution timeout in "SPI" TC build-plan
Key: IGNITE-10910
URL: https://issues.apach
Vyacheslav Daradur created IGNITE-10899:
---
Summary: Service Grid: disconnecting during node stop may lead to
deadlock
Key: IGNITE-10899
URL: https://issues.apache.org/jira/browse/IGNITE-10899
Looks like the test "ServicesTest.TestGetServiceProxy(False)" became
flaky after IGNITE-9607.
I muted the test on TC and filled Jira issue assigned to myself:
https://issues.apache.org/jira/browse/IGNITE-10888
On Mon, Jan 7, 2019 at 2:37 AM wrote:
>
> Hi Igniters,
>
> I've detected some new
Vyacheslav Daradur created IGNITE-10888:
---
Summary: .NET: ServicesTest.TestGetServiceProxy(False) became
flaky with high fail rate
Key: IGNITE-10888
URL: https://issues.apache.org/jira/browse/IGNITE-10888
change suggestions for
> users.
>
> чт, 10 янв. 2019 г. в 14:08, Vyacheslav Daradur :
>
> > Igniters,
> >
> > As you know, Ignite logs configuration tuning suggestions at node
> > startup to improve performance.
> >
> > At the moment, it recommends us
Igniters,
As you know, Ignite logs configuration tuning suggestions at node
startup to improve performance.
At the moment, it recommends using Java 8 even if later releases are used.
Public updates will not be available for business users since January
of 2019 if I'm not mistaken.
It may be
d index entries, maintaining
> > > consistency for concurrent reads and updates at the same time. Or
> > > alternatively we can think of offline defragmentation. It will be easier
> > > to
> > > implement and faster, but concurrent operations will be prohibited.
> >
Vyacheslav Daradur created IGNITE-10862:
---
Summary: Introduce tool to free up space on a disc of unused
memory pages
Key: IGNITE-10862
URL: https://issues.apache.org/jira/browse/IGNITE-10862
Hi, which Ignite's version do you use?
*Local* queries are prohibited on client nodes since they do not store data.
The check was added within task [1] and included in Ignite 2.7 release.
[1] https://issues.apache.org/jira/browse/IGNITE-8915
On Tue, Jan 8, 2019 at 10:17 PM prashant wrote:
>
>
Igniters, we have faced with the following problem on one of our deployments.
Let's imagine that we have used IgniteCache with enabled PDS during the time:
- hardware disc space has been occupied during growing up of an amount
of data, e.g. 100Gb;
- then, we removed non-actual data, e.g 50Gb,
ns both for the code and design review.
>
> В Пн, 24/12/2018 в 20:50 +0300, Nikolay Izhikov пишет:
> > Hello, Igniters.
> >
> > Please, let us know, if someone want to do additional review of this PR.
> >
> > В Пн, 24/12/2018 в 20:23 +0300, Vyacheslav Daradur пишет:
Vyacheslav Daradur created IGNITE-10830:
---
Summary: Return back semantic of
GridServiceProcessor#ServiceTopologyCallable to avoid possible serialization
issues
Key: IGNITE-10830
URL: https
The fix has been approved by Bot's visa and merged to master.
Anton, thanks for your help.
On Tue, Dec 25, 2018 at 3:41 PM Anton Vinogradov wrote:
>
> Slava,
>
> please fill the issue with fix and tcbot visa.
>
> On Tue, Dec 25, 2018 at 12:18 PM Vyacheslav Daradur
> wrote
Vyacheslav Daradur created IGNITE-10817:
---
Summary: Service Grid: Introduce diagnostic tool to dump pending
deployment tasks
Key: IGNITE-10817
URL: https://issues.apache.org/jira/browse/IGNITE-10817
The test has been fixed within
https://issues.apache.org/jira/browse/IGNITE-10739
Thanks to Oleg Ignatenko!
On Tue, Dec 25, 2018 at 7:37 AM Vyacheslav Daradur wrote:
>
> The failure has been introduced within task:
> https://issues.apache.org/jira/browse/IGNITE-10671 Double
> in
I prepared PR [1] to fix the issue, the test became green.
Anton, could you assist with the merge, please?
[1] https://github.com/apache/ignite/pull/5739
[2] https://ci.ignite.apache.org/viewQueued.html?itemId=2641732
On Tue, Dec 25, 2018 at 10:53 AM Vyacheslav Daradur wrote:
>
> This
Vyacheslav Daradur created IGNITE-10811:
---
Summary: Add new TC build-config to test Service Grid new and old
implementations
Key: IGNITE-10811
URL: https://issues.apache.org/jira/browse/IGNITE-10811
This is my fault, introduced within
https://issues.apache.org/jira/browse/IGNITE-10715
I have no idea why it had not been failed during testing on TC.
I will prepare the fix quickly.
On Tue, Dec 25, 2018 at 2:37 AM wrote:
>
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be
The failure has been introduced within task:
https://issues.apache.org/jira/browse/IGNITE-10671 Double
initialization of segmentAware and FileArchiver lead to race breaking
file compression.
The cause is a missed '@Test' annotation.
Here is the patch to fix [1], TC test is green [2].
[1]
-in-GridDhtPartitionsExchangeFuture-onDone-td35946.html
On Mon, Dec 24, 2018 at 4:23 PM Vyacheslav Daradur wrote:
>
> Stanislav, thank you for the notes, most of them have been resolved. I
> answered on GitHub.
>
>
> On Sun, Dec 23, 2018 at 9:34 PM Stanislav Lukyanov
> wrote:
> >
> &
ome comments – almost all are about minor issues, grammar and code
> style.
>
> Stan
>
> From: Vyacheslav Daradur
> Sent: 21 декабря 2018 г. 14:58
> To: dev@ignite.apache.org
> Subject: Re: Service grid redesign
>
> Igniters,
>
> Please, let us know if someone is
ira/browse/IGNITE-10715
On Tue, Dec 18, 2018 at 6:29 PM Anton Vinogradov wrote:
>
> Folks,
>
> Now I see 5-10% speedup at all TC suites right after the merge.
> Great fix!
>
>
> On Mon, Dec 17, 2018 at 2:39 PM Vyacheslav Daradur
> wrote:
>
> > Andrey Mashenkov
Igniters,
Please, let us know if someone is going to do an additional review?
We should know can we merge the PR since it has been approved by
Nikolay Izhikov and Denis Mekhanikov or we should wait for other
community members.
On Thu, Dec 20, 2018 at 7:52 PM Vyacheslav Daradur wrote:
>
points as well.
> >
> > Denis
> >
> > ср, 19 дек. 2018 г. в 17:37, Nikolay Izhikov :
> >
> > > Denis,
> > >
> > > I don't think that differences with your and my naming is huge :)
> > > And, it's definetely a matter of
from GridDhtPartitionsFullMessage.
> It doesn't really reflect its function. This message is supposed to mark
> the point in time, when deployment is finished.
>
> Denis
>
>
> пт, 14 дек. 2018 г. в 11:30, Vyacheslav Daradur :
>
> > >*1. Testing of the cache-based i
; >
> > Denis
> >
> > ср, 5 дек. 2018 г. в 18:34, Vyacheslav Daradur :
> >
> > > I filled a task [1].
> > >
> > > >> Slava, do you think Platforms tests can be fixed as well or one more
> > > ticket
> > > should be created?
&
Andrey Mashenkov, at first sight, I have not seen any problems with
.NET platform.
I believe we need carefully configure ports in platform's examples,
additional actions should not be required.
On Mon, Dec 17, 2018 at 2:35 PM Vyacheslav Daradur wrote:
>
> The task [1] i
Vyacheslav Daradur created IGNITE-10715:
---
Summary: Remove boilerplate of settings 'TcpDiscoveryVmIpFinder'
in tests
Key: IGNITE-10715
URL: https://issues.apache.org/jira/browse/IGNITE-10715
Vyacheslav Daradur created IGNITE-10705:
---
Summary: Wrong check of test's compatible 'dataMode' in
IgniteConfigVariationsAbstractTest
Key: IGNITE-10705
URL: https://issues.apache.org/jira/browse/IGNITE-10705
cause
> > we need someone to sign a software grant agreement, but there were several
> > people who contributed to the plugin.
> >
> > Some of the authors are not active contributors anymore. So I've stuck with
> > finding a way how to donate.
> >
> > Since
Dmitry Pavlov,
As far as I know, we are able to use following construction to ignore test:
Assume.assumeTrue("link-to-issue", false);
On Fri, Dec 14, 2018 at 5:44 PM Dmitriy Pavlov wrote:
>
> Thank you, Dmitrii,
>
> I've started unmuting tests starting from yesterday.
>
> Now muted test count
>*1. Testing of the cache-based implementation of the service grid.*
> I think, we should make a test suite, that will test the old implementation
> until we remove it from the project.
Agree. This is exactly what should be done as the first step once
phase 1 will be merged.
I think all tests in
Yes, it is expected this test become not flaky once Service Grid phase
1 have been merged:
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5756858704963167219=%3Cdefault%3E=testDetails_IgniteTests24Java8=pull%2F4434%2Fhead
On Thu, Dec 13, 2018 at 3:22 PM Dmitriy Pavlov
ion of the service processor, we use
`JdkMarshaller` as a common marshaller.
`IgniteServiceConfigVariationsFullApiTest` has been fixed to test
modes {SERIALIZABLE, CUSTOM_SERIALIZABLE, EXTERNALIZABLE}.
Thanks!
On Wed, Dec 12, 2018 at 4:30 PM Vyacheslav Daradur wrote:
>
> A bit more:
>
>
approaches seem good to me, in the current PR second approach has
been implemented.
It would be great if other Ignite's experts said their opinion.
On Wed, Dec 12, 2018 at 3:52 PM Vyacheslav Daradur wrote:
>
> Denis, thank you for the answer.
>
> I've already implemented the s
traints should be applied to them.
>
> So, I'm for using the *JdkMarshaller* regardless of the service type or a
> node state.
>
> Denis
>
> пт, 7 дек. 2018 г. в 15:57, Vyacheslav Daradur :
>
> > Igniters, I need your advice about the following problem:
> >
&
>From my point of view, it's important to further develop the thin client.
Users should be able to use most of Ignite's components via thin
client, as far as possible, just for example:
* transactional CRUD operations over data in the cluster;
* deploy/undeploy and monitor services in the Service
Alexey,
Have a look at the 'PluginProvider' interface, if you implemented a
telemetry service as a plugin:
* plugin may be placed in the 'web-console' module;
* plugin is initialized at node startup and is stopped at node shutdown;
* plugin have access to all Ignite's internals through context;
*
1 - 100 of 456 matches
Mail list logo
