Re: Semaphore Stuck when no acquirers to assign permit

Hi Alexey, I already reviewed it, but wanted to see the resolution of IGNITE-6454 first before I merge. Thanks, Vladisav On Fri, Feb 16, 2018 at 12:39 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Hi Vladislav, > > Can you please finalize the review? I would

Re: Ignite Semaphore Bug 7090

Hi Tim, thank you for delving deeper into the problem, I left you a comment/question on the JIRA. Best regards, Vladisav On Tue, Jan 23, 2018 at 3:00 PM, Vladisav Jelisavcic <vladis...@gmail.com> wrote: > Hi Tim, > > thanks for the update! I left you a comment on Jira. &

Re: Ignite Semaphore Bug 7090

Hi Tim, thanks for the update! I left you a comment on Jira. Best regards, Vladisav On Mon, Jan 22, 2018 at 6:17 PM, Tim Onyschak <tonysc...@gmail.com> wrote: > Hey Vladisav, > > I implemented your requests. Take a look, specifically, i created an > interface to encapsula

Re: Ignite Semaphore Bug 7090

Hi Tim, I reviewed your contribution and left you some comments on the pr. Thanks! Vladisav On Wed, Jan 17, 2018 at 10:14 PM, Vladisav Jelisavcic <vladis...@gmail.com> wrote: > Hi Tim, > > thank you for the contribution! > I'll do the review soon and let you know. > >

Re: Ignite ML Models improvements

Hi Artem, I agree, it is not supported in many frameworks; on the other hand, Spark MLlib supports it [1]. I think it is good thing to check with users if there is a need for this, since we are already on the topic of model importing/exporting. Best regards, Vladisav [1] https

Re: Ignite ML Models improvements

Hi Yury, since we're already on topic for importing/exporting models, just as a thought: maybe we should add support for PMML [1] [2]? Best regards, Vladisav [1] http://dmg.org/pmml/v4-1/GeneralStructure.html [2] https://github.com/jpmml/jpmml-model On Mon, Oct 16, 2017 at 2:20 PM, Yury Babak

Re: Ignite ML, next steps (IGNITE-5029)

Hi, excellent job so far! What about classification algorithms? If everyone agrees, let's start by adding logistic regression to the list: https://issues.apache.org/jira/browse/IGNITE-5059 Best regards, Vladisav On Fri, Apr 21, 2017 at 10:00 PM, Nikita Ivanov <nivano...@gmail.com>

[jira] [Created] (IGNITE-5059) Implement logistic regression

Vladisav Jelisavcic created IGNITE-5059: --- Summary: Implement logistic regression Key: IGNITE-5059 URL: https://issues.apache.org/jira/browse/IGNITE-5059 Project: Ignite Issue Type

Re: IgniteSemaphore and failoverSafe flag

iteTests_IgniteDataStrucutures# > testNameId-979977708202725050 > [2] https://issues.apache.org/jira/browse/IGNITE-1977 > > Thanks! > > 14.04.2017 15:27, Dmitry Karachentsev пишет: > > Vladislav, > > Yep, you're right. I'll fix it. > > Thanks! > > 14.04.2017 15:18, Vla

Re: IgniteSemaphore and failoverSafe flag

wLog.html?buildId=544238; > tab=buildResultsDiv=IgniteTests_IgniteBinaryObjectsDataStrucut > ures > > Thanks! > > -Dmitry. > > 13.04.2017 16:15, Dmitry Karachentsev пишет: > > Thanks a lot! > > 12.04.2017 16:35, Vladisav Jelisavcic пишет: > > Hi Dmit

Re: IgniteSemaphore and failoverSafe flag

Hi Dmitry, sure, I made a fix, take a look at the PR and the comments in the ticket. Best regards, Vladisav On Tue, Apr 11, 2017 at 3:00 PM, Dmitry Karachentsev < dkarachent...@gridgain.com> wrote: > Hi Vladislav, > > Thanks for your contribution! But it seems doesn't fix

[GitHub] ignite pull request #1780: IGNITE-4173

GitHub user vladisav opened a pull request: https://github.com/apache/ignite/pull/1780 IGNITE-4173 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladisav/ignite ignite-4173 Alternatively you can review and apply

[GitHub] ignite pull request #1751: IGNITE-1977 Fixes IgniteSemaphore failover deadlo...

GitHub user vladisav opened a pull request: https://github.com/apache/ignite/pull/1751 IGNITE-1977 Fixes IgniteSemaphore failover deadlock/fail bug You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladisav/ignite ignite-1977

Re: IgniteSemaphore and failoverSafe flag

Hey Dmitry, sorry for the late reply, I'll try to bake a pr later during the day. Best regards, Vladisav On Tue, Apr 4, 2017 at 11:05 AM, Dmitry Karachentsev < dkarachent...@gridgain.com> wrote: > Hi Vladislav, > > I see you're developing [1] for a while, did you have an

Re: IgniteSemaphore and failoverSafe flag

