Ilya Kasnacheev created IGNITE-12483:
Summary: ReflectionFactory is essential thanks to
PlatformDotNetSessionLockResult
Key: IGNITE-12483
URL: https://issues.apache.org/jira/browse/IGNITE-12483
Hi,
>From time to time I receive a following warning message (see quoted
below) from a program managing Ignite mailing lists. My guess is that
it is somehow related to gmail (spam) filtering. Does anyone
experience the same? Does anyone know how to fix it?
Quoted message
Hi! This is the
Igniters,
One more PME optimization ready to be reviewed.
I found a strange tx recovery delay caused by IGNITE_TX_SALVAGE_TIMEOUT.
I've checked the code and tests and found no reason to delay recovery.
So, the issue [1] is ready to be reviewed.
Improvement checked with benchmark [2] and fix,
Taras Ledkov created IGNITE-12484:
-
Summary: Fix issues related to client cache stop and SQL metadata
retrieval
Key: IGNITE-12484
URL: https://issues.apache.org/jira/browse/IGNITE-12484
Project:
Ivan Bessonov created IGNITE-12488:
--
Summary: Fix JavaDocs in DistributedMetaStorage
Key: IGNITE-12488
URL: https://issues.apache.org/jira/browse/IGNITE-12488
Project: Ignite
Issue Type:
Alexey, are you sure, you are testing new service framework?
Is yes - you definitely should file a bug.
> 23 дек. 2019 г., в 17:02, Alexey Goncharuk
> написал(а):
>
> Igniters,
>
> I have a question based on one of my recent tests debugging.
>
> The test is related to Ignite services. I
Hello!
Let me chime in to this discussion.
If we are doing any new metrics, please make sure that they are accessible.
I would expect that metrics are printed to console from time to time, at
least when they deviate from norm. It would also help if they are available
as Web Console screen, a
What is also interesting here is it specific to gmail or other email
providers are affected as well?
And what bothers me is that some messages seems to be undelivered to
my inbox. I even followed ezmlm instructions to request "bouncing"
messages and it worked fine. But it is inconvenient =(
пн,
Hi Ivan,
I receive such emails from time to time and I did not manage to
understand the conditions when this happens. From a quick search it looked
like it was related to the number of messages being received per certain
time interval, but I could not confirm this based on the number of messages
Ivan Bessonov created IGNITE-12485:
--
Summary: DiscoveryEvent make event message lazy initialization
Key: IGNITE-12485
URL: https://issues.apache.org/jira/browse/IGNITE-12485
Project: Ignite
Ivan Bessonov created IGNITE-12486:
--
Summary: Truncation of archived WAL segments doesn't work
Key: IGNITE-12486
URL: https://issues.apache.org/jira/browse/IGNITE-12486
Project: Ignite
Igniters,
I have a question based on one of my recent tests debugging.
The test is related to Ignite services. I noticed that sometimes a proxy
invocation of a newly deployed service fails because the service cannot be
found. I managed to reduce the test to a simple "start two nodes, deploy a
Ivan Bessonov created IGNITE-12487:
--
Summary: Inconsistent GridIoManager API for
sendToGridTopic(Collection nodes) and sendToGridTopic(UUID nodeId)
Key: IGNITE-12487
URL:
Nikolay,
Yes, I've rechecked, the new service processor is being used. I'll file a
bug shortly.
пн, 23 дек. 2019 г. в 17:33, Николай Ижиков :
> Alexey, are you sure, you are testing new service framework?
>
> Is yes - you definitely should file a bug.
>
> > 23 дек. 2019 г., в 17:02, Alexey
Ruslan Kamashev created IGNITE-12489:
Summary: Error during purges by expiration: Unknown page type
Key: IGNITE-12489
URL: https://issues.apache.org/jira/browse/IGNITE-12489
Project: Ignite
Pavel,
Thanks for taking over!
-
Denis
On Mon, Dec 23, 2019 at 12:21 AM Pavel Tupitsyn
wrote:
> Since there are no objections, I'm doing the rename:
> https://issues.apache.org/jira/browse/IGNITE-12458
>
> On Fri, Dec 20, 2019 at 1:12 PM Igor Sapego wrote:
>
> > +1, sounds reasonable to me.
https://repository.apache.org
At least Ignite PMC has access to data.
-
Denis
On Mon, Dec 23, 2019 at 11:35 AM Ilya Kasnacheev
wrote:
> Hello!
>
> Can you guide me where these downloads are from? We don't seem to publish
> ignite-schedule to Maven Central since early 1.x.
>
> Regards,
> --
>
Hi Ivan,
I also receive such emails recurrently, but this program didn't reject my
subscription. So I just ignore it.
Sincerely,
Dmitriy Pavlov
пн, 23 дек. 2019 г. в 18:25, Ivan Pavlukhin :
> What is also interesting here is it specific to gmail or other email
> providers are affected as well?
Hi, Alexey
Please attach a reproducer to the ticket.
As far as I remember we have the following behaviour for the proxies:
Let's assume you have deployed service from node A, then:
* if you invoke service locally from node A - it is guaranteed to
service to be deployed and ready to work
* if
Forwarding to the dev list. How exactly would you like to expand Visor CMD?
Please describe your idea and we can mover from that point.
Denis
On Monday, December 23, 2019, sgtech19 wrote:
> Hello team,
> I would like to add a new feature to the existing visor
> commands. Could
Hello!
I did not find the exact information but I can confirm that ignite-schedule
1.0.0 may see some downloads, but that's all. Since 1.0.0 we don't publish
this artifact so its usage also remains a mystery.
Regards,
--
Ilya Kasnacheev
пн, 23 дек. 2019 г. в 22:37, Denis Magda :
>
Since there are no objections, I'm doing the rename:
https://issues.apache.org/jira/browse/IGNITE-12458
On Fri, Dec 20, 2019 at 1:12 PM Igor Sapego wrote:
> +1, sounds reasonable to me.
>
> Best Regards,
> Igor
>
>
> On Fri, Dec 20, 2019 at 10:25 AM Pavel Tupitsyn
> wrote:
>
> > +1, let's
Ivan Pavlukhin created IGNITE-12482:
---
Summary: SQL: sql returns incorrect results for replicated caches
if started on node where rebalance is in progress
Key: IGNITE-12482
URL:
Folks,
I raised one more blocker for 2.8 [1]. It is about improper results of
query execution over REPLICATED cache in presence of MOVING
partitions. Fix is already on the way. Will finish with it in couple
of days.
[1] https://issues.apache.org/jira/browse/IGNITE-12482
пн, 23 дек. 2019 г. в
Folks,
Just for your information. Here is the list of release blockers issues
at this moment:
[1] IGNITE-9184 [Dmitriy Sorokin] Cluster hangs during concurrent node
client and server nodes restart
[2] IGNITE-12458 [Pavel Tupitsyn] Rename Affinity Awareness to
Partition Awareness
[3]
25 matches
Mail list logo
