Dmitriy Govorukhin created IGNITE-10891:
---
Summary: IgnitePdsThreadInterruptionTest.testInterruptsOnLFSRead
flaky in PDS indexing
Key: IGNITE-10891
URL: https://issues.apache.org/jira/browse/IGNITE-10891
Hi Denis,
Mixing JIRA and human mails in one list seems to be inconvenient both for
those interested in monitoring human and JIRA mails and from this
perspective separate lists approach looks superior.
Also, your mention of filtering made me wonder if "mixed" approach may have
effect opposite to
Also, for future releases Ignite-Spark connection we could start with
testing of scala 2.12 profile because Spark 2.4 could be run on Scala 2.12
See the link https://issues.apache.org/jira/browse/SPARK-14220
I also support drop 2.10 profile but later, in 3.0 release to wait more
widely adoption
Ilya, can you check your test on current implementation [1]?
[1] https://github.com/apache/ignite/pull/5662
10 дек. 2018 г. 17:10 пользователь "Dmitriy Pavlov"
написал:
Reverted.
https://issues.apache.org/jira/browse/IGNITE-8227 reopened
пн, 10 дек. 2018 г. в 16:23, Dmitriy Pavlov :
>
Ilya Borisov created IGNITE-10890:
-
Summary: Web console: UIRouter cleanup
Key: IGNITE-10890
URL: https://issues.apache.org/jira/browse/IGNITE-10890
Project: Ignite
Issue Type: Improvement
Denis,
Could you please specify what component and what type of downloads do you
mean.
What is the ratio between 2.10 and actual?
P.s. There is a big chance that 150 downloads caused by TC or by Release
check.
On Fri, Jan 11, 2019 at 2:17 AM Denis Magda wrote:
> I see that we're getting
Hi Ilya,
I am not able reproduce this issue in small reproducer project but this is
consistently happening in my project. So I debugged this issue and attached
the screenshot in this mail.
*NOTE: *This issue occurs if the statistics are enabled on cache
configuration level
Resending with screenshots.
> I am not able reproduce this issue in small reproducer project but this is
> consistently happening in my project. So I debugged this issue and attached
> the screenshot in this mail.
>
>
>
> *NOTE: *This issue occurs if the statistics are enabled on cache
>
Resending
I am not able reproduce this issue in small reproducer project but this is
consistently happening in my project. So I debugged this issue and attached
the screenshot in this mail.
*NOTE: *This issue occurs if the statistics are enabled on cache
configuration level
Hi, Igniters!
I want discuss and define options naming format in our utilities. I found
two naming styles in CommandHandler class --excludeCaches and --skip-zeros.
I think we should unify it. At this moment almost all options have second
naming format. I am offering rename --excludeCaches to
Alexei Scherbakov created IGNITE-10894:
--
Summary: Reduce heap utilization for grids with big topologies and
caches numbers.
Key: IGNITE-10894
URL: https://issues.apache.org/jira/browse/IGNITE-10894
Hi Oleg,
AFAIK digest subscription works for individuals, who can voluntary
subscribe to digests. It is not about forwarding digests from one list
to another.
Forwarding digest may require us to develop some kind of our own tool for
this (like AI TC Bot), but I would like to avoid any
Sergey,
Thanks for raising up the question.
Did you mean following (?):
- boolean argument: *--word1-word2*
- single value argument *--word1-word2=value*
- multiple values argument *--word1-word2=value1 --word1-word2=value2*
On Fri, Jan 11, 2019 at 2:05 PM Sergey Antonov
wrote:
> Hi,
Alexander Lapin created IGNITE-10893:
Summary: ClientListenerResponse.status uses codes both from
IgniteQueryErrorCode and ClientListenerResponse itself.
Key: IGNITE-10893
URL:
Sergey,
Not quite, I meant:
- boolean argument: *--word1-word2*
- single value argument *--word1-word2 value*
- multiple values argument *--word1-word2 value1,value2*
пт, 11 янв. 2019 г. в 14:12, Sergey Kozlov :
> Sergey,
>
> Thanks for raising up the question.
>
> Did you mean following (?):
Yes, currently handler handles exception in the same way as
'GridAbstractTest', so, it will work from any thread.
пт, 11 янв. 2019 г., 15:18 Ilya Lantukh ilant...@gridgain.com:
> Dmitry,
>
> It doesn't make sense to run that test now because the root cause of it's
> failure had been fixed.
>
>
Yakov,
Sounds good. But there is a flaw in the procedure, that you described.
If we have a TcpDiscoveryMetricsUpdateMessage in a queue, and a newer one
arrives, then we will consider the existing one obsolete and won't process
it. The newest metrics update message will be moved to the queue's
Sergey Kozlov created IGNITE-10892:
--
Summary: Add support JDK 10/11 for ignite.sh(.bat)
Key: IGNITE-10892
URL: https://issues.apache.org/jira/browse/IGNITE-10892
Project: Ignite
Issue Type:
Roman Kondakov created IGNITE-10895:
---
Summary: MVCC: Document several modes of pessimistic transactions
are allowed for MVCC caches.
Key: IGNITE-10895
URL: https://issues.apache.org/jira/browse/IGNITE-10895
Hello!
1. Unfortunately, it's complicated:
- With JDBC, we don't really offer complete reasoning for a problem,
*especially* if it is Ignite internal problem or expectations mismatch,
which is frequent case.
- With ODBC, we don't have ways to offer full Java stack trace to client,
neither
Hello!
In any case I don't see why we would keep ignite-schedule module. We could
merge this change if you moved this functionality into ignite-spring (while
also fixing single thread problem).
The sole reason of existence of ignite-schedule module was the extra
dependency, if we don't have it
Maxim Pudov created IGNITE-10905:
Summary:
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtInvalidPartitionException
happens during rolling restart of a cluster
Key: IGNITE-10905
URL:
Mauricio,
Thanks for spotting and fixing the issue. I've merged the changes!
--
Denis
On Fri, Jan 11, 2019 at 9:40 AM Mauricio Stekl
wrote:
> Hi,
> In order to help with some SEO, I am attaching a patch that would fix some
> missing canonical tags for API docs under /releases/latest/ and adds
Dmitry,
It doesn't make sense to run that test now because the root cause of it's
failure had been fixed.
You should verify that getting an unhandled exception in any system thread
leads to the failure of currently running test.
On Fri, Jan 11, 2019 at 12:16 PM Dmitrii Ryabov
wrote:
> Ilya,
I like the idea to make all messages be processed with equal priority.
It will make nodes with overgrown discovery message queues die more often,
though. But maybe, this is how it's supposed to work.
Denis
пт, 11 янв. 2019 г. в 16:26, Denis Mekhanikov :
> Yakov,
>
> Sounds good. But there is a
ARomantsov created IGNITE-10896:
---
Summary: Add ability to use more than one key with control.sh
--cache idle_verify
Key: IGNITE-10896
URL: https://issues.apache.org/jira/browse/IGNITE-10896
Project:
Aleksey Zinoviev created IGNITE-10901:
-
Summary: [ML][Umbrella] Add support of regression metrics to
evaluate regression
Key: IGNITE-10901
URL: https://issues.apache.org/jira/browse/IGNITE-10901
Alexey Goncharuk created IGNITE-10898:
-
Summary: Exchange coordinator failover breaks in some cases when
node filter is used
Key: IGNITE-10898
URL: https://issues.apache.org/jira/browse/IGNITE-10898
Vyacheslav Daradur created IGNITE-10899:
---
Summary: Service Grid: disconnecting during node stop may lead to
deadlock
Key: IGNITE-10899
URL: https://issues.apache.org/jira/browse/IGNITE-10899
Stanislav Lukyanov created IGNITE-10900:
---
Summary: Print a warning if native persistence is used without an
explicit consistent ID
Key: IGNITE-10900
URL: https://issues.apache.org/jira/browse/IGNITE-10900
Denis,
+1 to the idea to get rid of priority.
Discovery should handle only messages used to update cluster state and
topology.
They are all small and have high priority.
There is no real reason to use discovery for metrics and similar "readonly"
features.
Maybe, better case it to have special
Aleksey Zinoviev created IGNITE-10902:
-
Summary: [ML] Implement a few regression metrics in one
RegressionMetrics class
Key: IGNITE-10902
URL: https://issues.apache.org/jira/browse/IGNITE-10902
Aleksey Zinoviev created IGNITE-10904:
-
Summary: [ML] Refactor all examples with regression to use
RegressionMetrics
Key: IGNITE-10904
URL: https://issues.apache.org/jira/browse/IGNITE-10904
JiajunYang created IGNITE-10897:
---
Summary: Blocked drop table operations cause strange issues
Key: IGNITE-10897
URL: https://issues.apache.org/jira/browse/IGNITE-10897
Project: Ignite
Issue
> How big the message worker's queue may grow until it becomes a problem?
Denis, you never know. Imagine node may be flooded with messages because of
the increased timeouts and network problems. I remember some cases with
hundreds of messages in queue on large topologies. Please, no O(n)
Pavel Kuznetsov created IGNITE-10906:
Summary: SQL: UPDATE statement allows null for entire value cache
object
Key: IGNITE-10906
URL: https://issues.apache.org/jira/browse/IGNITE-10906
Project:
Dmitriy Govorukhin created IGNITE-10907:
---
Summary:
IgniteUtilsSelfTest.testDoInParallelWithStealingJobRunTaskInExecutor flaky
failed in Basic 1
Key: IGNITE-10907
URL:
1500 (2.11) vs 150 (2.10) - downloads of ignite-scalar artifacts of defined
version. My point is that those few who are on 2.10 should be considered -
we usually don't do breaking changes in minor releases, only major.
Ignite 3.0?
--
Denis
On Fri, Jan 11, 2019 at 12:59 AM Anton Vinogradov
Dmitriy Govorukhin created IGNITE-10909:
---
Summary: GridCacheBalancingStoreSelfTest.testConcurrentLoad flaky
test fail in Cache 1
Key: IGNITE-10909
URL: https://issues.apache.org/jira/browse/IGNITE-10909
Dmitriy Govorukhin created IGNITE-10908:
---
Summary:
GridServiceProcessorBatchDeploySelfTest.testDeployAllTopologyChange flaky fail
with NPE in Service Grid (legacy mode)
Key: IGNITE-10908
URL:
40 matches
Mail list logo
