Ilya Borisov created IGNITE-8805:
Summary: Web console: use TypeScript for E2E tests
Key: IGNITE-8805
URL: https://issues.apache.org/jira/browse/IGNITE-8805
Project: Ignite
Issue Type:
Dmitriy, great job! Very important fix to a very bad problem in the product
that could cause data consistency issue.
Will it be included into 2.6, or will we have to wait for 2.7?
D.
On Thu, Jun 14, 2018 at 6:53 AM, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com> wrote:
> Folks,
>
> I fixed
Denis Magda created IGNITE-8804:
---
Summary: Windows WSL configuration has to be added to Ignite
configs
Key: IGNITE-8804
URL: https://issues.apache.org/jira/browse/IGNITE-8804
Project: Ignite
In continuation to my previous email about INFO level log output, we also
have a big problem with QUIET log mode. Here is an example of a single node
output after another node joined and left 3 times:
[22:50:23] Ignite node started OK (id=931fcf60)
> [22:50:23] Topology snapshot [ver=4,
Dmitriy Setrakyan created IGNITE-8803:
-
Summary: Need to fix Ignite QUIET log output
Key: IGNITE-8803
URL: https://issues.apache.org/jira/browse/IGNITE-8803
Project: Ignite
Issue Type:
Dmitriy Setrakyan created IGNITE-8802:
-
Summary: Need to fix Ignite INFO output
Key: IGNITE-8802
URL: https://issues.apache.org/jira/browse/IGNITE-8802
Project: Ignite
Issue Type:
Guys, are you targeting this for the next big Ignite release? Should be in
3 m from now.
--
Denis
On Thu, Jun 14, 2018 at 2:58 AM Anton Vinogradov wrote:
> Corrected IEP URL:
>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-21%3A+JCache+1.1+support
>
> чт, 14 июн. 2018 г. в 12:48,
GitHub user BiryukovVA opened a pull request:
https://github.com/apache/ignite/pull/4192
IGNITE-8182: TC.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/BiryukovVA/ignite IGNITE-8182
Alternatively you can review and apply
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4159
---
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/4183
---
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/4171
---
Ryabov Dmitrii created IGNITE-8801:
--
Summary: Change default behaviour of atomic operations inside
transactions
Key: IGNITE-8801
URL: https://issues.apache.org/jira/browse/IGNITE-8801
Project:
Igniters,
I found 2 methods,
1. PageStore.pageOffset(long pageId) - it unused, seem that old artifact.
2. IgnitePageStoreManager.pagesAllocated(int grpId) - used only in test,
seem that same problem can be solved with IgnitePageStoreManager.pages(grpId,
partId).
I suggest, remove these methods
GitHub user mcherkasov opened a pull request:
https://github.com/apache/ignite/pull/4191
IGNITE-8799: Web agent hides connection exceptions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/4190
IGNITE-8800
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8800
Alternatively you can review and apply these
Vladimir Ozerov created IGNITE-8800:
---
Summary: Binary: add type name to an error when schema cannot be
resolved
Key: IGNITE-8800
URL: https://issues.apache.org/jira/browse/IGNITE-8800
Project:
Mikhail Cherkasov created IGNITE-8799:
-
Summary: Web agent hides connection exceptions
Key: IGNITE-8799
URL: https://issues.apache.org/jira/browse/IGNITE-8799
Project: Ignite
Issue Type:
Alexey Goncharuk created IGNITE-8797:
Summary: Error during writeCheckpointEntry is not passed to
failure handler during checkpoint finish
Key: IGNITE-8797
URL:
Vyacheslav Koptilin created IGNITE-8796:
---
Summary: Client node is terminated by the Failure handler in case
of dynamic cache start failed on that client node.
Key: IGNITE-8796
URL:
Ok, I see, this is what I was trying to understand, and this is an
important note I think:
* We should request AffinityFunction for each particular cache and only
enable this functionality for known functions
* Make sure that known server-side functions never change their behavior
Thanks
On
Github user voipp closed the pull request at:
https://github.com/apache/ignite/pull/4189
---
Yury Babak created IGNITE-8795:
--
Summary: Add ability to start and maintain TensorFlow cluster on
top of Apache Ignite
Key: IGNITE-8795
URL: https://issues.apache.org/jira/browse/IGNITE-8795
Project:
Igor Sapego created IGNITE-8794:
---
Summary: CPP Thin: Implement Best Effort Affinity
Key: IGNITE-8794
URL: https://issues.apache.org/jira/browse/IGNITE-8794
Project: Ignite
Issue Type: New
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4156
---
Pavel Kovalenko created IGNITE-8793:
---
Summary: Introduce metrics for File I/O operations to monitor disk
performance
Key: IGNITE-8793
URL: https://issues.apache.org/jira/browse/IGNITE-8793
Project:
Vladimir is right,
As far as I know, most users use affinity functions provided by Ignite.
So we could optimize for the default case and, in future, optionally,
let user implement their own AffinityFunction for thin clients.
Best Regards,
Igor
On Thu, Jun 14, 2018 at 3:06 PM Vladimir Ozerov
GitHub user voipp opened a pull request:
https://github.com/apache/ignite/pull/4189
#rerun test 200 times
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/voipp/ignite IGNITE-5971
Alternatively you can review and apply these
Pavel,
The idea here is that optimization will be applicable only for well-known
affinity functions. E.g., we know that for rendezvous affinity, partition
is "hash(key) % partitions". This is all we need to make default affinity
work.
On Thu, Jun 14, 2018 at 11:41 AM, Pavel Tupitsyn
wrote:
>
Yury Babak created IGNITE-8792:
--
Summary: Introduction of TensorFlow integration module
Key: IGNITE-8792
URL: https://issues.apache.org/jira/browse/IGNITE-8792
Project: Ignite
Issue Type: New
Github user xtern closed the pull request at:
https://github.com/apache/ignite/pull/4187
---
Pavel Kovalenko created IGNITE-8791:
---
Summary:
IgnitePdsTxCacheRebalancingTest.testTopologyChangesWithConstantLoad fails on TC
Key: IGNITE-8791
URL: https://issues.apache.org/jira/browse/IGNITE-8791
Ok, go #1. I'll create ticket for defaults change and make appropriate
changes in current PR with link to new ticket.
2018-06-14 10:56 GMT+03:00 Dmitry Karachentsev :
> I would vote for 1 or 3 (this I like more), but not 2 as such breaking
> change involves more pain to our users. Let it be in
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4139
---
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/4188
IGNITE-8761
WAL fsync at rollover should be asynchronous in LOG_ONLY and BACKGROUND
modes
You can merge this pull request into a Git repository by running:
$ git pull
Alexey Goncharuk created IGNITE-8790:
Summary: JVM crash during memory recovery
Key: IGNITE-8790
URL: https://issues.apache.org/jira/browse/IGNITE-8790
Project: Ignite
Issue Type: Bug
GitHub user xtern opened a pull request:
https://github.com/apache/ignite/pull/4187
Flaky tests TC run.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xtern/ignite IGNITE-8712-TC
Alternatively you can review and apply these
Corrected IEP URL:
https://cwiki.apache.org/confluence/display/IGNITE/IEP-21%3A+JCache+1.1+support
чт, 14 июн. 2018 г. в 12:48, Александр Меньшиков :
> Igniters,
>
> I've prepared IEP-21 [1] for this JCache updating task.
> It will help us to manage the issues and see the progress in one place.
Igniters,
I've prepared IEP-21 [1] for this JCache updating task.
It will help us to manage the issues and see the progress in one place.
Also, we have finally added tests for TCK 1.1.0 [2] to our TC which can be
run on any branch.
Both tests cases (for 1.0.1 and for 1.1.0) will coexist until
John,
The page is moved between FreeList buckets synchronously during the
corresponding cache entry update, so it is the part of cache.put() or
cache.remove() operation.
ср, 13 июн. 2018 г. в 2:32, Denis Magda :
> Whenever you add or remove an entry, it changes the size of a page which
> can
AffinityFunction interface has the following method:
int partition(Object key)
User calls cache.put(x,y) from the client.
In order to calculate the target node we have to call that partition method,
and then use partition map to get the node by partition.
But client does not have
Dmitriy Gladkikh created IGNITE-8789:
Summary: Add a call to the FailureHandler for an error with
meta-data.
Key: IGNITE-8789
URL: https://issues.apache.org/jira/browse/IGNITE-8789
Project:
Also it would be better to set the 'atomic' cache to PARTITIONED mode to
equally split the data across all available nodes. This can be done by
setting the 'cacheMode' property to 'PARTITIONED'. Please see [1].
Ivan
[1]
I would vote for 1 or 3 (this I like more), but not 2 as such breaking
change involves more pain to our users. Let it be in 3.0 and included in
migration guide, I don't see much drawbacks here.
Thanks!
13.06.2018 19:20, Ivan Rakov пишет:
+1 to Eduard.
It's a reasonable change, but we can't
Hi Nikolay,
I'll take a look at the nearest time.
On Sat, Jun 9, 2018 at 6:14 PM, Nikolay Izhikov wrote:
> Hello, guys.
>
> I've implement prototype of TDE implementation [1]
> Vladimir, can you do some prereview of this prototype?
> Any feedback on public API or any other part of
Denis, that's right.
Best Regards,
Igor
On Wed, Jun 13, 2018 at 10:58 PM Denis Magda wrote:
> Pavel,
>
> Most likely the client will be pulling the partitioning map periodically.
> If the local map is outdated, it won't be a big deal because a server node
> that receives a request:
>
>-
Yashasvi Kotamraju created IGNITE-8788:
--
Summary: Getting NullPointerException during commit into
cassandra, after reconnecting to ignite server
Key: IGNITE-8788
URL:
Hi Pavel,
Thanks for trying to run the benchmark. The error arises because an Apache
Ignite node started with the default config does not have the cache with
name '*atomic*'. To run the benchmark you should do the following:
1. Checkout latest '*master*' branch from Apache Ignite repo [1].
47 matches
Mail list logo
