Nikolay, Alexey,
First, the idea of the slim binary release and docker image was discussed
openly on the dev-list [1]. Second, nobody talks about removing these
modules from the product. The idea was to create an additional distribution
which is much lighter than the current full package to
Hello, Ilya.
ignite-jta
ignite-zookeeper
Why you suggest to remove these modules?
As far as I know, they are used in the real production environment.
You can take this vide(in Russian) as an example -
https://www.youtube.com/watch?v=GSi_C9_gQMc
> 29 февр. 2020 г., в 08:22, Alexey Zinoviev
>
I have no idea what is the slim package and why the Ml should be remove
from that. We doesnt discuss it before and it looks like very strange list
is not based on previos discussions
Also, I see, that Ilya has outdated list of modules: we see here removed
tensorflow and missed New Spark 2.4
Ivan, thanks for stepping in.
Prasad, is Ivan's assumption correct that you query the data with SQL under
the observed circumstances? My guess is that you were referring to the
key-value APIs as long as the issue is gone when the write-through is
enabled.
-
Denis
On Fri, Feb 28, 2020 at 2:30
As I understand the thing here is in combination of read-through and
SQL. SQL queries do not read from underlying storage when read-through
is configured. And an observed result happens because query from a
client node over REPLICATED cache picks random server node (kind of
load-balancing) to
Ilya,
Actually I don't remember that we've come to an agreement with the
list of modules for "slim" distribution. AFAIR, those discussion still
not finished.
Also, why should we remove `ignite-ml` from current distribution?
Alexey, should we?
On Sat, 29 Feb 2020 at 00:38, Denis Magda wrote:
>
Sounds reasonable to produce the slim package. Though, if it's time
consuming then we should target it to 2.8.1.
-
Denis
On Fri, Feb 28, 2020 at 1:36 PM Ilya Kasnacheev
wrote:
> Hello!
>
> Are we doing a "slim" package for 2.8, though?
>
> There was a suggestion to remove the following
Hello!
Are we doing a "slim" package for 2.8, though?
There was a suggestion to remove the following modules from slim binary
distribution:
ignite-aop
ignite-aws
ignite-camel
ignite-cassandra-serializers
ignite-cassandra-store
ignite-cloud
ignite-direct-io
ignite-flink
ignite-flume
ignite-gce
Please disregard previous message. I jumped into a wrong train.
Best regards,
Ivan Pavlukhin
пт, 28 февр. 2020 г. в 22:52, Ivan Pavlukhin :
>
> I believe that some permissions are required to access a project with
> release builds on TC.
>
> Best regards,
> Ivan Pavlukhin
>
> пт, 28 февр. 2020
I might have missed some context, but a side note:
> If current thread is write lock owner then it can't acquire read lock.
> RRWL doesn't allow upgrades or downgrades.
>From ReentrantReadWriteLock javadoc:
Reentrancy also allows downgrading from the write lock to a read lock,
by acquiring the
I believe that some permissions are required to access a project with
release builds on TC.
Best regards,
Ivan Pavlukhin
пт, 28 февр. 2020 г. в 11:58, Pavel Tupitsyn :
>
> Sergey, can't confirm, those links work for me
>
> On Thu, Feb 27, 2020 at 11:17 PM Sergey Antonov
> wrote:
>
> > Hello,
Pavel,
Good news!
Best regards,
Ivan Pavlukhin
чт, 27 февр. 2020 г. в 16:34, Pavel Tupitsyn :
>
> Ivan, thank you, this is the answer:
>
> > it always fails when configured to run with Java 9 and higher
>
> Ignite can only be built with Java 8, and NuGet project includes Java build
> step,
Hello, Petr,
Can we share these suites [1] [2] to the whole community, for
instance, in read-only mode?
I think they are helpful for testing\checking the release by each
community member.
TC [Check RC: Licenses, compile, chksum]
[1]
Marinko created IGNITE-12730:
Summary: Streaming blocking threads
Key: IGNITE-12730
URL: https://issues.apache.org/jira/browse/IGNITE-12730
Project: Ignite
Issue Type: Bug
Components:
Andrey N. Gura created IGNITE-12729:
---
Summary: LT.warn() method ignores passed exception
Key: IGNITE-12729
URL: https://issues.apache.org/jira/browse/IGNITE-12729
Project: Ignite
Issue
Maxim,
I get 404 code for all TC links [1][2][3] in your email, not only TC [Check
RC: Licenses, compile, chksum]. [1]
[1]
https://ci.ignite.apache.org/viewLog.html?buildId=5085462=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum=buildResultsDiv
[2]
Maxim,
Finally, thanks a lot for starting the voting process!
I've already cast my vote and want to bring up some issues that are not
blockers though:
1. Ignite technical documentation is not finished yet - @Artem Budnikov
is coordinating this process as well as
contributes to many
+1 (binding)
Downloaded, started a cluster, ran several examples pulling Maven
artifacts from the staging.
-
Denis
On Fri, Feb 28, 2020 at 7:09 AM Maxim Muzafarov wrote:
> Dear Community,
>
>
> I have uploaded a release candidate to:
>
Amelchev Nikita created IGNITE-12728:
Summary: The cache#putAllAsync method does not collect statistics
Key: IGNITE-12728
URL: https://issues.apache.org/jira/browse/IGNITE-12728
Project: Ignite
Dear Community,
Please use this thread for all non-voting, discussion, questions
related to this 2.8.0-rc1 release.
Cast your vote here:
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Release-Apache-Ignite-2-8-0-RC1-td46140.html
Dear Community,
I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.8.0-rc1/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.8.0-rc1/
The following staging can be used for testing:
Ivan,
I also don't think this issue is a blocker for 2.8 as it affects only
experimental functionality and only in special cases.
Removing key length limitations in MetaStorage seems more strategic
approach to me but depending on how we decide to approach it (as a local
fix or as part of a
Moti Nisenson-Ken created IGNITE-12727:
--
Summary: BYOK support
Key: IGNITE-12727
URL: https://issues.apache.org/jira/browse/IGNITE-12727
Project: Ignite
Issue Type: Wish
Sergey,
It seems these links ([4] Check RC: Licenses, compile, checksum) [1]
is only accessed for users included into the release group on the
TeamCity.
Sorry for not mentioned it before.
[1]
Ivan,
This issue doesn't seem to be a blocker for 2.8 release from my point of view.
I think we definitely will have such bugs in future and 2.8.1 is our
goal for them.
Please, let me know if we should wait for the fix and include it exactly in 2.8.
On Fri, 28 Feb 2020 at 15:40, Nikolay
Igniters,
I think we can replace cache name with the cache id.
This should solve issue with the length limitation.
What do you think?
> 28 февр. 2020 г., в 15:32, Ivan Bessonov написал(а):
>
> Hello Igniters,
>
> we have an issue in master branch and in the upcoming 2.8 release that
>
Hello Igniters,
we have an issue in master branch and in the upcoming 2.8 release that
related to new metrics functionality implemented in [1]. You can't use new
"configureHistogramMetric" and "configureHitRateMetric" configuration
methods on caches with long names. My estimation shows that cache
Guys, can somebody check those links from TC account different from @
apache.org domain?
пт, 28 февр. 2020 г. в 11:58, Pavel Tupitsyn :
> Sergey, can't confirm, those links work for me
>
> On Thu, Feb 27, 2020 at 11:17 PM Sergey Antonov >
> wrote:
>
> > Hello, Maxim!
> >
> > All your links to
Ivan Bessonov created IGNITE-12726:
--
Summary: Cache names can't be used as part of
DistributedMetaStorage keys
Key: IGNITE-12726
URL: https://issues.apache.org/jira/browse/IGNITE-12726
Project:
Prasad,
The current version in the entry is checked agains the version which was
read from the very same entry, so with absence of concurrent updates the
version will be the same.
>From your description, I think there might be a concurrent read for the key
that you clear which loads the value on
Maxim, I checked the links - looks we are all set!
чт, 27 февр. 2020 г. в 23:17, Sergey Antonov :
> Hello, Maxim!
>
> All your links to ci.ignite.apache.org/ return 404 http code. It's okay?
>
> чт, 27 февр. 2020 г. в 19:06, Maxim Muzafarov :
>
> > Igniters,
> >
> >
> > I've prepared everything
Can someone please comment on this?
On Wed, Feb 26, 2020 at 6:04 AM Denis Magda wrote:
> Ignite Dev team,
>
> This sounds like an issue in our replicated cache implementation rather
> than an expected behavior. Especially, if partitioned caches don't have
> such a specificity.
>
> Who can
Hi Artsiom,
I replied in the ticket [1].
[1] https://issues.apache.org/jira/browse/IGNITE-12610
Best regards,
Ivan Pavlukhin
ср, 26 февр. 2020 г. в 19:04, Artsiom Panko :
>
> Hello everyone. Task 12610
> (https://issues.apache.org/jira/browse/IGNITE-12610) is ready for review
>
Hi,
* How do you ensure that there are no concurrent updates on the keys?
[Prasad]: The cache for which it is failing is kind of bootstrap cache
which changes very rarely. I made sure that I was the only one working on
this system while debugging the issue.
The cache for which it is failing is
I guest those links on CI are visible to only Release Manager, mostly PMCs from
Apache Ignite.
> On 28 Feb 2020, at 11:58, Pavel Tupitsyn wrote:
>
> Sergey, can't confirm, those links work for me
>
> On Thu, Feb 27, 2020 at 11:17 PM Sergey Antonov
> wrote:
>
>> Hello, Maxim!
>>
>> All
Classification: For internal use only
Hi, I can confirm. I also see:
404
You do not have enough permissions to access project with internal id: project20
i.e for this link:
Sergey, can't confirm, those links work for me
On Thu, Feb 27, 2020 at 11:17 PM Sergey Antonov
wrote:
> Hello, Maxim!
>
> All your links to ci.ignite.apache.org/ return 404 http code. It's okay?
>
> чт, 27 февр. 2020 г. в 19:06, Maxim Muzafarov :
>
> > Igniters,
> >
> >
> > I've prepared
Prasad,
> Can you please answer following questions?
> 1) The significance of the nodeOrder w.r.t Grid and cache?
>
Node order is a unique integer assigned to a node when the node joins grid.
The node order is included into GridCacheVersion to disambiguate versions
generated on different nodes
38 matches
Mail list logo
