Denis,
>> the blocking PME no longer happens if a node leaves the cluster
We should mention this should be the baseline node
On Tue, Mar 10, 2020 at 9:40 AM Denis Magda wrote:
> Pavel, thank you. I referred to your article from a blog post to be
> published on blogs.apache.org. Please feel free
Denis Garus created IGNITE-12759:
Summary: Getting a SecurityContext from GridSecurityProcessor
Key: IGNITE-12759
URL: https://issues.apache.org/jira/browse/IGNITE-12759
Project: Ignite
Issue
Hi guys!
I created the iep ticket [1] and started work.
1. https://issues.apache.org/jira/browse/IGNITE-12759
чт, 5 мар. 2020 г. в 12:00, Denis Garus :
> Hi, guys!
>
>
> I've prepared the IEP-41: Security Context of a thin client on remote
> nodes [1]; take a look, please.
>
> If there aren't an
Hello, Igniters.
I rewrote pages about new metrics and system views.
Please, take a look.
https://apacheignite.readme.io/docs/new-metrics
https://apacheignite.readme.io/docs/system-views
https://issues.apache.org/jira/browse/IGNITE-12408
> 6 марта 2020 г., в 16:40, Artem Budnikov
> написал(а
Folks,
It seems everything is ready to go and only minor issues left with
documentation.
Are we ready to announce 2.8 release widely?
On Tue, 10 Mar 2020 at 12:10, Nikolay Izhikov wrote:
>
> Hello, Igniters.
>
> I rewrote pages about new metrics and system views.
> Please, take a look.
>
> http
Hello!
It is currently included.
Maxim, can you prepare a slim release package based on your generic release
procedures? We could take a look at it and then perhaps add it to downloads
page officially.
What do you think?
Regards,
--
Ilya Kasnacheev
пт, 6 мар. 2020 г. в 20:48, Maxim Muzafarov
Hello!
Please avoid targeting feature tickets on 2.8.1 by default.
As far as my understanding goes, plan for 2.8.1 is to be a bugfix release
with specific changes cherry picked, so new features are unlikely to be
included, and should be negotiated with person responsible for this release
before
Denis Chudov created IGNITE-12760:
-
Summary: Prevent AssertionError on message unmarshalling, when
classLoaderId contains id of node that already left
Key: IGNITE-12760
URL: https://issues.apache.org/jira/browse/I
Hi Nikolay,
I looked through the metrics pages and found a couple of minor issues:
* Looks like this sentence should contain a link to somewhere:
"Please, see XXX as an example and OpenCensus documentation for
additional information."
* Please mention that for the OpenCensus exporter to
Philipp Masharov created IGNITE-12761:
-
Summary: Add ability to disable check crc sums of stored pages due
to invalidate_indexes.
Key: IGNITE-12761
URL: https://issues.apache.org/jira/browse/IGNITE-12761
Alexander Kovalev created IGNITE-12762:
--
Summary: PHP: Thin client: Transactions
Key: IGNITE-12762
URL: https://issues.apache.org/jira/browse/IGNITE-12762
Project: Ignite
Issue Type: New
Hi Igniters,
Today I noticed quite old code aimed to workaround an old bug in 1.5 JDK
revision which was fixed in rev 1.7
org/apache/ignite/internal/util/nio/GridNioServer.java:161
Since we widely use lambdas now (so Ignite requires at least Java 1.8) do we
really need it now?
I would like to
Hello!
Feel free to file a ticket, contribute a fix.
Regards,
--
Ilya Kasnacheev
вт, 10 мар. 2020 г. в 16:38, Seliverstov Igor :
> Hi Igniters,
>
> Today I noticed quite old code aimed to workaround an old bug in 1.5 JDK
> revision which was fixed in rev 1.7
>
> org/apache/ignite/internal/uti
Nikolay Izhikov created IGNITE-12763:
Summary: OpenCensus integration example.
Key: IGNITE-12763
URL: https://issues.apache.org/jira/browse/IGNITE-12763
Project: Ignite
Issue Type: Sub-ta
Hello, Igniters.
I prepared a PR for the new system view - JOBS. [1]. Ticket [2]
For now, as you may know, internally we have two processors that implement
compute feature:
* `GridTaskProcessor` - manage locally started compute tasks.
* `GridJobProcessor` - manage compute jobs that should be e
Ilya Kasnacheev created IGNITE-12764:
Summary: Regression: Thin JDBC streaming
fails/BatchUpdateException if function is used
Key: IGNITE-12764
URL: https://issues.apache.org/jira/browse/IGNITE-12764
Maxim Muzafarov created IGNITE-12765:
Summary: Slim binary release and docker image for Apache Ignite
Key: IGNITE-12765
URL: https://issues.apache.org/jira/browse/IGNITE-12765
Project: Ignite
Ilya,
It is not "mine" generic release procedures they are "ours" :-)
I've created the issue [1] based on current discussion thread.
[1] https://issues.apache.org/jira/browse/IGNITE-12765
On Tue, 10 Mar 2020 at 13:31, Ilya Kasnacheev wrote:
>
> Hello!
>
> It is currently included.
>
> Maxim, c
Hello!
I understand that procedures are courtesy Apache Ignite, but I assume that
you went through them and can now repeat them reproducibly.
Thank you!
--
Ilya Kasnacheev
вт, 10 мар. 2020 г. в 18:12, Maxim Muzafarov :
> Ilya,
>
> It is not "mine" generic release procedures they are "ours" :-
Vyacheslav Koptilin created IGNITE-12766:
Summary: Node startup can be broken in case of using Local cache
with persistence enabled.
Key: IGNITE-12766
URL: https://issues.apache.org/jira/browse/IGNITE-1276
Andrey N. Gura created IGNITE-12767:
---
Summary: MetricRegistryMBean is not hread safe
Key: IGNITE-12767
URL: https://issues.apache.org/jira/browse/IGNITE-12767
Project: Ignite
Issue Type: Im
Anton,
Does it mean that the PME is skipped only for cases when the native
persistence is used and a failed node was in the baseline topology? How
about pure in-memory clusters and clusters with CacheStore?
-
Denis
On Tue, Mar 10, 2020 at 12:40 AM Anton Vinogradov wrote:
> Denis,
>
> >> the b
Andrey N. Gura created IGNITE-12768:
---
Summary: MetricRegistryMBean doesn't show histogram values in case
when histogram name contains underscore character
Key: IGNITE-12768
URL: https://issues.apache.org/jira/br
> • Looks like this sentence should contain a link to somewhere: "Please, see
> XXX as an example and OpenCensus documentation for additional information."
Fixed.
> • Please mention that for the OpenCensus exporter to work, the module
> should be enabled.
Fixed.
> • Also, there
Andrey N. Gura created IGNITE-12769:
---
Summary: MetricRegistryMBean and OpenCensusExporterSpi have memory
leak
Key: IGNITE-12769
URL: https://issues.apache.org/jira/browse/IGNITE-12769
Project: Ignit
Hi, everyone.
I've done some benchmarks and wonder whether we need to disable service
metrics somehow. As Denis suggested, proxies might be involved for local
services. If I enable current proxy for local services, I see the flowing
cases:
1) Service proxy is too slow with trivial operations to c
Hi Dmitry,
Thanks for the guidance. I've created the repository and will keep things
moving.
https://github.com/apache/ignite-website
-
Denis
On Sat, Mar 7, 2020 at 3:08 AM Dmitriy Pavlov wrote:
> Hi Denis,
>
> Unfortunately, I don't know details on how to set it up.
>
> One thing I've notic
@Nikolay Izhikov , @Andrey Gura ,
could you folks check out this thread?
I have a feeling that what Dominik is describing was talked out before and
rather some sort of a limitation than an issue with the current
implementation.
-
Denis
On Tue, Mar 3, 2020 at 11:41 PM Dominik Przybysz
wrote:
>
Igniters,
Not intentionally the discussion continued outside of dev list. I am
returning it back. You can find it below. Do not hesitate to join if you
have some thoughts on raised questions. May be you have ideas how to enrich
text query results with score/rank information.
вт, 10 мар. 2020 г. в
Igniters,
Initially I wanted to delay the discussion about everything related to
2.8.1 until all 2.8 release activities are finished, but I already see
some possible problems. Mainly it is related to adding tickets to
2.8.1 scope. I recall that it was already discussed in some other
thread that it
Ivan,
targeting to specific version means that this change should be
included in release with target fix version. No more, no less.
On Wed, Mar 11, 2020 at 2:42 AM Ivan Pavlukhin wrote:
>
> Igniters,
>
> Initially I wanted to delay the discussion about everything related to
> 2.8.1 until all 2.8
Andrey,
> targeting to specific version means that this change should be
> included in release with target fix version. No more, no less.
What do you mean by "targeting to a specific version" here? Fix
version in JIRA? Something else?
My main point here is to simplify things. Issues like [1] loo
32 matches
Mail list logo
