Ilya Borisov created IGNITE-8096:
Summary: Web console: add ability to clone cluster configuration
entities
Key: IGNITE-8096
URL: https://issues.apache.org/jira/browse/IGNITE-8096
Project: Ignite
GitHub user alex-plekhanov opened a pull request:
https://github.com/apache/ignite/pull/3729
IGNITE-8069 IgniteOutOfMemoryException should be handled accordingly â¦
â¦to provided failure handler
You can merge this pull request into a Git repository by running:
$ git pull http
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3685
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3720
---
Vladimir Ozerov created IGNITE-8097:
---
Summary: Java thin client: throw handshake exception on connect
phase
Key: IGNITE-8097
URL: https://issues.apache.org/jira/browse/IGNITE-8097
Project: Ignite
Andrey Aleksandrov created IGNITE-8098:
--
Summary: Getting affinity for topology version earlier than
affinity is calculated because of data race
Key: IGNITE-8098
URL: https://issues.apache.org/jira/browse/IGN
Pavel Konstantinov created IGNITE-8099:
--
Summary: Web console: wrong editing behavior in case of incorrect
field value
Key: IGNITE-8099
URL: https://issues.apache.org/jira/browse/IGNITE-8099
Proj
Cross posting to dev.
Vladimir Ozerov, can you please take a look at NPE from query processor
(see below - GridQueryProcessor.typeByValue(GridQueryProcessor.java:1901))?
--Yakov
2018-03-29 0:19 GMT+03:00 smurphy :
> Code works in Ignite 2.1.0. Upgrading to 2.4.0 produces the stack trace
> below
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3565
---
Guys, especially Vladimir Ozerov, Yakov Zhanov, Dmitriy Setrakyan,
While the technical side of the change is being reviewed, I would also ask
you to pay attention to the public API changes here.
--AG
2018-03-21 23:43 GMT+03:00 Pavel Tupitsyn :
> Hi Alexei,
>
> > Pavel Tupitsyn, could you lend
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/3730
ignite-zk latest master merged with ZooKeeper discovery impl branch
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apach
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3702
---
Pavel Kuznetsov created IGNITE-8100:
---
Summary: jdbc getSchemas method could miss schemas for not started
remote caches
Key: IGNITE-8100
URL: https://issues.apache.org/jira/browse/IGNITE-8100
Project
Dmitriy Sorokin created IGNITE-8101:
---
Summary: Ability to terminate system workers by JMX for test
purposes
Key: IGNITE-8101
URL: https://issues.apache.org/jira/browse/IGNITE-8101
Project: Ignite
Dmitriy Pavlov created IGNITE-8102:
--
Summary:
IgnitePdsCorruptedStoreTest.testNodeInvalidatedWhenPersistenceIsCorrupted
failed in Direct IO 2 suite
Key: IGNITE-8102
URL: https://issues.apache.org/jira/browse/IGN
Hi Igniters,
A number of .NET tests failed, it seems it requied to be updated/fixed first
Ignite Platform .NET Core Linux [ tests 2 ]
dll: TransactionsParityTest.TestTransactions (master fail rate 0,0%)
dll: CachePartitionedTest.TestTransactionScopeMultiCache(True)
(master fail rate
Vyacheslav,
Service deployment design, based on replicated utility cache has proven to
be unstable and deadlock-prone.
You can find a list of JIRA issues, connected to it, in my previous letter.
The intention behind it is similar to the binary metadata redesign, that
happened in the following tic
Alexander Belyak created IGNITE-8103:
Summary: Node with BLT is not allowed to join cluster without one
Key: IGNITE-8103
URL: https://issues.apache.org/jira/browse/IGNITE-8103
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3721
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3660
---
Ivan Fedotov created IGNITE-8104:
Summary: Proper toString() implementation for IgniteConfiguration
properties
Key: IGNITE-8104
URL: https://issues.apache.org/jira/browse/IGNITE-8104
Project: Ignite
Alexander Belyak created IGNITE-8105:
Summary: Close() while auto activate
Key: IGNITE-8105
URL: https://issues.apache.org/jira/browse/IGNITE-8105
Project: Ignite
Issue Type: Bug
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/2854
---
Crossposting to dev.
Guys,
User use Ignite native persistence with CacheStore configured.
Seems, changing CacheStore requires cache recreation in his case to changes
can be applied.
Does anybody has idea how it can be fixed?
Do we allow to rewrite cache config in native store if it has minor cha
Ilya Kasnacheev created IGNITE-8106:
---
Summary: In control.sh -active, exception will be eaten and not
displayed
Key: IGNITE-8106
URL: https://issues.apache.org/jira/browse/IGNITE-8106
Project: Ignit
Ilya Kasnacheev created IGNITE-8107:
---
Summary: Drop cache with SQL table, recreate table on a different
cache - cluster fails to activate
Key: IGNITE-8107
URL: https://issues.apache.org/jira/browse/IGNITE-8107
Github user andrey-kuznetsov closed the pull request at:
https://github.com/apache/ignite/pull/2749
---
Alexey Popov created IGNITE-8108:
Summary: .NET: Fix flaky
EntityFrameworkCacheInitializationTest.TestConfigurationAndStartup
Key: IGNITE-8108
URL: https://issues.apache.org/jira/browse/IGNITE-8108
Pr
> On 29 Mar 2018, at 12:32, Max Shonichev wrote:
>
>
>
> 1. About packaging/package.sh
>
> 1.1. I personally dislike the use of bashism, e.g. like reserved keywords,
> double '[[', double '((', but that's ok
> for targeted distro (RHEL/Centos). The only requirement is please add more
> comme
GitHub user apopovgg opened a pull request:
https://github.com/apache/ignite/pull/3731
IGNITE-8108: .NET: Fix flaky EntityFrameworkCacheInitializationTest.Tâ¦
â¦estConfigurationAndStartup
You can merge this pull request into a Git repository by running:
$ git pull https://git
Sergey Chugunov created IGNITE-8109:
---
Summary:
IgniteCacheEntryListenerAtomicTest#testConcurrentRegisterDeregister timeouts
when ZooKeeper Discovery is used
Key: IGNITE-8109
URL: https://issues.apache.org/jira/
Vyacheslav Koptilin created IGNITE-8110:
---
Summary: GridCacheWriteBehindStore.Flusher thread uses the wrong
transformation from milliseconds to nanoseconds.
Key: IGNITE-8110
URL: https://issues.apache.org/jir
Ivan Rakov created IGNITE-8111:
--
Summary: Add extra validation for WAL segment size
Key: IGNITE-8111
URL: https://issues.apache.org/jira/browse/IGNITE-8111
Project: Ignite
Issue Type: Improvemen
According recent conversation 'Code Inspection' I would like to bump up
this thread too.
Igniters, who can advice if coverity has integration/ability to be run on
TeamCity? Who can help to proof, that it is possible to be executed using
maven.
вт, 19 сент. 2017 г. в 14:27, Yakov Zhdanov :
> Bas,
GitHub user x-kreator opened a pull request:
https://github.com/apache/ignite/pull/3732
Ignite 8071
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/x-kreator/ignite ignite-8071
Alternatively you can review and apply these change
Guys,
I've looked at IGNITE-6827 implementation and have comment. I think
that rollbackOnTopologyChangeTimeout parameter isn't related with
implemented functionality. It's responsibility of PME to rollback
transactions that blocks exchange, so rollbackOnTopologyChangeTimeout
should be configured f
Hello!
Let me share my idea of how this shoud work. Splitting package into
sub-packages should be dependency-driven.
It means that all Ignite modules without dependencies or with small
dependencies (such as ignite-log4j) should be included in ignite-core. It
doesn't make sense to make a zillion R
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3705
---
Vyacheslav Koptilin created IGNITE-8112:
---
Summary: DirectIO artifact is not published in the maven repository
Key: IGNITE-8112
URL: https://issues.apache.org/jira/browse/IGNITE-8112
Project: Igni
Sergey Chugunov created IGNITE-8113:
---
Summary: ZookeeperClientTest#testReconnect3, testReconnect4 fail
on TC
Key: IGNITE-8113
URL: https://issues.apache.org/jira/browse/IGNITE-8113
Project: Ignite
Eduard Shangareev created IGNITE-8114:
-
Summary: Add fail recovery mechanism to tracking pages
Key: IGNITE-8114
URL: https://issues.apache.org/jira/browse/IGNITE-8114
Project: Ignite
Issu
GitHub user sk0x50 opened a pull request:
https://github.com/apache/ignite/pull/3733
ignite-8112: updated build configuration (direct-io artifact should be
published in maven repository)
You can merge this pull request into a Git repository by running:
$ git pull https://gith
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/3734
IGNITE-8114 Add fail recovery mechanism to tracking pages
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8114
Alexey Goncharuk created IGNITE-8115:
Summary: Add a warning on local node startup if the node is not in
Baseline
Key: IGNITE-8115
URL: https://issues.apache.org/jira/browse/IGNITE-8115
Project: I
Igniters,
We've bumped into situation when using extremely small (<10 pages) WAL
segment size caused unobvious errors and assertions:
https://issues.apache.org/jira/browse/IGNITE-8111
Let's reach a consensus on which value of WAL segment size should be
considered as minimum. I tried tests with
I have no objections on 512kb
пн, 2 апр. 2018 г. в 19:17, Ivan Rakov :
> Igniters,
>
> We've bumped into situation when using extremely small (<10 pages) WAL
> segment size caused unobvious errors and assertions:
> https://issues.apache.org/jira/browse/IGNITE-8111
> Let's reach a consensus on whi
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3021
---
Ivan,
Will his value be used as a default one as well or only is a possible
minimum? As for the defaults, I see that Postgres and Cassandra set 16mb as
a default segment size:
https://www.postgresql.org/docs/9.1/static/wal-configuration.html
https://www.enterprisedb.com/docs/en/10.0/EPAS_Guide_v10
Denis,
The topic is about a possible minimum only.
Our default for WAL segment size is 64mb and we are not going to change
it (at least under this ticket).
Best Regards,
Ivan Rakov
On 02.04.2018 19:51, Denis Magda wrote:
Ivan,
Will his value be used as a default one as well or only is a pos
+1 for this from an Ignite professional services consultant. The more we can do
to protect users from non-sensical configuration settings, the better. I’ve
seen a lot of them in the field (and not just related to WAL segment size). As
Scott McNealy of Sun fame once said, “there’s nothing dumber
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/3735
IGNITE-8106 Collect suppressed exceptions from causes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8106
Alter
Eduard Shangareev created IGNITE-8116:
-
Summary: Historic WAL rebalance fails
Key: IGNITE-8116
URL: https://issues.apache.org/jira/browse/IGNITE-8116
Project: Ignite
Issue Type: Bug
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3646
---
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/3736
Ignite 2.4.2 master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.2-master
Alternatively you can review
I looked into the ticket and do not understand this property
name: RollbackOnTopologyChangeTimeout
I think what we need to configure is a forceful kill of transactions in
case of partition map exchange, right? In that case, the timeout should be
configured for PME, not transactions. The property n
Rick Lin created IGNITE-8117:
Summary: Slow Ignite Cache with multi-nodes
Key: IGNITE-8117
URL: https://issues.apache.org/jira/browse/IGNITE-8117
Project: Ignite
Issue Type: Improvement
GitHub user gromtech opened a pull request:
https://github.com/apache/ignite/pull/3737
IGNITE-7944 Disconnected client node tries to send JOB_CANCEL message
* Skip sending messages if client disconnected.
* Throw IgniteCheckedException if a client node is disconnected and
commun
Folks,
Any other thoughts on this? Should we create tickets for compute support if
there are no objections?
-Val
On Thu, Mar 22, 2018 at 4:27 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> I agree that compute and services functionality is important for thin
> client. It does
Pavel Konstantinov created IGNITE-8118:
--
Summary: sqlline.bat throws NPE under PowerShell
Key: IGNITE-8118
URL: https://issues.apache.org/jira/browse/IGNITE-8118
Project: Ignite
Issue Ty
Val, my preference would be not to have compute functionality on thin clients,
as it would introduce extra security risk.
Any particular reason why you are asking for this feature?
D.
On Apr 2, 2018, 8:47 PM, at 8:47 PM, Valentin Kulichenko
wrote:
>Folks,
>
>Any other thoughts on this? Shou
Alexander Belyak created IGNITE-8119:
Summary: NPE on clear DB and unclear WAL/WAL_ARCHIVE
Key: IGNITE-8119
URL: https://issues.apache.org/jira/browse/IGNITE-8119
Project: Ignite
Issue Ty
61 matches
Mail list logo