Hello Ignite Community!
My name is Alexey Popov. I want to contribute to Apache Ignite.
My Jira ID alexey.tank2
Thanks!
I've opened a ticket https://issues.apache.org/jira/browse/IGNITE-6828 some
time ago to fix this message.
If nobody argues I will prepare a patch.
Thanks,
Alexey
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hm, actually, I've missed existent MXBean: RebalancingPartitionsCount.
Probably it should be enough.
Thanks,
Alexey
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hi Igniters,
I saw several cases when Ignite users/admins need to ensure if Data
Rebalancing is NOT in progress to prevent possible data loss.
For instance, when nodes one-by-one are moved out of the cluster for
maintenance and returned back by some script.
Currently, this information could be
Hi Pavel,
Let me add my 5 cents.
1. It would be great if both Handshake request & response have some "magic"
number (2 or 4 bytes) inside their msg body. That will simplify handling
situations when non-Ignite client connects to Ignite server and vice versa.
2. It makes sense to add server
ode, 0 indicates success, everything else is an error.
Thanks,
Pavel
On Thu, Nov 30, 2017 at 12:01 PM, Alexey Popov <tank2.a...@gmail.com> wrote:
> Hi Pavel,
>
> Let me add my 5 cents.
>
> 1. It would be great if both Handshake request & response have some
> "
It will utilize commons-logging (it is in dependency tree) according to
https://spring.io/blog/2009/12/04/logging-dependencies-in-spring/
"The nice thing about commons-logging is that you don’t need anything else
to make your application work. It has a runtime discovery algorithm that
looks for
Hi Igniters,
Could you please advise why Ignite does not indicate
1) the logger type it uses
2) the logger configuration file (name) it applies
during startup?
Can we add such output to IgniteLogger implementations?
Thanks,
Alexey
--
Sent from:
Hi Igniters,
Ignite examples and Ignite itself with some configurations prints out
annoying messages related to slf4j:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See
I've created https://issues.apache.org/jira/browse/IGNITE-6826
Thanks,
Alexey
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Denis Magda
Sent: Tuesday, November 21, 2017 2:01 AM
To: dev@ignite.apache.org
Subject: Re: Ignite Logger & logging file config output
Good point. Could you create a ticket and probably contribute this improvement?
—
Denis
> On Nov 20, 2017, at 3:12 AM, Alexey Popov <tank2.a.
Hi Raymond,
You are right, distributed queues require changes at Ignite core.
https://issues.apache.org/jira/browse/IGNITE-2701
It was created almost 1 year ago. Please vote for this feature.
As far as I know there is no plan/schedule for it.
Thank you,
Alexey
From: Raymond Wilson
Sent:
ging file config output
Alexey,
Looks cool and helpful! I understand correctly that improvement is
implemented for all type of loggers which Ignite supports?
On Fri, Dec 1, 2017 at 5:18 PM, Alexey Popov <tank2.a...@gmail.com> wrote:
> Hi Denis,
>
> https://issues.apache.org/jira
Hi, Igniters
I wonder why Ignite examples have multicast ipFinder for DiscoverySpi at
their configuration?
It is a quite common case to try them locally and Vm ipFinder is the best
option for that.
Multicast ipFinder adds some instability when several persons try & debug
samples or evaluate a new
Hi Igniters,
I am looking into Client DiscoverySpi procedure and see some differences in
Client behavior when it trying to connect to servers.
Case 1: If the Client can't connect (Connection refused) to some Server it
goes to the next IP/port from the ipFinder list.
Case 2: But if the client
Hi Igniters,
We often see similar questions from users and customers related to
IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their
relations. And we see several side-effects after incorrect timeout
configuration.
I tried to briefly describe these timeout settings
Hi Yakov,
Do the proposed changes look good to you?
Thanks,
Alexey
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Yakov,
1. The proposal list of parameters to deprecate:
TcpDiscoverySpi.setConnectTimeout (covered by
IgniteConfiguration.setFailureDetectionTimeout)
TcpDiscoverySpi.setReconnectCount (covered by
IgniteConfiguration.setFailureDetectionTimeout)
TcpDiscoverySpi.setSocketTimeout (covered by
Alexey Popov created IGNITE-6627:
Summary: .NET: cache deserialization fail with complex value type
& enum
Key: IGNITE-6627
URL: https://issues.apache.org/jira/browse/IGNITE-6627
Project: Ig
Alexey Popov created IGNITE-6690:
Summary: DiscoverySpi: Clientmode Ignite should not fail on
handshake errors
Key: IGNITE-6690
URL: https://issues.apache.org/jira/browse/IGNITE-6690
Project: Ignite
Alexey Popov created IGNITE-6876:
Summary: ODBC: Add support for SQL_ATTR_CONNECTION_TIMEOUT
Key: IGNITE-6876
URL: https://issues.apache.org/jira/browse/IGNITE-6876
Project: Ignite
Issue
Alexey Popov created IGNITE-7047:
Summary: NPE at org.jsr166.ConcurrentLinkedHashMap.replace
Key: IGNITE-7047
URL: https://issues.apache.org/jira/browse/IGNITE-7047
Project: Ignite
Issue
Alexey Popov created IGNITE-7191:
Summary: JDBC: set socket buffer to 64k by default
Key: IGNITE-7191
URL: https://issues.apache.org/jira/browse/IGNITE-7191
Project: Ignite
Issue Type
Alexey Popov created IGNITE-7192:
Summary: JDBC: support FQDN to multiple IPs during connection
establishment
Key: IGNITE-7192
URL: https://issues.apache.org/jira/browse/IGNITE-7192
Project: Ignite
Alexey Popov created IGNITE-7247:
Summary: C++: Change default mapper behavior for
BinaryConfiguration
Key: IGNITE-7247
URL: https://issues.apache.org/jira/browse/IGNITE-7247
Project: Ignite
Alexey Popov created IGNITE-7263:
Summary: Daemon-mode Ignite node should not open client
port (10800)
Key: IGNITE-7263
URL: https://issues.apache.org/jira/browse/IGNITE-7263
Project: Ignite
Alexey Popov created IGNITE-6946:
Summary: Change Ignite Logger configuration on the fly
Key: IGNITE-6946
URL: https://issues.apache.org/jira/browse/IGNITE-6946
Project: Ignite
Issue Type
Alexey Popov created IGNITE-6896:
Summary: .NET: support Multidimensional Arrays in binary serializer
Key: IGNITE-6896
URL: https://issues.apache.org/jira/browse/IGNITE-6896
Project: Ignite
Alexey Popov created IGNITE-6907:
Summary: Add LINQ many-to-many test and LINQ with transactions test
Key: IGNITE-6907
URL: https://issues.apache.org/jira/browse/IGNITE-6907
Project: Ignite
Alexey Popov created IGNITE-6955:
Summary: Update
com.google.code.simple-spring-memcached:spymemcached to 2.8.4
Key: IGNITE-6955
URL: https://issues.apache.org/jira/browse/IGNITE-6955
Project: Ignite
Alexey Popov created IGNITE-6971:
Summary: Ignite Logger type & logging file config indication
Key: IGNITE-6971
URL: https://issues.apache.org/jira/browse/IGNITE-6971
Project: Ignite
I
Alexey Popov created IGNITE-6974:
Summary: .NET: consoleWrite error during application shutdown
Key: IGNITE-6974
URL: https://issues.apache.org/jira/browse/IGNITE-6974
Project: Ignite
Issue
Alexey Popov created IGNITE-6828:
Summary: Confusing messages "SLF4J: Failed to load class" at
Ignite start
Key: IGNITE-6828
URL: https://issues.apache.org/jira/browse/IGNITE-6828
Proje
Alexey Popov created IGNITE-6835:
Summary: ODBC driver should handle ungraceful tcp disconnects
Key: IGNITE-6835
URL: https://issues.apache.org/jira/browse/IGNITE-6835
Project: Ignite
Issue
Alexey Popov created IGNITE-7153:
Summary: Redis: BufferUnderflowException at
GridRedisProtocolParser.readBulkStr for values > 8kb
Key: IGNITE-7153
URL: https://issues.apache.org/jira/browse/IGNITE-7
Alexey Popov created IGNITE-7170:
Summary: Fix javadoc MemoryConfiguration (20% instead of 80%)
Key: IGNITE-7170
URL: https://issues.apache.org/jira/browse/IGNITE-7170
Project: Ignite
Issue
Alexey Popov created IGNITE-7627:
Summary: Introduce a new eviction policy to avoid eviction of
Index pages
Key: IGNITE-7627
URL: https://issues.apache.org/jira/browse/IGNITE-7627
Project: Ignite
Alexey Popov created IGNITE-7704:
Summary: Document IgniteConfiguration, TcpDiscoverySpi,
TcpCommunicationSpi timeouts and their relations
Key: IGNITE-7704
URL: https://issues.apache.org/jira/browse/IGNITE-7704
Alexey Popov created IGNITE-7705:
Summary: DIscoverySpi should inherit networkTimeout from
IgniteConfiguration
Key: IGNITE-7705
URL: https://issues.apache.org/jira/browse/IGNITE-7705
Project: Ignite
Alexey Popov created IGNITE-7720:
Summary: Update ODBC cluster configuration: replace
OdbcConfiguration with ClientConnectorConfiguration
Key: IGNITE-7720
URL: https://issues.apache.org/jira/browse/IGNITE-7720
Alexey Popov created IGNITE-7851:
Summary: .NET: linq query throws "Hexadecimal string with odd
number of characters" exception
Key: IGNITE-7851
URL: https://issues.apache.org/jira/browse/I
Alexey Popov created IGNITE-8127:
Summary: .NET: Fix flaky test
ClientConnectionTest.TestClientDisposeWhileOperationsAreInProgress
Key: IGNITE-8127
URL: https://issues.apache.org/jira/browse/IGNITE-8127
Alexey Popov created IGNITE-8108:
Summary: .NET: Fix flaky
EntityFrameworkCacheInitializationTest.TestConfigurationAndStartup
Key: IGNITE-8108
URL: https://issues.apache.org/jira/browse/IGNITE-8108
Alexey Popov created IGNITE-7824:
Summary: Rollback part of IGNITE-7170 changes
Key: IGNITE-7824
URL: https://issues.apache.org/jira/browse/IGNITE-7824
Project: Ignite
Issue Type: Bug
Alexey Popov created IGNITE-7888:
Summary: ODBC: Add support for SQL_ATTR_LOGIN_TIMEOUT
Key: IGNITE-7888
URL: https://issues.apache.org/jira/browse/IGNITE-7888
Project: Ignite
Issue Type
Alexey Popov created IGNITE-7889:
Summary: .NET: linq GroupBy and Where does not work together.
Key: IGNITE-7889
URL: https://issues.apache.org/jira/browse/IGNITE-7889
Project: Ignite
Issue
46 matches
Mail list logo
