Roman Kondakov created IGNITE-10752:
---
Summary: MVCC: Tests invariants are violated sometimes
Key: IGNITE-10752
URL: https://issues.apache.org/jira/browse/IGNITE-10752
Project: Ignite
Issue
Hello!
We often rely on server nodes' logs since there is always possibility that
client will swallow our error, especially when we discover internal errors.
We could try and isolate cases when we are sure that there is error on user
side, change log level for such errors.
Regards,
--
Ilya
Ivan Pavlukhin created IGNITE-10757:
---
Summary: Refactoring: split MvccProcessor into multiple components
Key: IGNITE-10757
URL: https://issues.apache.org/jira/browse/IGNITE-10757
Project: Ignite
Roman Kondakov created IGNITE-10756:
---
Summary: MVCC: Query trackers are not released sometimes
Key: IGNITE-10756
URL: https://issues.apache.org/jira/browse/IGNITE-10756
Project: Ignite
I think that the error detected in the server’s SQL engine is INFO or even
DEBUG – for the server it is just a normal workflow.
At the same time the error needs to be propagated to the client – and shown to
the user as an exception, error code in the response, etc.
Stan
From: Ilya Kasnacheev
Yuriy,
I have several questions:
Are we going to add some properties to cluster configuration for history
size?
And what will be default history size?
Will the same queries count as same item of historical data?
How we will evict old data that not fit into history?
Will we somehow count
Pavel Kovalenko created IGNITE-10749:
Summary: Improve speed of checkpoint finalization on binary memory
recovery
Key: IGNITE-10749
URL: https://issues.apache.org/jira/browse/IGNITE-10749
Hi Igniters,
As of now we have query statistics (
*org.apache.ignite.IgniteCache#queryMetrics*) , but it's look a little bit
wrong, due to at least few reasons:
1) Duration execution it just time between start execution and return
cursor to client and doesn't include all life time of query.
2) It
Yury Gerzhedovich created IGNITE-10754:
--
Summary: Query history statistics API
Key: IGNITE-10754
URL: https://issues.apache.org/jira/browse/IGNITE-10754
Project: Ignite
Issue Type: Task
Hello!
I don't think we can push it to public repositories in binary form. No
change in that regard. As for Spring, I honestly have no idea. Maybe
they're dual license?
Regards,
--
Ilya Kasnacheev
чт, 20 дек. 2018 г. в 01:32, Scott Feldstein :
> Hi Ilya, that’s great news!
>
> What’s the
Roman Kondakov created IGNITE-10753:
---
Summary: MVCC: Sometimes vacuum does not cleanup all outdated
versions
Key: IGNITE-10753
URL: https://issues.apache.org/jira/browse/IGNITE-10753
Project:
Denis
I can't agree with you.
Apache Ignite is the compute platform. It means that an exception on a
server node looks like an alarm that something went wrong or even broken.
I think if we can catch the mistake from user request and return the
correct response (e.g. with error code) is good
Hi,
I prepared a patch with deadlock detection algorithm implementation
(you can find it from ticket [1]).
Now I would like to discuss options for configuring deadlock
detection. From a usability standpoint following need to be supported:
1. Turn deadlock detection on/off (on by default).
2.
Maxim Muzafarov created IGNITE-10748:
Summary: Remove dead code in TcpCommunicationSpi for the tcp
client creation flow
Key: IGNITE-10748
URL: https://issues.apache.org/jira/browse/IGNITE-10748
Ilya Kasnacheev created IGNITE-10751:
Summary: Document hibernate-5.3 module
Key: IGNITE-10751
URL: https://issues.apache.org/jira/browse/IGNITE-10751
Project: Ignite
Issue Type: Task
Oleg Ignatenko created IGNITE-10758:
---
Summary: remove from tests scaffolding annotations
"@RunWith(JUnit4.class)" and their respective imports
Key: IGNITE-10758
URL:
Roman Kondakov created IGNITE-10755:
---
Summary: MVCC: Flaky continuous query tests
Key: IGNITE-10755
URL: https://issues.apache.org/jira/browse/IGNITE-10755
Project: Ignite
Issue Type: Bug
More food for thought - here are JCL guidelines that look close to what I’ve
suggested:
http://commons.apache.org/proper/commons-logging/guide.html#JCL_Best_Practices
Big thanks to Oleg Ignatenko for the pointer.
Thanks,
Stan
From: Stanislav Lukyanov
Sent: 20 декабря 2018 г. 17:20
To:
+1.
ERROR and even WARNING messages are often treated as incidents in the
production systems.
Ignite produces a lot of these messages though.
I’d suggest the following as a rule of thumb:
- ERROR – we’re sure there is an issue with a node/cluster that needs
attention; cluster stability and/or
Andrey Gura created IGNITE-10760:
Summary: Confusing message about system worker blocking
Key: IGNITE-10760
URL: https://issues.apache.org/jira/browse/IGNITE-10760
Project: Ignite
Issue
Roman Kondakov created IGNITE-10750:
---
Summary: MVCC: Unexpected tx state exception after coordinator fail
Key: IGNITE-10750
URL: https://issues.apache.org/jira/browse/IGNITE-10750
Project: Ignite
Hello!
Where should user-specified SQL errors and REST call parameter errors fall
in this scheme?
Regards,
--
Ilya Kasnacheev
чт, 20 дек. 2018 г. в 16:12, Stanislav Lukyanov :
> +1.
>
> ERROR and even WARNING messages are often treated as incidents in the
> production systems.
> Ignite
I agree that the status quo is that all info is at least visible in the Ignite
server logs,
so I’d avoid making current ERROR/WARN messages DEBUG for now.
INFO is safe though – we’ll be able to debug things same as now, but monitoring
systems won’t complain about our unnecessarily red log.
Andrew Mashenkov created IGNITE-10759:
-
Summary: Disable implicit distributed joins when
queryParallelizm>1.
Key: IGNITE-10759
URL: https://issues.apache.org/jira/browse/IGNITE-10759
Project:
Roman Kondakov created IGNITE-10767:
---
Summary: MVCC: Unknown page type error during scan query
Key: IGNITE-10767
URL: https://issues.apache.org/jira/browse/IGNITE-10767
Project: Ignite
Pavel Kovalenko created IGNITE-10771:
Summary: Print troubleshooting hint when exchange latch got stucked
Key: IGNITE-10771
URL: https://issues.apache.org/jira/browse/IGNITE-10771
Project: Ignite
I think I found names which should satisfy me and Denis, and possibly Nikolay )
See the following names (Actual name <- Previously used):
- ServiceDeploymentManager <- ServicesDeploymentManager
- ServiceDeploymentActions <- ServicesDeploymentActions
- ServiceDeploymentProcessId <-
Roman Kondakov created IGNITE-10765:
---
Summary: MVCC:
MvccReplicatedTxPessimisticOriginatingNodeFailureRecoveryTest.testManyKeysRollback
fails sometimes
Key: IGNITE-10765
URL:
Roman Kondakov created IGNITE-10769:
---
Summary: MVCC:
CacheMvccContinuousQueryClientTest.testNodeJoinsRestartQuery fails sometimes
Key: IGNITE-10769
URL: https://issues.apache.org/jira/browse/IGNITE-10769
Roman Kondakov created IGNITE-10764:
---
Summary: MVCC: Transactions failed to acquire lock within timeout
Key: IGNITE-10764
URL: https://issues.apache.org/jira/browse/IGNITE-10764
Project: Ignite
Roman Kondakov created IGNITE-10768:
---
Summary: MVCC:
CacheMvccBasicContinuousQueryTest.testUpdateCountersGapClosedSimplePartitioned
may hang
Key: IGNITE-10768
URL:
Roman Kondakov created IGNITE-10770:
---
Summary: MVCC: testInsertAndQueryMultipleCaches in JDBC suite is
flaky
Key: IGNITE-10770
URL: https://issues.apache.org/jira/browse/IGNITE-10770
Project:
Sergey Antonov created IGNITE-10761:
---
Summary: GridCacheProcessor should add info about cache in
excecption message, if applicable.
Key: IGNITE-10761
URL: https://issues.apache.org/jira/browse/IGNITE-10761
Roman Kondakov created IGNITE-10766:
---
Summary: MVCC:
CacheMvccTxRecoveryTest.testCountersNeighborcastServerFailed fails sporadically
Key: IGNITE-10766
URL: https://issues.apache.org/jira/browse/IGNITE-10766
Roman Kondakov created IGNITE-10763:
---
Summary: MVCC: Transaction already completed error in some tests
Key: IGNITE-10763
URL: https://issues.apache.org/jira/browse/IGNITE-10763
Project: Ignite
ARomantsov created IGNITE-10772:
---
Summary: If version look like X.X.X.X rest version return X.X.X-X
Key: IGNITE-10772
URL: https://issues.apache.org/jira/browse/IGNITE-10772
Project: Ignite
Hi,
I uploaded updated version of the plugin to community wiki [1].
[1] https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules
пн, 17 дек. 2018 г. в 19:47, Павлухин Иван :
>
> Dmirity,
>
> Thank you! Permissions works for me.
>
> I will spend a while using a newly built plugin on
Anton Dmitriev created IGNITE-10747:
---
Summary: [ML] Add NaN (missing) value support into Decision Tree
training
Key: IGNITE-10747
URL: https://issues.apache.org/jira/browse/IGNITE-10747
Project:
Anton Dmitriev created IGNITE-10746:
---
Summary: ML: Participate in TensorFlow 2.0 preparation
Key: IGNITE-10746
URL: https://issues.apache.org/jira/browse/IGNITE-10746
Project: Ignite
Issue
39 matches
Mail list logo