Hi everyone, I agree with Val, he's got a point; recreating the lock doesn't seem possible (at least not the with the transactional cache lock/semaphore we have). Is this re-create behavior really needed? Best regards, Vladisav On Thu, Mar 16, 2017 at 8:34 PM, Valentin Kulichenko

Re: [VOTE] Apache Ignite 1.8.0 RC1

+1 (non-binding) On Tue, Dec 6, 2016 at 9:17 AM, Anton Vinogradov wrote: > +1 (binding) > > On Tue, Dec 6, 2016 at 3:43 AM, Roman Shtykh > wrote: > > > +1 (binding) > > > > -Roman > > > > > > > > > > On Tuesday, December 6, 2016 8:14 AM,

Re: [VOTE] Use Upsource for Code Review

+1 (non-binding) On Wed, Nov 16, 2016 at 6:15 PM, Denis Magda wrote: > +1 > > — > Denis > > > On Nov 16, 2016, at 2:08 AM, Pavel Tupitsyn > wrote: > > > > Following the discussion on Upsource [1], > > I would like to call a vote on accepting it as our

Re: IGNITE-4155 IgniteSemaphoreExample unexpected behavior

Hi Sergey, thanks for finding and submitting this bug! Best regards, Vladisav On Thu, Nov 10, 2016 at 1:46 PM, Sergey Chugunov <sergey.chugu...@gmail.com> wrote: > Hello Vladisav, > > Thanks for confirmation! > > I created a JIRA <https://issues.apache.org/jira/browse

Re: IGNITE-4155 IgniteSemaphoreExample unexpected behavior

nodes, this really is a bug. Thanks! Vladisav On Wed, Nov 9, 2016 at 11:23 AM, Sergey Chugunov <sergey.chugu...@gmail.com> wrote: > Hello Vladisav, > > I found this behavior in a very simple environment: I had two nodes on my > local machine started by *ExampleNodeStartup* clas

Re: IGNITE-4155 IgniteSemaphoreExample unexpected behavior

. If this is not the case (test was executed normally) then please submit a ticket describing more your setup, how many nodes, how many backups configured, etc.. Thanks! Vladisav On Tue, Nov 8, 2016 at 10:37 AM, Sergey Chugunov <sergey.chugu...@gmail.com> wrote: > Hello folks, > > I

Re: IgniteSemaphore and failoverSafe flag

