Hi Amir,
let me say sincere thank you for continuing to contribute.
Bumping up this thread.
Igniters, who has an expertise here?
вс, 17 июн. 2018 г. в 17:59, Amir Akhmedov :
> Hi All,
> Can you please review my changes for IGNITE-8740.
>
> PR: https://github.com/apache/ignite/pull/4208
> TC:
Hi Amir,
I reviewed the changes and I'm not sure I understood how they fix they
issue. I left more detailed comment in the ticket, can you please clarify?
-Val
On Fri, Jun 22, 2018 at 9:53 AM Dmitry Pavlov wrote:
> Hi Amir,
>
> let me say sincere thank you for continuing to contribute.
>
>
Thanks folks!
Dmitriy P., please proceed with the release finalization. Don't accept any
other commits to 2.6.
--
Denis
On Fri, Jun 22, 2018 at 4:32 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> After a conversation with Amir, IGNITE-8740 is merged to master and 2.6.
>
>
Ilya Suntsov created IGNITE-8864:
Summary: sql-query-put x 5 performance drop
Key: IGNITE-8864
URL: https://issues.apache.org/jira/browse/IGNITE-8864
Project: Ignite
Issue Type: Bug
Val,
I replied to it already :)
Thanks,
Amir
On Fri, Jun 22, 2018 at 7:20 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Amir,
>
> Thanks for quick reaction. I added a follow up question in the ticket.
>
> -Val
>
> On Fri, Jun 22, 2018 at 3:48 PM Amir Akhmedov
> wrote:
>
>>
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4208
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3945
---
Hi Val,
Thanks for your comments. I replied in the ticket with my vision of the
issue and how I tried to solve it. Please check it and let me know.
Thanks,
Amir
On Fri, Jun 22, 2018 at 5:42 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Hi Amir,
>
> I reviewed the changes and
Guys,
I reviewed changes in IGNITE-8740, but I'm not sure the fix is correct. I
left a more detailed comment in the ticket. Hopefully, Mair will be able to
respond shortly and clarify.
-Val
On Fri, Jun 22, 2018 at 10:58 AM Denis Magda wrote:
> Dmitriy,
>
> No, that's an honor for us to see
Amir,
Thanks for quick reaction. I added a follow up question in the ticket.
-Val
On Fri, Jun 22, 2018 at 3:48 PM Amir Akhmedov
wrote:
> Hi Val,
> Thanks for your comments. I replied in the ticket with my vision of the
> issue and how I tried to solve it. Please check it and let me know.
>
>
Great, thanks! As always, happy to contribute!
Thanks,
Amir
On Fri, Jun 22, 2018 at 7:32 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Amir,
>
> I merged you change to master and 2.6. Thanks!
>
> -Val
>
> On Fri, Jun 22, 2018 at 4:21 PM Amir Akhmedov
> wrote:
>
>> Val,
>> I
Amir,
I merged you change to master and 2.6. Thanks!
-Val
On Fri, Jun 22, 2018 at 4:21 PM Amir Akhmedov
wrote:
> Val,
> I replied to it already :)
>
> Thanks,
> Amir
>
>
> On Fri, Jun 22, 2018 at 7:20 PM Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
>> Amir,
>>
>> Thanks for
After a conversation with Amir, IGNITE-8740 is merged to master and 2.6.
-Val
On Fri, Jun 22, 2018 at 2:52 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Guys,
>
> I reviewed changes in IGNITE-8740, but I'm not sure the fix is correct. I
> left a more detailed comment in the
Alexei Scherbakov created IGNITE-8863:
-
Summary: Race on rollback and prepare on near tx can cause remote
tx hang
Key: IGNITE-8863
URL: https://issues.apache.org/jira/browse/IGNITE-8863
Project:
Github user antkr closed the pull request at:
https://github.com/apache/ignite/pull/4103
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3993
---
GitHub user antkr reopened a pull request:
https://github.com/apache/ignite/pull/4103
Ignite 1.9.13
CI
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-1.9.13
Alternatively you can review and apply
Github user antkr closed the pull request at:
https://github.com/apache/ignite/pull/4123
---
Andrey Kuznetsov created IGNITE-8862:
Summary: IgniteChangeGlobalStateTest hangs on TeamCity
Key: IGNITE-8862
URL: https://issues.apache.org/jira/browse/IGNITE-8862
Project: Ignite
Issue
Dmitriy,
No, that's an honor for us to see you in this role ;) Both Andrey Gura,
Anton Vinogradov are our release-management veterans. Please feel free to
contact them directly.
Could you take over this ticket review and include it in the release:
GitHub user ezhuravl opened a pull request:
https://github.com/apache/ignite/pull/4249
IGNITE-8426 LongJVMPauseDetector add logger from context
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8426
Github user antkr closed the pull request at:
https://github.com/apache/ignite/pull/4040
---
On Fri, Jun 22, 2018 at 6:13 AM, Sergey Chugunov
wrote:
> Dmitriy,
>
> Answering to your questions:
>
> 1) policy applies only to servers as coordinator never waits for clients in
> PME protocol;
>
Sergey, to my knowledge, clients do participate in PME (although would be
interesting to find out
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4141
---
Dmitry Karachentsev created IGNITE-8859:
---
Summary: Open upper Java verison bounds
Key: IGNITE-8859
URL: https://issues.apache.org/jira/browse/IGNITE-8859
Project: Ignite
Issue Type:
Sergey Chugunov created IGNITE-8860:
---
Summary: IgniteDiscoveryThread marker interface should be restored
on RingMessageWorker class
Key: IGNITE-8860
URL: https://issues.apache.org/jira/browse/IGNITE-8860
Dmitry Karachentsev created IGNITE-8852:
---
Summary: CacheJoinNodeDiscoveryData.CacheInfo has boolean flags
and long field for flags
Key: IGNITE-8852
URL: https://issues.apache.org/jira/browse/IGNITE-8852
GitHub user pvinokurov opened a pull request:
https://github.com/apache/ignite/pull/4242
IGNITE-8746 EVT_CACHE_REBALANCE_PART_DATA_LOST event received twice â¦
â¦on the coordinator node
You can merge this pull request into a Git repository by running:
$ git pull
Dmitry Karachentsev created IGNITE-8851:
---
Summary: StoredCacheData and CacheJoinNodeDiscoveryData.CacheInfo
duplicate "sql" flag
Key: IGNITE-8851
URL: https://issues.apache.org/jira/browse/IGNITE-8851
Hi Alexey,
Sure, it will be honor for me.
In the same time I relatevely new in this area, so I would highly
appreciate any assistance of experienced community members to make this
happen.
Sincerely,
пт, 22 июн. 2018 г. в 12:18, Alexey Goncharuk :
> Denis,
>
> Currently, I am not aware of
Hi Pavel,
Thank you for the response. Yes, your LINQ example can be a workaround. And
SQL query can be as well.
The small project with LINQ query example can be found here
https://github.com/gromtech/ignite-linq-issue-reproducer
I just want to know if there any plans to support such LINQ
Sergey Chugunov created IGNITE-8853:
---
Summary: Test
CacheSerializableTransactionsTest#testIncrementTxRestart fails on TC
Key: IGNITE-8853
URL: https://issues.apache.org/jira/browse/IGNITE-8853
Denis,
Currently, I am not aware of anybody who can immediately review and
sign-off the suggested patch. The original scope of tickets have been
resolved, so I suggest to move on with what we have now.
I will not be able to continue with the release process until Thursday next
week.
Dmitriy
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4195
---
GitHub user alex-plekhanov opened a pull request:
https://github.com/apache/ignite/pull/4243
IGNITE-8774 Daemon moves cluster to compatibility mode when joins
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alex-plekhanov/ignite
Sergey Chugunov created IGNITE-8855:
---
Summary: Client nodes make a lot of attempts to join topology if
EXCHANGE_HISTORY is significantly smaller than number of clients
Key: IGNITE-8855
URL:
Vyacheslav Koptilin created IGNITE-8856:
---
Summary: Incorrect behavior of BinaryTypeConfiguration in case of
using a wildcard fro type names
Key: IGNITE-8856
URL:
Github user akuznetsov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/4221
---
Github user akuznetsov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/4092
---
Sergey Kozlov created IGNITE-8854:
-
Summary: !indexes and !primarykeys return nothing for
o.a.i.IgniteJdbcDriver
Key: IGNITE-8854
URL: https://issues.apache.org/jira/browse/IGNITE-8854
Project:
GitHub user andrewmed opened a pull request:
https://github.com/apache/ignite/pull/4244
IGNITE-8737: Improve checkpoint logging information
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrewmed/ignite ignite-8737-2
Github user andrewmed closed the pull request at:
https://github.com/apache/ignite/pull/4186
---
Hi Ed,
Which Sergey do you mean? I know a number of contributors.
Sincerely,
вт, 19 июн. 2018 г. в 22:15, Eduard Shangareev :
> Hi,
>
> 1. It looks weird, yeah. Need to ask Sergey, who has changed it last time.
>
> 2. Because we could reuse memory. For example, after cache destroy or
>
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4213
---
GitHub user antkr opened a pull request:
https://github.com/apache/ignite/pull/4245
IGNITE-8836 Added IGNITE_FORCE_JVM_SHUTDOWN_TIMEOUT property to forceâ¦
⦠node shutdown within given timout.
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/4246
Follow up fix for 8471
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-master-8471-followup
Alternatively
Dmitriy,
Answering to your questions:
1) policy applies only to servers as coordinator never waits for clients in
PME protocol;
2) we cannot restart handing node automatically only stop it. Node restart
should be responsibility of monitoring system or end user.
--
Thanks,
Sergey.
On Thu, Jun
Sergey Chugunov created IGNITE-8857:
---
Summary: ZookeeperClusterNode class instances sneak into
BaselineTopology when non-empty user attributes are defined
Key: IGNITE-8857
URL:
Dmitry Karachentsev created IGNITE-8858:
---
Summary: Client none may not stop
Key: IGNITE-8858
URL: https://issues.apache.org/jira/browse/IGNITE-8858
Project: Ignite
Issue Type: Bug
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4224
---
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/4247
IGNITE-8858 - Client none may not stop.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8858
GitHub user andrey-kuznetsov opened a pull request:
https://github.com/apache/ignite/pull/4248
IGNITE-8860 Returned IgniteDiscoveryThread to RingMessageWorker.
You can merge this pull request into a Git repository by running:
$ git pull
Oleg Ostanin created IGNITE-8861:
Summary: Wrong method call in IgniteServise documentation snippet
Key: IGNITE-8861
URL: https://issues.apache.org/jira/browse/IGNITE-8861
Project: Ignite
53 matches
Mail list logo
