Would be nice if someone in the community would pick this ticket up.
On Wed, Aug 8, 2018 at 1:19 AM, Nikolay Izhikov wrote:
> Hello, Valentin.
>
> Yes, this is a bug.
>
> Ticket created - https://issues.apache.org/jira/browse/IGNITE-9229
>
> В Вт, 31/07/2018 в 16:01 -0700, Valentin Kulichenko
Hi David,
Welcome. I believe everyone in the community is happy that new people come
and help.
I've added you to contributor role. You can now assign ticket to yourself.
Sincerely,
Dmitriy Pavlov
P.S. Additional references that should boost your onboarding.
Please subscribe to both dev and
I think we should be updating the IEP with metrics specifications in
parallel.
D.
On Wed, Aug 8, 2018, 05:32 Roman Kondakov
wrote:
> Hi Ivan!
>
> In my opinion we need to preserve the essence of the metrics: if we
> didn't consider dirty writes as updates before MVCC implementation, we
> also
Pavel Pereslegin created IGNITE-9238:
Summary: Test
GridTaskFailoverAffinityRunTest.testNodeRestartClient hangs when coordinator
forces client to reconnect on grid startup.
Key: IGNITE-9238
URL:
I've be working with ignite for almost a year, but haven't contributed
anything back yet.
IGNITE-7616 is annoying me, so I might as well just fix it. My Jira ID is
syssoftsol.
Thanks,
-DH
This change will trigger master every time if free agent percent >50%
longer than 10 minutes. And likelihood that was just one commit in each
runall is increased. But it is not 100% because several commit may be done
while TC was loaded.
Contributed change is not bisect based on git revisions,- I
Yury Babak created IGNITE-9237:
--
Summary: [ML] Random forest optimization
Key: IGNITE-9237
URL: https://issues.apache.org/jira/browse/IGNITE-9237
Project: Ignite
Issue Type: Improvement
Dmitry,
Good news.
How can I trigger build\MTCGA.Bot to find the problem commit?
As for this case I've already found commit who caused the test to fall.
I don't know how to fix this problem. Probably, we slould conslut with
author to find out the right case.
On Wed, 8 Aug 2018 at 18:29 Dmitriy
Hi all,
Looks like no one has objections about the API I want to introduce.
Could someone please review and push my patch?
Thanks,
Mike.
вт, 31 июл. 2018 г. в 13:02, Mikhail Cherkasov :
> > I have commented your change: setProtocols is still redundant since we
> have protocol in
No they are not. I just want to understand.
On Wednesday, August 8, 2018, Dmitriy Pavlov wrote:
> Hi John,
>
> Are these questions related to some contribution?
>
> Sincerely,
> Dmitriy Pavlov
>
> ср, 8 авг. 2018 г. в 3:18, John Wilson :
>
> > Hi,
> >
> > Assume the following:
> >
> >
> >-
Ok, let's fill priority and version for new failures.
About locating changes, which break particular build:
Thanks to Pavel Pereslegin for his recent contribution to MTCGA.Bot. Patch
allows to adaptively trigger 'run all' in case there are enought of free
agents. So it will be easier to locate
I used to think that OS allocates pages not immediately after call to
allocate(), but only during first touch of each page.
I'm not sure every OS provides guaranee that 'allocated' memory will never
cause OOME. Please correct me if I'm wrong.
ср, 8 авг. 2018 г. в 17:38, Dmitriy Setrakyan :
>
Nikolay,
I’ve updated publicagent03_9091 and tested all current builds for Ignite Tests
2.4+ project for master branch.
Please test your PR on this agent (select it when starting build) for correct
java configuration.
If everything is OK — I’ll distribute this Java among all other agents.
Dmitriy, yes, if you set it as blocker and assign it to the next release,
the likelihood of someone looking at it before the release will increase.
We should follow this practice for all new test failures.
Moreover, if someone's change caused a new test failure, then we should try
to contact that
Hello!
I think that the comment sums it up nicely. WebLogic seems to add extra
stuff to session ID, which has to be removed.
What is the problem that you have? I suggest responding to userlist (
*u...@ignite.apache.org
* ) since it's the one to discuss end user problems.
Regards,
--
Ilya
Alexey,
I am not sure I understand. If cache creation proceeds, but memory region
was not allocated, how can the cache operate?
D.
On Wed, Aug 8, 2018 at 8:05 AM, Alexey Goncharuk wrote:
> I do not mind making this change, but note that the reason for non-lazy
> region allocation is the need
Dears,
We are facing a problem with session timeout in weblogic
We are using ignite, spring and spring security and deploy on tomcat and
weblogic
and we found something that Ignite has a special handle for sessionId in case
of WebLogic
String srvInfo = ctx.getServerInfo();
//
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/4499
IGNITE-9236 : Removed setting failureDetectionTimeout to Integer.MAX_VALUE
in tests.
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user andrewmed opened a pull request:
https://github.com/apache/ignite/pull/4498
IGNITE-9235: Transitivity violation in GridMergeIndex Comparator
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Ilya Lantukh created IGNITE-9236:
Summary: Handshake timeout never completes in some tests
(GridCacheReplicatedFailoverSelfTest in particular)
Key: IGNITE-9236
URL:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4489
---
I do not mind making this change, but note that the reason for non-lazy
region allocation is the need to gracefully handle OOME errors during cache
start. When a region is pre-allocated, no OOME can happen.
If a region is allocated dynamically, then all errors that happened during
the node start
Andrew Medvedev created IGNITE-9235:
---
Summary: Transitivity violation in GridMergeIndex Comparator
Key: IGNITE-9235
URL: https://issues.apache.org/jira/browse/IGNITE-9235
Project: Ignite
Alexey Kuznetsov created IGNITE-9234:
Summary: Wrong javadocs about null value for cache name.
Key: IGNITE-9234
URL: https://issues.apache.org/jira/browse/IGNITE-9234
Project: Ignite
Hi Dmitriy,
Would it increase likelihood that somebody will pick up this ticket if we
will set blocker priority?
If it would increase I totally agree. IMO, JIRA priorities do not have much
effect on community members, do it?
Sincerely,
Dmitriy Pavlov
вт, 7 авг. 2018 г. в 14:00, Dmitriy
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4462
---
Hi John,
Are these questions related to some contribution?
Sincerely,
Dmitriy Pavlov
ср, 8 авг. 2018 г. в 3:18, John Wilson :
> Hi,
>
> Assume the following:
>
>
>- I have a transaction coordinator and two primary nodes with 0 backup
>nodes.
>- Persistence store is enabled.
>-
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4376
---
Hi Ivan!
In my opinion we need to preserve the essence of the metrics: if we
didn't consider dirty writes as updates before MVCC implementation, we
also shouldn't count these writes in MVCC metrics implementation too.
So, I think we need to count only committed entries. But we can count
this
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4486
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4491
---
Ivan Pavlukhin created IGNITE-9233:
--
Summary: MVCC SQL: False write conflicts on fast updates
Key: IGNITE-9233
URL: https://issues.apache.org/jira/browse/IGNITE-9233
Project: Ignite
Issue
Dmitry,
I'm not familiar with all details of Ignite release management and can miss
something with changing the right issue priority. Hope you'll help me with
it at the initial stage. Generally, I agree with you here. I've marked this
issue as `Blocker` and attached to `2.7` release as this
Hello Denis,
> Is it a typo? May be it should be something like:
> grid(0).getOrCreateCache(cfg); //< original configuration
Yep, it looks like a typo.
> Can I fix it in my PR?
It would be great :)
Best regards,
Slava.
ср, 8 авг. 2018 г. в 11:09, Denis Garus :
> Hi, Slava!
>
> I
Vyacheslav Daradur created IGNITE-9232:
--
Summary: Remove commented method GridCacheUtils#isMongoCache
Key: IGNITE-9232
URL: https://issues.apache.org/jira/browse/IGNITE-9232
Project: Ignite
Stanilovsky Evgeny created IGNITE-9231:
--
Summary: onMarkDirty improvement throttle implementation.
Key: IGNITE-9231
URL: https://issues.apache.org/jira/browse/IGNITE-9231
Project: Ignite
Sergey Kozlov created IGNITE-9230:
-
Summary: Cannot use array fields in DML oprtations in sqlline
Key: IGNITE-9230
URL: https://issues.apache.org/jira/browse/IGNITE-9230
Project: Ignite
Hi Yriy!
Go ahead! You were added!
--Yakov
2018-08-07 17:19 GMT+03:00 Юрий :
> Hello, Ignite Community!
>
> My name is Iurii. I want to contribute to Apache Ignite.
> my JIRA user name is jooger. Any help on this will be appreciated.
>
> Thanks!
>
> --
> Live with a smile! :D
>
Hi, Slava!
I noticed that in the
IgniteAbstractDynamicCacheStartFailTest#testCacheStartAfterFailure method
the second started cache uses new configuration:
```
public void testCacheStartAfterFailure() throws Exception {
CacheConfiguration cfg = createCacheConfigsWithBrokenAffinityFun(
false, 1,
Dmitry,
As with MVCC we can have multiple versions of each tuple at the same time
it introduces storage overhead. It would be good to have a measure for such
overhead.
Another thing is related to VACUUM procedure. For protecting system from
crash in case of high load it would be great to detect
Hello, Valentin.
Yes, this is a bug.
Ticket created - https://issues.apache.org/jira/browse/IGNITE-9229
В Вт, 31/07/2018 в 16:01 -0700, Valentin Kulichenko пишет:
> Hi Nikolay,
>
> Can you please take a look at this thread on SO?
>
Nikolay Izhikov created IGNITE-9229:
---
Summary: Integration with Spark Data Frame. Add support for a
ARRAY data type
Key: IGNITE-9229
URL: https://issues.apache.org/jira/browse/IGNITE-9229
Project:
42 matches
Mail list logo
