Igor,
I’ve double checked and do confirm that your account was added to a special
LDAP group that allows you to commit changes.
Please make sure that you use a valid username/password combination.
—
Denis
> On Mar 17, 2017, at 1:23 PM, Konstantin Boudnik wrote:
>
> +1
> PMC members don't hav
+1
PMC members don't have _any_ special privileges when it gets to the code access
Cos
--
Take care,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of an
All committers, PMC or not, should have write access to the code.
On Fri, Mar 17, 2017 at 12:54 PM, Denis Magda wrote:
> CC-ing the dev list.
>
> Igor, it looks strange to me. I received a notification saying that
> ‘isapego’ was established. Did you setup the password?
>
> BTW, if to refer to t
Sergey,
I this case, I would agree with the approach proposed by Denis, where you
would return an array of values. However, I still think we should provide
an overall average value for the free space as well. I also think that we
need to come up with some way to provide the fragmentation score, sa
CC-ing the dev list.
Igor, it looks strange to me. I received a notification saying that ‘isapego’
was established. Did you setup the password?
BTW, if to refer to this page [1] then only PMC members have a write access to
the repository:
They have write access to the code repository,
*Dmitri
Val,
Will it be possible to incorporate the fix into the nearest 2.0 release?
—
Denis
> On Mar 17, 2017, at 11:43 AM, Rishi Yagnik wrote:
>
> Hi Val,
>
> Hope you are well, any update on web session clustering.
>
> Thanks,
> Rishi
>
> On Sat, Mar 11, 2017 at 12:29 PM, Rishi Yagnik
> wrote
Sergey, Ilya,
Thanks for the clarification. We’re on the same page.
Dmitriy, Sergi, Alex G., do you have any thoughts on this?
—
Denis
> On Mar 17, 2017, at 5:33 AM, Ilya Lantukh wrote:
>
> Denis, Sergey,
>
> Changes in https://issues.apache.org/jira/browse/IGNITE-4535 won't be so
> global.
Hi Val,
Hope you are well, any update on web session clustering.
Thanks,
Rishi
On Sat, Mar 11, 2017 at 12:29 PM, Rishi Yagnik
wrote:
> Hi Val,
>
> Thanks looking forward for the fix..
>
> Take Care,
> Rishi
>
> > On Mar 11, 2017, at 11:31 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.c
GitHub user skalashnikov opened a pull request:
https://github.com/apache/ignite/pull/1638
IGNITE-3487: Made _key and _val columns hidden
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3487
Alterna
Github user skalashnikov closed the pull request at:
https://github.com/apache/ignite/pull/1573
---
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
Valentin, thank you.
Aleksey, yeah :-)
2017-03-16 15:51 GMT+03:00 ALEKSEY KUZNETSOV :
> watch him, he is gonna remove all the messages he doesn't like :)
>
> чт, 16 мар. 2017 г. в 14:56, Valentin Kulichenko <
> valentin.kuliche...@gmail.com>:
>
> > Hi,
> >
> > These classes are part of plugin fr
You know better, go ahead! :)
Sergi
2017-03-17 16:16 GMT+03:00 ALEKSEY KUZNETSOV :
> we've discovered several problems regarding your "accumulation"
> approach.These are
>
>1. perfomance issues when transfering data from temporary cache to
>permanent one. Keep in mind big deal of concure
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/1637
IGNITE-3586: CPP: Made QueryArgument internal
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3586
Alternatively
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/1636
IGNITE-518: unmute fixed tests.
Unmute tests that was fixed in IGNITE-4036
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ig
Hi,
GridNearTx*Request are sent from the originating node while GridDhtTx*Request
are sent from the primary node.
If originating node is primary the same time, then only GridDhtTx*Request
is sent.
On Fri, Mar 17, 2017 at 4:48 PM, ALEKSEY KUZNETSOV wrote:
> Hi all! We've got a group of GridDhtT
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/1635
IGNITE-4002: Fixed warning/error messages during ODBC driver installation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-igni
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/1634
IGNITE-4834
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4834
Alternatively you can review and apply these
Hi all! We've got a group of GridDhtTx*Request classes, how do they relate
to GridNearTx*Request classes?
--
*Best Regards,*
*Kuznetsov Aleksey*
we've discovered several problems regarding your "accumulation"
approach.These are
1. perfomance issues when transfering data from temporary cache to
permanent one. Keep in mind big deal of concurent transactions in Service
commiter
2. extreme memory load when keeping temporary cache i
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/1633
IGNITE-4827
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4827
Alternatively you can review and apply
Denis, Sergey,
Changes in https://issues.apache.org/jira/browse/IGNITE-4535 won't be so
global. I am not going to replace older mechanics, but rather re-enable and
adjust them to work with PageMemory. We will still use the same distributed
hash table and evict entries based on existing EvictionPol
Tomas Novak created IGNITE-4836:
---
Summary: Yarn deployment is ignoring memory limits
Key: IGNITE-4836
URL: https://issues.apache.org/jira/browse/IGNITE-4836
Project: Ignite
Issue Type: Bug
Alexandr Fedotov created IGNITE-4835:
Summary: Add ability to start rebalancing from management console
Key: IGNITE-4835
URL: https://issues.apache.org/jira/browse/IGNITE-4835
Project: Ignite
Vladimir Ozerov created IGNITE-4834:
---
Summary: Allow execution of optional tasks in exchange worker
Key: IGNITE-4834
URL: https://issues.apache.org/jira/browse/IGNITE-4834
Project: Ignite
I
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/1632
Ignite 1.7.9 p1 Release
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.7.9-p1
Alternatively you can rev
Dmitry Karachentsev created IGNITE-4833:
---
Summary: IngiteClientRejoinTest sometimes fails with enabled peer
class loading
Key: IGNITE-4833
URL: https://issues.apache.org/jira/browse/IGNITE-4833
Dmitriy,
My main goal was to add a metric to estimate FreeList space fragmentation
and "hist" was the first thing I came up with.
Let's consider one case: we placed into a cache 4 entities 60% page size
each.
After that we'll have 4 pages in FreeList each with a hole of 40% of it's
size.
Utilizat
Denis,
My answers are in place.
On Thu, Mar 16, 2017 at 9:04 PM, Denis Magda wrote:
> Sergey,
>
> Considering that the swap tier will no longer be supported in 2.0 all the
> methods that start with ‘getSwap…’ are no longer relevant and have to be
> removed from metrics. For instance, the swap f
Github user SomeFire closed the pull request at:
https://github.com/apache/ignite/pull/1631
---
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 e
GitHub user SomeFire opened a pull request:
https://github.com/apache/ignite/pull/1631
IGNITE-4795
+licensies
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SomeFire/ignite ignite-4795
Alternatively you can review and apply thes
Valentin, ok, thank you.
2017-03-16 18:39 GMT+03:00 Valentin Kulichenko <
valentin.kuliche...@gmail.com>:
> Vyacheslav,
>
> I will review and merge in nearest time.
>
> -Val
>
> On Thu, Mar 16, 2017 at 8:08 AM, Vyacheslav Daradur
> wrote:
>
> > Hello everyone.
> >
> > Please review changes: *htt
31 matches
Mail list logo
