Dmitriy, no problem, I'll rename it.
Semyon
On Tue, Jan 9, 2018 at 11:20 PM, Dmitriy Setrakyan
wrote:
> Thanks Semyon!
>
> I have a naming nitpick. Can we rename Problem to Failure, e.g.
> CommunicationProblemResolver to CommunicationFailureResolver?
>
> D.
>
> On Tue, Jan 9, 2018 at 3:39 AM, S
Hi Andrey,
Could you please share detail of this API mismatch? AFAIK, the main
guarantee we need for disco SPI is total message ordering. Zookeeper
provides this guarantee. Moreover, Zookeeper is proven to be correct and
reliable coordinator service by many users and Jepsen tests, as opposed to
va
Hi Ignor,
Would you please help review my patch to see if it is ok. I'm hoping to
include this in 2.4.
Thanks
Jason
-Original Message-
From: Denis Magda [mailto:dma...@apache.org]
Sent: Thursday, December 21, 2017 2:15 PM
To: dev@ignite.apache.org; Igor Rudyak
Subject: Re: IGNITE-6853
Single Number is easier to manage than prefix + number
ср, 10 янв. 2018 г. в 10:13, Sergey Kosarev :
> Hi,
> Why Event ID should be a number?
> Maybe better to split main subsystems by prefixes?
> something like
> Networking: IGN-NET
> Persistence: IGN-PERS
> etc.
>
> Sergey Kosarev
>
> > On 10
Hi,
Why Event ID should be a number?
Maybe better to split main subsystems by prefixes?
something like
Networking: IGN-NET
Persistence: IGN-PERS
etc.
Sergey Kosarev
> On 10 Jan 2018, at 03:49, Denis Magda wrote:
>
> Igniters,
>
> As a preface, Alexey Kukushkin laid out an insightful and pr
Andrey — double checked your solution and it works now. Guess there was some
merge error first time.
Sorry for misleading.
So, there is working solution for Java 9 build and I’d like to save this
configuration in ignite-6730 (making IGNITE-7144 and IGNITE-6736 to become
subtasks in the process)
+1, better t I think we need more ch bigger ranges for subsystems. E.g.,
10K reserved for SQL would be enough. Not because there are so many real
errors, but because we would need subgroups.
ср, 10 янв. 2018 г. в 6:49, Alexey Kuznetsov :
> Denis,
>
> I think it will be very useful.
>
> P.S. Minor
Denis,
I think it will be very useful.
P.S. Minor note, I think ranges should be _000 - _999?
On Wed, Jan 10, 2018 at 7:49 AM, Denis Magda wrote:
> Igniters,
>
> As a preface, Alexey Kukushkin laid out an insightful and profound
> explanation on what’s wrong with Ignite logs from a DevOps pe
Igniters,
As a preface, Alexey Kukushkin laid out an insightful and profound explanation
on what’s wrong with Ignite logs from a DevOps perspective, how the community
can easily tackle the gaps and how our efforts will be payed off if we take his
advice in consideration:
http://apache-ignite-d
Andrey Kornev created IGNITE-7368:
-
Summary: IgniteCache.getAll() throws high volume of
GridDhtInvalidPartitionException if on-heap is enabled
Key: IGNITE-7368
URL: https://issues.apache.org/jira/browse/IGNITE-736
GitHub user techbysample opened a pull request:
https://github.com/apache/ignite/pull/3347
IGNITE-6899: Adding GA Grid to Apache Ignite ML module
IGNITE-6899: Adding GA Grid to Apache Ignite ML module
You can merge this pull request into a Git repository by running:
$ git pull
+ dev list
Igniters, Pavel,
I think we need to bring support for key-value transactions to one of the
future versions. As far as I understand, a server node, a thin client will be
connected to, will be the transaction coordinator and the client will simply
offloading everything to it. What do
Thanks Semyon!
I have a naming nitpick. Can we rename Problem to Failure, e.g.
CommunicationProblemResolver to CommunicationFailureResolver?
D.
On Tue, Jan 9, 2018 at 3:39 AM, Semyon Boikov wrote:
> Hi all,
>
> Currently I'm working on implementation of DiscoverySpi based on Apache
> ZooKeeper
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3345
---
Github user sk0x50 closed the pull request at:
https://github.com/apache/ignite/pull/3331
---
Semyon,
Not to discourage you or anything, just a interesting fact from recent history.
I vaguely remember already trying to implement DiscoverySpi on top of Zookeeper
back in 2012. After a few failed attempts and a lot of help from Zookeeper's
original developers (Flavio Junqueira and Ben Reed
Hi Petr!
Could you please clarify what is wrong with fix proposed in IGNITE-6736,
and what is supposed to be a replacement for monitorEnter/monitorExit now?
2018-01-09 19:08 GMT+03:00 Petr Ivanov :
> Hi all.
>
>
> After some thorough research and with help of fellow igniters, I’ve
> managed to p
Artem Malykh created IGNITE-7367:
Summary: Flickering minMax test in SparseDistributedMatrixTest
Key: IGNITE-7367
URL: https://issues.apache.org/jira/browse/IGNITE-7367
Project: Ignite
Issue
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/3346
IGNITE-7284: Introduce DEV_ONLY marker to IgniteLogger
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7284
Alt
GitHub user artemmalykh opened a pull request:
https://github.com/apache/ignite/pull/3345
Ignite return auth 7322 6783 step 22
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-return-auth-7322-6783-s
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/3344
ignite-7365 Switch segment rollover hanging is fixed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-7365
Alternat
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3336
---
GitHub user artemmalykh opened a pull request:
https://github.com/apache/ignite/pull/3343
IGNITE-7322: Return authorship step 2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-return-auth-7322-6783-
Ilya Kasnacheev created IGNITE-7366:
---
Summary: Affinity assignment exception in service processor during
multiple nodes join
Key: IGNITE-7366
URL: https://issues.apache.org/jira/browse/IGNITE-7366
P
GitHub user dolphin1414 opened a pull request:
https://github.com/apache/ignite/pull/3342
IGNITE-6772: SQL exception messages made more informative.
SQL exception messages made more informative.
You can merge this pull request into a Git repository by running:
$ git pull https:
Andrey Gura created IGNITE-7365:
---
Summary: File channel associated with WAL can be closed by
interruption
Key: IGNITE-7365
URL: https://issues.apache.org/jira/browse/IGNITE-7365
Project: Ignite
Hi all.
After some thorough research and with help of fellow igniters, I’ve managed to
prepare more or less stable Java 9 build configuration of Apache Ignite.
Here are changes to make it work:
- Java 8 profiles and build process revision, made in IGNITE-7203;
- Java 9 maven profile prepared
Andrey Gura created IGNITE-7364:
---
Summary: [Test failed]
IgnitePdsThreadInterruptionTest.testInterruptsOnWALWrite fails or hangs
Key: IGNITE-7364
URL: https://issues.apache.org/jira/browse/IGNITE-7364
P
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/3341
IGNITE-7277: override equals() & hashCode() methods for JdbcTableMetaâ¦
⦠to prevent tables duplication at the tables metadata result set.
You can merge this pull request into a Git rep
Ilya Kasnacheev created IGNITE-7363:
---
Summary: Inconsistent millis in java.util.Date when retrieved in
SELECT query
Key: IGNITE-7363
URL: https://issues.apache.org/jira/browse/IGNITE-7363
Project: I
Igor Sapego created IGNITE-7362:
---
Summary: ODBC: Third party libraries truncate any inserted varlen
data to ColumnSize
Key: IGNITE-7362
URL: https://issues.apache.org/jira/browse/IGNITE-7362
Project: Ig
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/3340
ignite-2.4.1 reconnect fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-2.4.1-merge-master-recFix
Alterna
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/3339
IGNITE-7335: add test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7335
Alternatively you can review
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/3338
---
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/3338
IGNITE-7335 DatabaseMetaData getTables error
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7335
Alte
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/3312
---
Github user tledkov-gridgain closed the pull request at:
https://github.com/apache/ignite/pull/3322
---
GitHub user tledkov-gridgain opened a pull request:
https://github.com/apache/ignite/pull/3337
IGNITE-7343 Add guard to prevent concurrent usage the JDBC thin connection
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/a
Evgenii Zhuravlev created IGNITE-7361:
-
Summary: HA: NPE in HadoopJobTracker.jobMetaCache
Key: IGNITE-7361
URL: https://issues.apache.org/jira/browse/IGNITE-7361
Project: Ignite
Issue Typ
GitHub user artemmalykh opened a pull request:
https://github.com/apache/ignite/pull/3336
IGNITE-7322: Return authorship of 7322 and 6783
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-return-auth-
Alex Volkov created IGNITE-7360:
---
Summary: SQL: incorrect date/time values could be inserted
Key: IGNITE-7360
URL: https://issues.apache.org/jira/browse/IGNITE-7360
Project: Ignite
Issue Type:
Hi all,
Currently I'm working on implementation of DiscoverySpi based on Apache
ZooKeeper (ZookeeperDiscoverySpi) and want to share results of this work.
In very large clusters (>1000 nodes) current default implementation of
DiscoverySpi - TcpDiscoverySpi - has some significant drawbacks:
- TcpDi
Sergey Kalashnikov created IGNITE-7359:
--
Summary: SQL: DDL synchronization with query and cache API
operations
Key: IGNITE-7359
URL: https://issues.apache.org/jira/browse/IGNITE-7359
Project: Ign
GitHub user anton-vinogradov opened a pull request:
https://github.com/apache/ignite/pull/3335
Ignite 7003 1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7003-1
Alternatively you can review and a
Github user slukyano closed the pull request at:
https://github.com/apache/ignite/pull/3320
---
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/3334
Ignite 7217 2.1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7217-2.1
Alternatively you can review and apply
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/
IGNITE-7318 .NET: Move SQL examples to Sql namespace
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-7318
Alternativ
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/3332
Ignite 7217 2.3
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7217-2.3
Alternatively you can review and apply
Github user slukyano closed the pull request at:
https://github.com/apache/ignite/pull/3301
---
49 matches
Mail list logo
