Val and Michael ,
Very good point!
Any idea how it could be implemented?
Actually I need distributed scheduling.
On Thu, Jun 22, 2017 at 5:37 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> I think Michael brought up a very good point. Current ignite-scheduler
> module sched
Anton, Nikolay,
Looks like you participated in the fix. Can you please check?
-Val
On Wed, Jun 21, 2017 at 7:01 PM Igor Rudyak wrote:
> Thanks Val,
>
> It looks like there is still this problem in version 2.0.0
>
> Igor
>
> On Wed, Jun 21, 2017 at 3:20 PM, Valentin Kulichenko <
> valentin.kuli
Thanks Val,
It looks like there is still this problem in version 2.0.0
Igor
On Wed, Jun 21, 2017 at 3:20 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Igor,
>
> Here is the ticket I'm talking about:
> https://issues.apache.org/jira/browse/IGNITE-3230
>
> -Val
>
> On Wed, Jun
I think Michael brought up a very good point. Current ignite-scheduler
module schedules jobs only locally which is not very useful in distributed
system. I don't think I've ever seen it used and I don't think it makes
sense to spend time on it if we just replace one dependency with another.
However
Hi Nikita,
1. Makes sense to me.
2. Externalizable object should not be written as binary with flag 103, it
should be written in the same way it's written now. I don't see any reason
to change the protocol. Purpose of this task it to move the logic to binary
marshaller instead of depending on opt
I agree. Ivan, do you have objections?
-Val
On Mon, Jun 19, 2017 at 3:55 PM, Dmitriy Setrakyan
wrote:
> Ivan,
>
> The semantic now is very confusing, because localEvict does not evict to
> off-heap, it just removes it from on-heap. The off-heap cache always has
> the entry anyway.
>
> My vote w
If taking the quartz route, it be great if ignite could expose a distributed
ignite job store, so you could setup and use quartz in a distributed way, in a
similar way to terracotta or hazelcasts quartz jobstores.
Sent from my iPhone
> On 21 Jun 2017, at 15:43, Alexey Kuznetsov wrote:
>
> Hi
Igor,
Here is the ticket I'm talking about:
https://issues.apache.org/jira/browse/IGNITE-3230
-Val
On Wed, Jun 21, 2017 at 8:57 AM, Igor Rudyak wrote:
> Val,
>
> Are there any ticket for this in Jira?
>
> Igor
>
> On Jun 21, 2017 5:50 AM, "Valentin Kulichenko" <
> valentin.kuliche...@gmail.com
Github user AMashenkov closed the pull request at:
https://github.com/apache/ignite/pull/1949
---
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 is
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/2178
Ignite-1.7.6-p2
for test purposes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.7.6-p2-fixed
Alternativel
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/2177
Ignite-1.8.8.b1
for test purposes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.8.8.b1
Alternatively you c
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/2176
ignite-5574 For offheap_tiered cache first try read value from offheap in
order to avoid redundant synchronization on entry
You can merge this pull request into a Git repository by running:
$
Andrey Gura created IGNITE-5574:
---
Summary: Try to get rid of blocking synchronization on cache entry
for cache.localPeek operation
Key: IGNITE-5574
URL: https://issues.apache.org/jira/browse/IGNITE-5574
Val,
Are there any ticket for this in Jira?
Igor
On Jun 21, 2017 5:50 AM, "Valentin Kulichenko" <
valentin.kuliche...@gmail.com> wrote:
> Igor,
>
> What version are you going on? I believe we already fixed this in the past.
>
> -Val
>
> On Wed, Jun 21, 2017 at 2:30 AM Igor Rudyak wrote:
>
> >
Hi Val,
I am using version 2.0.0.
Igor
On Jun 21, 2017 5:50 AM, "Valentin Kulichenko" <
valentin.kuliche...@gmail.com> wrote:
> Igor,
>
> What version are you going on? I believe we already fixed this in the past.
>
> -Val
>
> On Wed, Jun 21, 2017 at 2:30 AM Igor Rudyak wrote:
>
> > Hi guys,
>
GitHub user ntikhonov opened a pull request:
https://github.com/apache/ignite/pull/2175
IGNITE-5489
IGNITE-5489
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5489
Alternatively you can review and a
ation: 49
<17:02:09> Starting iteration: 45
<17:02:09> Starting iteration: 38
<17:02:09> Starting iteration: 42
<17:02:09> Starting iteration: 43
<17:02:09> Starting iteration: 40
<17:02:09> Starting iteration: 35
<17:02:09> Starting iteration: 31
<17
Hi!
Good point, I will take a look.
On Wed, Jun 21, 2017 at 5:42 PM, 李玉珏 wrote:
> Hi，
>
>
> There is also an alternative that the community can consider using the
> scheduling functionality in the spring-context module, for the following
> reasons:
> 1.quartz is a very heavy framework, and most
Vladimir Ozerov created IGNITE-5572:
---
Summary: DDL: Support ALTER TABLE ADD COLUMN
Key: IGNITE-5572
URL: https://issues.apache.org/jira/browse/IGNITE-5572
Project: Ignite
Issue Type: Task
Vladimir Ozerov created IGNITE-5571:
---
Summary: Make sure that cache-less execution works as good as
cache-based
Key: IGNITE-5571
URL: https://issues.apache.org/jira/browse/IGNITE-5571
Project: Ignit
GitHub user dspavlov opened a pull request:
https://github.com/apache/ignite/pull/2174
Ignite 5558: mock-based standalone WAL records iterator
Don't merge, this PR is for testing purposes
You can merge this pull request into a Git repository by running:
$ git pull https://githu
Dmitry Karachentsev created IGNITE-5570:
---
Summary: IgniteMessaging should have sendAsync() method
Key: IGNITE-5570
URL: https://issues.apache.org/jira/browse/IGNITE-5570
Project: Ignite
Igor,
What version are you going on? I believe we already fixed this in the past.
-Val
On Wed, Jun 21, 2017 at 2:30 AM Igor Rudyak wrote:
> Hi guys,
>
> How to force *TcpDiscoveryZookeeperIpFinder* to publish public IP address
> (in addition to private IP) of Ignite node when it's deployed in
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/2173
storing binary metadata on disk
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12347
Alternativ
Alexey Goncharuk created IGNITE-5569:
Summary: TCP Discovery SPI allows multiple NODE_JOINED /
NODE_FAILED leading to a cluster DDoS
Key: IGNITE-5569
URL: https://issues.apache.org/jira/browse/IGNITE-5569
Hi，
There is also an alternative that the community can consider using the
scheduling functionality in the spring-context module, for the following
reasons:
1.quartz is a very heavy framework, and most functions we don't need;
2., we already have spring dependencies in our project without intro
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/2172
IGNITE-5548
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5548
Alternatively you can review and apply these
Stanilovsky Evgeny created IGNITE-5568:
--
Summary: setActiveOnStart have no effect on node startup
Key: IGNITE-5568
URL: https://issues.apache.org/jira/browse/IGNITE-5568
Project: Ignite
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/2171
Ingite-gg-12329 Do not update partition map if cluster going to inactive
state.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/grid
Alexander Menshikov created IGNITE-5567:
---
Summary: Make benchmark Ignite.reentrantLock vs IgniteCache.lock
Key: IGNITE-5567
URL: https://issues.apache.org/jira/browse/IGNITE-5567
Project: Ignite
GitHub user ezhuravl opened a pull request:
https://github.com/apache/ignite/pull/2170
H2Indexes are not deleted if key class implements Externalizable
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite
Hello, please review.
PR: https://github.com/apache/ignite/pull/1709/files
JIRA: https://issues.apache.org/jira/browse/IGNITE-2313
CI:
http://ci.ignite.apache.org/viewLog.html?buildId=675135&tab=buildResultsDiv&buildTypeId=Ignite20Tests_RunAll
Thank you very much!
--
View this message in context:
http://apache-ignite-developers.2346864.n4.nabble.com/More-JIRA-rights-tp19006p19008.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
Done.
On Wed, Jun 21, 2017 at 11:44 AM, Jokser wrote:
> Hi guys,
>
> Could you please give me JIRA task workflow rights (assign, change status),
> edit descriptions and so on?
> My JIRA account is Jokser.
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers.2346864.n4.na
Hi guys,
Could you please give me JIRA task workflow rights (assign, change status),
edit descriptions and so on?
My JIRA account is Jokser.
--
View this message in context:
http://apache-ignite-developers.2346864.n4.nabble.com/More-JIRA-rights-tp19006.html
Sent from the Apache Ignite Develope
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/2169
Ignite-gg-12336 Visor node throws NPE on exit
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12336
Denis, great idea!
Best Regards,
Igor
On Wed, Jun 21, 2017 at 6:43 AM, Denis Magda wrote:
> Thanks for confirming that the issue has been solved.
>
> I’ve added a special documentation section [1] to avoid issues like that
> in the future and placed "Platforms Interoperability Getting Started”
Semen Boikov created IGNITE-5566:
Summary: Improve TcpCommunicationSpi protocol for node stopping
Key: IGNITE-5566
URL: https://issues.apache.org/jira/browse/IGNITE-5566
Project: Ignite
Issue
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/2168
IGNITE-5424 Fix GridServiceProxy does not unwraps exception message fâ¦
â¦rom InvocationTargetException.
You can merge this pull request into a Git repository by running:
$ git pull ht
Probably a good task for a newbie.
D.
On Jun 21, 2017, 9:41 AM, at 9:41 AM, Alexey Kuznetsov
wrote:
>Done,
>
>https://issues.apache.org/jira/browse/IGNITE-5565
>
>I think it could take a couple of days in background mode.
>
>On Wed, Jun 21, 2017 at 1:40 PM, Dmitriy Setrakyan
>
>wrote:
>
>> Th
Done,
https://issues.apache.org/jira/browse/IGNITE-5565
I think it could take a couple of days in background mode.
On Wed, Jun 21, 2017 at 1:40 PM, Dmitriy Setrakyan
wrote:
> Thanks! Please file a ticket. Do you have an idea on the amount of work
> this would require?
>
> On Wed, Jun 21, 2017
Alexey Kuznetsov created IGNITE-5565:
Summary: Replace Cron4J with Quartz for ignite-schedule module.
Key: IGNITE-5565
URL: https://issues.apache.org/jira/browse/IGNITE-5565
Project: Ignite
Alexey Goncharuk created IGNITE-5564:
Summary: Race between read-through and topology version update
Key: IGNITE-5564
URL: https://issues.apache.org/jira/browse/IGNITE-5564
Project: Ignite
43 matches
Mail list logo
