GitHub user a-polyakov opened a pull request:
https://github.com/apache/ignite/pull/4128
IGNITE-8620 Remove intOrder and loc keys from node info in control.sh --tx
utility
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/a-polyak
Github user voipp closed the pull request at:
https://github.com/apache/ignite/pull/4119
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3977
---
Dmitriy,
I’ve replaced root user requirement with ignite user requirement. It is
necessary because after installation ignite user receive all Apache Ignite work
directories ownership (to be able to write woking files there).
In fact, Apache Ignite as a service is configured to run just under th
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3962
---
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/4129
IGNITE-6595: Applied patch.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6596
Alternatively you can review
Hi Alexander,
https://issues.apache.org/jira/browse/IGNITE-8687 is 'In progress'. Is it
expected?
Nikolay, have you some time to apply patch, if it passes review?
Sincerely,
Dmitriy Pavlov
вт, 5 июн. 2018 г. в 5:09, Dmitriy Setrakyan :
> Thanks, Alex! Sounds like a good plan.
>
> On Mon, Jun 4
Vitaliy Biryukov created IGNITE-8699:
Summary: ZookeeperDiscoverySpiTest#testDisconnectOnServersLeft
flaky fails (rarely)
Key: IGNITE-8699
URL: https://issues.apache.org/jira/browse/IGNITE-8699
Pr
Hello, Igniters.
Actually, I don't understand why we should merge in master something broken.
Currently, Ignite is not ready for JCache 1.1.
Only change I see in PR is new profile [1].
Is it required to have it to continue jcache 1.1 support implementation?
I think Alexandex can proceed with cur
Hi
After Alexander create separate tickets for failed tests, everybody is
free to fix them.
So we can proceed faster issue resolving.
Hello, Igniters.
Actually, I don't understand why we should merge in master something broken.
Currently, Ignite is not ready for JCache 1.1.
Only change I see
Nikolay, there isn't anything broken in PR.
The PR is needed to add new build-plan on TC.
We need tools to check that fixes for 1.1 don't break compatibility with 1.0.
On Tue, Jun 5, 2018 at 1:21 PM, Кузнецов Алексей Львович
wrote:
> Hi
>
> After Alexander create separate tickets for failed tes
Vyacheslav,
Let's create build plan on TC for this profile.
Why we need to merge it in master now?
В Вт, 05/06/2018 в 13:29 +0300, Vyacheslav Daradur пишет:
> Nikolay, there isn't anything broken in PR.
>
> The PR is needed to add new build-plan on TC.
>
> We need tools to check that fixes for
AFAIK TeamCity is not able to create such build-plan on the fly.
Moreover, we will not be able to test master branch in both profiles
in this case.
Am I miss something?
On Tue, Jun 5, 2018 at 1:31 PM, Nikolay Izhikov wrote:
> Vyacheslav,
>
> Let's create build plan on TC for this profile.
> Why
Guys, we had a private talk with Vyacheslav and Dmitriy Pavlov.
Here are its resulst:
1. I will create JCache1.1 build plan.
I will be able to run tests with Alex new profile enabled.
So, Alex can run and share with community tests results both for jcache 1.0 and
jcache 1.1.
2. Alex, please, cr
Ilya Kasnacheev created IGNITE-8700:
---
Summary: Support Uid/Pwd fields for authentication in DSN
connection strings
Key: IGNITE-8700
URL: https://issues.apache.org/jira/browse/IGNITE-8700
Project: Ig
Alex, please try to run this build plan for your branch
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11
В Вт, 05/06/2018 в 13:56 +0300, Nikolay Izhikov пишет:
> Guys, we had a private talk with Vyacheslav and Dmitriy Pavlov.
> Here are its resulst:
>
> 1. I
Ilya Kasnacheev created IGNITE-8701:
---
Summary: If Thin Client authentication is disabled on cluster,
JDBC Thin Driver disallows supplying of login/password
Key: IGNITE-8701
URL: https://issues.apache.org/jira/br
Github user devozerov closed the pull request at:
https://github.com/apache/ignite/pull/4129
---
Igniters,
Recently was optimized GridLongList serialization. [1]
I found that GridIntList and GridByteArrayList can be optimized as well.
We can reduce message size by sending only valuable part of the array:
public boolean writeTo(ByteBuffer buf, MessageWriter writer) {
...
writer.wr
Agree with Nikolay we should create build plan, and we can use this build
plan in developement branch.
Merge to master is not necessary before issue is ready.
вт, 5 июн. 2018 г. в 14:04, Nikolay Izhikov :
> Alex, please try to run this build plan for your branch
>
>
> https://ci.ignite.apache.or
Ilya Kasnacheev created IGNITE-8702:
---
Summary: Crash in ODBC driver under Informatica connection checker
Key: IGNITE-8702
URL: https://issues.apache.org/jira/browse/IGNITE-8702
Project: Ignite
Vladimir Ozerov created IGNITE-8703:
---
Summary: JDBC thin: drop support of versions older than 2.5.0
Key: IGNITE-8703
URL: https://issues.apache.org/jira/browse/IGNITE-8703
Project: Ignite
I
Hi Nikita,
I guess there is no significiant boost from this change, but I may be
wrong. Can we somehow do macrobenchmark with GridLongList changes?
Sincerely,
Dmitriy Pavlov
вт, 5 июн. 2018 г. в 14:21, Nikita Amelchev :
> Igniters,
>
> Recently was optimized GridLongList serialization. [1]
>
>
Alexander Menshikov created IGNITE-8704:
---
Summary: CacheManagerTest.getUnsafeTypedCacheRequest failed
Key: IGNITE-8704
URL: https://issues.apache.org/jira/browse/IGNITE-8704
Project: Ignite
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/4130
IGNITE-8685 Incorrect size for switch segment record
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-86
GitHub user SharplEr opened a pull request:
https://github.com/apache/ignite/pull/4131
ignite-8704 fixed
For [IGNITE-8704](https://issues.apache.org/jira/browse/IGNITE-8704)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SharplEr
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/4132
IGNITE-8703
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8703
Alternatively you can review and apply these
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4133
ignite-2.5.1-p6
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p6
Alternatively you can review and apply
Igniters,
I prepared a rather important patch [1] related to WAL.
In the current implementation, we calculation incorrect size for
SEGMENT_SWITCH record, it leads to stopping the iteration at the end of a
segment and iterator do not advance to the next segment.
[1] https://issues.apache.org/jira/
Alexander Menshikov created IGNITE-8705:
---
Summary: CacheMBStatisticsBeanTest.testClear failed
Key: IGNITE-8705
URL: https://issues.apache.org/jira/browse/IGNITE-8705
Project: Ignite
Iss
Thanks, Dmitriy, I'll take a look.
вт, 5 июн. 2018 г. в 15:24, Dmitriy Govorukhin :
> Igniters,
>
> I prepared a rather important patch [1] related to WAL.
> In the current implementation, we calculation incorrect size for
> SEGMENT_SWITCH record, it leads to stopping the iteration at the end of
Alexey Goncharuk created IGNITE-8706:
Summary:
IgnitePdsDataRegionMetricsTest#testMemoryUsageMultipleNodes fails in master
Key: IGNITE-8706
URL: https://issues.apache.org/jira/browse/IGNITE-8706
P
GitHub user SharplEr opened a pull request:
https://github.com/apache/ignite/pull/4134
IGNITE-8705: CacheMBStatisticsBeanTest.testClear failed
For [IGNITE-8705](https://issues.apache.org/jira/browse/IGNITE-8705)
You can merge this pull request into a Git repository by running:
Dmitriy Govorukhin created IGNITE-8707:
--
Summary: DataStorageMetrics.getTotalAllocatedSize metric does not
account reserved partition page header.
Key: IGNITE-8707
URL: https://issues.apache.org/jira/browse/I
Alexander Menshikov created IGNITE-8708:
---
Summary: CacheManagerTest.close_cachesEmpty failed
Key: IGNITE-8708
URL: https://issues.apache.org/jira/browse/IGNITE-8708
Project: Ignite
Issu
GitHub user SharplEr opened a pull request:
https://github.com/apache/ignite/pull/4135
ignite-8708: CacheManagerTest.close_cachesEmpty failed
For [ignite-8708](https://issues.apache.org/jira/browse/IGNITE-8708)
You can merge this pull request into a Git repository by running:
$
Hi,
Welcome to the Ignite community!
To subscribe to dev list you can send email to
dev-subscr...@ignite.apache.org
See also https://ignite.apache.org/community/resources.html#mail-lists
Sincerely,
Dmitriy Pavlov
пт, 1 июн. 2018 г. в 23:48, The Malted Loaf :
> subscribe!
>
>
Alexander Menshikov created IGNITE-8709:
---
Summary: CacheMBStatisticsBeanTest.testPutIfAbsent failed
Key: IGNITE-8709
URL: https://issues.apache.org/jira/browse/IGNITE-8709
Project: Ignite
GitHub user SharplEr opened a pull request:
https://github.com/apache/ignite/pull/4136
ignite-8709 CacheMBStatisticsBeanTest.testPutIfAbsent failed
For [ignite-8709](https://issues.apache.org/jira/browse/IGNITE-8709)
You can merge this pull request into a Git repository by running:
Vladislav Pyatkov created IGNITE-8710:
-
Summary: Applying WAL works long time or fail at all, when *.wal
files been removed
Key: IGNITE-8710
URL: https://issues.apache.org/jira/browse/IGNITE-8710
Sergey Chugunov created IGNITE-8711:
---
Summary:
IgniteStandByClientReconnectToNewClusterTest#testInactiveClientReconnectToActiveCluster
fails in master
Key: IGNITE-8711
URL: https://issues.apache.org/jira/browse
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/4137
IGNITE-8701
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8701
Alternatively you can review and apply these
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2991
---
Github user voipp closed the pull request at:
https://github.com/apache/ignite/pull/4023
---
GitHub user ascherbakoff opened a pull request:
https://github.com/apache/ignite/pull/4138
IGNITE-7339 RENTING partition is not evicted after restore from storage
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ig
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4137
---
Pavel Pereslegin created IGNITE-8712:
Summary:
IgniteDataStructureUniqueNameTest#testUniqueNameMultithreaded fails sometimes
in master.
Key: IGNITE-8712
URL: https://issues.apache.org/jira/browse/IGNITE-8712
Hello Igniters!
I have found some confusing behavior of atomic partitioned cache with
`PRIMARY_SYNC` write synchronization mode.
Node with a primary partition sends a message to remote nodes with backup
partitions via `GridDhtAtomicAbstractUpdateFuture#sendDhtRequests`.
If during of sending o
Fix formatting
Hello Igniters!
I have found some confusing behavior of atomic partitioned cache with
`PRIMARY_SYNC` write synchronization mode.
Node with a primary partition sends a message to remote nodes with backup
partitions via `GridDhtAtomicAbstractUpdateFuture#sendDhtRequests`.
If during o
GitHub user xtern opened a pull request:
https://github.com/apache/ignite/pull/4139
IGNITE-8712 Should wait until continuous query notifies all nodes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xtern/ignite IGNITE-8712
Alte
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4073
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4069
---
Denis,
Seem that you right, it is a problem.
I guess in this case primary node should send CachePartialUpdateException
to near node.
On Tue, Jun 5, 2018 at 6:13 PM, Denis Garus wrote:
> Fix formatting
>
> Hello Igniters!
>
> I have found some confusing behavior of atomic partitioned cache with
GitHub user voipp opened a pull request:
https://github.com/apache/ignite/pull/4140
IGNITE-955 #draft
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/voipp/ignite IGNITE-955
Alternatively you can review and apply these changes a
Dmitry P., Anton V.,
I made some changes and updated the ticket. Also as was asked I tried to
squash the commits into one but looks like I screwed up everything and the
PR now looks completely terrible. Since I'm not an advanced git user, could
you please check the PR and let me know if anything co
It was discussed here.
Dmitry,
There are other cases that can result in inconsistent state of Atomic cache
with 2 or more backups.
1. For PRIMARY_SYNC. Primary sends requests to all backups and respond to
near and then one of backup update fails.
Will primary retry update operation? I doubt.
2. For all sync modes
Igniters,
Recently we've stumbled across the following two tickets [1], [2] which
seem to be very critical from the usability and stability points of view.
The [1] results in clients not being able to update persistence-enabled
clusters unless the client configuration is identical to the server
co
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4124
---
Harendra Rai created IGNITE-8713:
Summary: Security vulnerabilities in
spring-data-commons-1.13.1.RELEASE.jar
Key: IGNITE-8713
URL: https://issues.apache.org/jira/browse/IGNITE-8713
Project: Ignite
Here -
http://apache-ignite-developers.2346864.n4.nabble.com/Issues-with-forceServerMode-on-clients-and-unclear-contract-of-isClient-isClientMode-methods-td31152.html
:)
On Tue, Jun 5, 2018 at 7:38 PM, Eduard Shangareev <
eduard.shangar...@gmail.com> wrote:
> It was discussed here.
>
Alexander Menshikov created IGNITE-8714:
---
Summary: CacheEntryEvent.getOldValue should be available
Key: IGNITE-8714
URL: https://issues.apache.org/jira/browse/IGNITE-8714
Project: Ignite
I agree in general. First issue is severe usability issue, while second
one may fail crash recovery and cause data loss. This makes AI 2.5 not
recommended for using.
Best Regards,
Ivan Rakov
On 05.06.2018 19:39, Alexey Goncharuk wrote:
Igniters,
Recently we've stumbled across the following t
Alexander Menshikov created IGNITE-8715:
---
Summary: Problems with Closeable objects from Factory
Key: IGNITE-8715
URL: https://issues.apache.org/jira/browse/IGNITE-8715
Project: Ignite
I
Okay. There are tests results:
https://ci.ignite.apache.org/viewLog.html?buildId=1361493&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JCacheTck11
It's the same as locally.
Also, I have created sub-tasks for all problems we have:
1) CacheManagerTest.getUnsafeTypedCacheRequest failed.
https
I'd like to add that first issue [1] has a follow-up fix [2]. It should
be backported along with the first fix.
[1] - https://issues.apache.org/jira/browse/IGNITE-8476
[2] - https://issues.apache.org/jira/browse/IGNITE-8682
Best Regards,
Ivan Rakov
On 05.06.2018 20:57, Ivan Rakov wrote:
I agre
Petr,
Were you ever able to successfully start an Ignite node from Ubuntu on
Windows 10?
It looks like a node startup hangs for me. Here is the message I am getting
when bringing up a node in verbose mode:
*[18:24:27,778][WARNING][main][TcpDiscoverySpi] Node has not been connected
> to topology
Alex,
I think it is OK to break TCK 1.0.1 tests in favor of TCK 1.1. Once we
finish the migration, I would remove the TCK 1.0.1 test suite altogether.
D.
On Tue, Jun 5, 2018 at 11:13 AM, Александр Меньшиков
wrote:
> Okay. There are tests results:
>
> https://ci.ignite.apache.org/viewLog.html?b
Dmitriy,
I will check soon and see what can be done to overcome this.
Yet, I still doubt that running Apache Ignite packed in DEB under Windows 10
WSL Ubuntu is a plausible user case.
To be honest, I doubt that our packages are being downloaded and installed at
all...
> On 5 Jun 2018, at 2
Hi
For Windows users we should provide Windows installer (.exe or .msi) that
set up and install AI as service. But that task requires significant
efforts and makes sense to start in that way after stabilization DEB/RPM
architecture
On Tue, Jun 5, 2018 at 10:12 PM, Petr Ivanov wrote:
> Dmitriy,
Agree, I see zero benefits of being compliant with both specification
versions. Let’s just focus on the latest one.
Denis
On Tuesday, June 5, 2018, Dmitriy Setrakyan wrote:
> Alex,
>
> I think it is OK to break TCK 1.0.1 tests in favor of TCK 1.1. Once we
> finish the migration, I would remove
On Tue, Jun 5, 2018 at 1:54 PM, Sergey Kozlov wrote:
> Hi
>
> For Windows users we should provide Windows installer (.exe or .msi) that
> set up and install AI as service. But that task requires significant
> efforts and makes sense to start in that way after stabilization DEB/RPM
> architecture
On Tue, Jun 5, 2018 at 12:12 PM, Petr Ivanov wrote:
> Dmitriy,
>
>
> I will check soon and see what can be done to overcome this.
>
Thanks! Looking forward to your feedback.
>
> Yet, I still doubt that running Apache Ignite packed in DEB under Windows
> 10 WSL Ubuntu is a plausible user case.
Pavel Vinokurov created IGNITE-8716:
---
Summary: SQL query and WITH caluse produces syntax error
Key: IGNITE-8716
URL: https://issues.apache.org/jira/browse/IGNITE-8716
Project: Ignite
Issue
74 matches
Mail list logo