(this is similar to: https://issues.apache.org/jira/browse/IGNITE-3386). This should be fixed (semaphore should be recreated when create==true, as suggested by Denis in the ticket). It should be a minor fix, will be ready for 1.8. Best regards, Vladisav On Tue, Nov 1, 2016 at 5:41 PM, Andrey Gura

Re: NullPointerException when stopping IgniteSemaphore

Sure, I'll do the review. It is lazy initialized, same as latch and other datastructures. Regards, Vladisav On Thu, Jul 21, 2016 at 10:24 AM, Yakov Zhdanov <yzhda...@apache.org> wrote: > Vladislav, can you please review and merge to master the fix and test case > suggested by Kro

ReadWriteUpdateLock

, Vladisav

Re: Ignite Download links broken

Not working for me also, but only 1.6.0 (latest) and 1.5.0.final, the rest is working fine. On Mon, Jun 20, 2016 at 8:02 AM, Sergey Kozlov wrote: > Hi > > It's a known issue: apache site puts links to a nearest site for user (I > suppose it based on IP address) and does it

Re: Integration with Apache Apex

Hi, it looks really interesting to me, I'll be glad to pick this one. Best regards, Vladisav On Fri, May 13, 2016 at 7:41 AM, Thomas Weise <t...@apache.org> wrote: > Dear Ignite community, > > Apache Apex is a data in-motion processing platform. It was developed since >

[GitHub] ignite pull request: IGNITE-642: Implements cache distributed reen...

Github user vladisav closed the pull request at: https://github.com/apache/ignite/pull/519 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

Yakov, did you had time to do another review round of ignite-642? Thanks! On Fri, Apr 15, 2016 at 3:53 PM, Vladisav Jelisavcic <vladis...@gmail.com> wrote: > Yakov, > > I've finished the initialization tests for ignite-642 (and moved > serialization test from GridCac

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

Yakov, I've finished the initialization tests for ignite-642 (and moved serialization test from GridCacheLockAbstractTest to IgniteLockAbstractSelfTest). Please check the commit and let me know if you spot anything else. Thanks! On Fri, Apr 15, 2016 at 10:11 AM, Vladisav Jelisavcic <vla

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

Yakov, I reviewed the changes in ignite-642 and it looks good to me, but I have one question. Can you please look at my comment in ignite-642 ticket? Thanks! Vladisav On Thu, Apr 14, 2016 at 7:51 PM, Vladisav Jelisavcic <vladis...@gmail.com> wrote: > Sure, I'll look into it la

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

Sure, I'll look into it later today, or tomorrow at the latest On Thu, Apr 14, 2016 at 5:53 PM, Yakov Zhdanov wrote: > Vlad, please see my changes in ignite-642 and comment in the ticket. > > Alex, can you please take a look at my latest commit as well and provide >

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

Yakov, sorry for the long delay, I added another commit to the PR, can you please do the review again? Thanks! Vladisav On Sun, Mar 27, 2016 at 11:30 AM, Vladisav Jelisavcic <vladis...@gmail.com> wrote: > Yakov, I've seen your comments, can you please check the jira again? > > &

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

Yakov, I've seen your comments, can you please check the jira again? On Wed, Mar 23, 2016 at 4:46 PM, Yakov Zhdanov <yzhda...@apache.org> wrote: > Vlad, can you please check my comments again? > > --Yakov > > 2016-03-18 17:57 GMT+03:00 Vladisav Jelisavcic <vladis...@gm

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

Hi Yakov, yes, thanks for the comments, I think everything should be ok now, please review the PR and tell me if you think anything else is needed. Once ignite-642 is merged into master, I'll submit a PR for IgniteReadWriteLock (hopefully on time for 1.6. release). Best regrads, Vladisav

[jira] [Created] (IGNITE-2768) Public API for data structures should be guarded from being invoked after node is stopped

Vladisav Jelisavcic created IGNITE-2768: --- Summary: Public API for data structures should be guarded from being invoked after node is stopped Key: IGNITE-2768 URL: https://issues.apache.org/jira/browse

Re: distributed data types for ML applications

This sounds excellent, I'll get right to it. Best regards, Vladisav On Fri, Mar 4, 2016 at 2:48 AM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > Vladislav, > > This would be a great contribution. For a feature like this, I would pick 1 > ML library and propose the

distributed data types for ML applications

Igniters, is IGNITE-1251 still a thing? If so, I would really like to start working on this one. Best regards, Vladisav

Re: Semaphore waiting for permit even if node is shut down

Sure, no problem. I created a ticket: https://issues.apache.org/jira/browse/IGNITE-2735 and a PR to resolve this problem. I think this should also fix: IGNITE-1977 but the non-failover test scenario is not good anymore; Best regards, Vladisav On Mon, Feb 29, 2016 at 2:32 PM, Vladimir

[GitHub] ignite pull request: IGNITE-2735: Fixes distributed semaphore loca...

GitHub user vladisav opened a pull request: https://github.com/apache/ignite/pull/525 IGNITE-2735: Fixes distributed semaphore local node stopping issue. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vladisav/ignite ignite

[jira] [Created] (IGNITE-2735) Interrupt all acquires on local node after ignite.close

Vladisav Jelisavcic created IGNITE-2735: --- Summary: Interrupt all acquires on local node after ignite.close Key: IGNITE-2735 URL: https://issues.apache.org/jira/browse/IGNITE-2735 Project: Ignite

[jira] [Created] (IGNITE-2399) Add asynchronous acquire to IgniteSemaphore

Vladisav Jelisavcic created IGNITE-2399: --- Summary: Add asynchronous acquire to IgniteSemaphore Key: IGNITE-2399 URL: https://issues.apache.org/jira/browse/IGNITE-2399 Project: Ignite

Re: Semaphore action

Andrey Kornev <andrewkor...@hotmail.com> > > Sent: Sunday, January 17, 2016 10:27 AM > > Subject: RE: Semaphore action > > To: <dev@ignite.apache.org> > > > > > >Vladisav, > > > > It would be great if you c

Re: Ignite-1.5 Release

with TOP_CHANGE_THEAD_CNT = 1 everything is running ok; @Yakov I made a new commit to my IGNITE-638 branch, can you please take a look? Best regards, Vladisav > On Wed, Nov 11, 2015 at 3:48 PM, Denis Magda <dma...@gridgain.com> wrote: > > > Hi Vladislav, > &

Re: IgniteMultiMap design

v 3, 2015 at 5:46 AM, Vladisav Jelisavcic <vladis...@gmail.com> > wrote: > > > Dear Dmitriy, > > > > it sounds excellent, I would like to do it, > > but I would like to implement ReentrantLock first: > > https://issues.apache.org/jira/browse/IGNITE-642 >

Re: IgniteMultiMap design

Dear Dmitriy, it sounds excellent, I would like to do it, but I would like to implement ReentrantLock first: https://issues.apache.org/jira/browse/IGNITE-642 What do you think? On Tue, Nov 3, 2015 at 3:37 AM, Dmitriy Setrakyan wrote: > Igniters, > > MultiMap should be

[GitHub] ignite pull request: IGNITE-638: Implements cache distributed sema...

GitHub user vladisav reopened a pull request: https://github.com/apache/ignite/pull/120 IGNITE-638: Implements cache distributed semaphore This interface provides a rich API for working with distributed semaphore. Distributed semaphore provides functionality similar

[GitHub] ignite pull request: IGNITE-638: Implements cache distributed sema...

Github user vladisav closed the pull request at: https://github.com/apache/ignite/pull/120 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Semaphore issue

Hi everyone, my name is VJ, i would like to implement IgniteSemaphore datastructure ( IGNITE-638). My Jira ID is vladisav, can someone please assign it to me? Thanks, VJ