[jira] [Created] (IGNITE-11729) Low description for lost policy functional
ARomantsov created IGNITE-11729:
---
Summary: Low description for lost policy functional
Key: IGNITE-11729
URL: https://issues.apache.org/jira/browse/IGNITE-11729
Project: Ignite
Issue Type: Improvement
Components: documentation
Affects Versions: 2.7
Reporter: ARomantsov
Fix For: 3.0, 2.8
Current description in
https://apacheignite.readme.io/docs/partition-loss-policies seems not covered
persistence case and text description is not clean
Probably we need to transform it into two tables (in-memory, persistence)
Rows - cache_write, cache_read, cache_remove,sql_read, sql_write
Columns - READ_ONLY_SAFE ,READ_ONLY_ALL, READ_WRITE_SAFE, etc
{code:java}
Policies
Ignite supports the following PartitionLossPolicies:
READ_ONLY_SAFE - all writes to a cache/table will fail with an exception. Reads
will only be allowed for entries belonging to survived/alive partitions. Reads
from lost partitions will fail with an exception.
READ_ONLY_ALL - reads are allowed from any partition including the lost ones.
An exception is thrown in an attempt to write to any partition. The result of
reading from a lost partition is undefined and may be different on different
nodes in the cluster.
READ_WRITE_SAFE - all reads and writes are allowed for entries in
survived/alive partitions. All reads and writes of entries belonging to the
lost partitions will fail with an exception.
READ_WRITE_ALL - all reads and writes will proceed as if all partitions were in
a consistent state (as if no partition loss happened). The result of reading
from a lost partition is undefined and may be different on different nodes in
the cluster.
IGNORE - this mode never marks a lost partition as lost, pretending that no
partition loss has happened and clearing the partition loss state right away.
Technically, the partition will not be added to the collection of
lostPartitions which is the main difference from READ_WRITE_ALL mode. IGNORE
mode is used by default.
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11322) [USABILITY] Extend Node FAILED message by add consistentId if it exist
ARomantsov created IGNITE-11322: --- Summary: [USABILITY] Extend Node FAILED message by add consistentId if it exist Key: IGNITE-11322 URL: https://issues.apache.org/jira/browse/IGNITE-11322 Project: Ignite Issue Type: Bug Affects Versions: 2.7 Reporter: ARomantsov Fix For: 2.8 Now I having only this [GridDiscoveryManager] Node FAILED: TcpDiscoveryNode [id=f8cd73a1-8da5-4a07-b298-55634dd7c9f8, addrs=ArrayList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, lastExchangeTime=1550141566893, loc=false, isClient=false] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11302) idleConnectionTimeout TcpComm different on server and client (client default > server custom) lead to wait until client timeout on server side
ARomantsov created IGNITE-11302: --- Summary: idleConnectionTimeout TcpComm different on server and client (client default > server custom) lead to wait until client timeout on server side Key: IGNITE-11302 URL: https://issues.apache.org/jira/browse/IGNITE-11302 Project: Ignite Issue Type: Bug Affects Versions: 2.5 Reporter: ARomantsov Fix For: 2.8 Server config: Client config Server wait until default idleConnectionTimeout (10 m) for client fail. If both config with idleConnectionTimeout=1 s - ignite worked according to config -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11263) If host in TcpDiscoveryVmIpFinder is unreachable - server hang on start
ARomantsov created IGNITE-11263:
---
Summary: If host in TcpDiscoveryVmIpFinder is unreachable - server
hang on start
Key: IGNITE-11263
URL: https://issues.apache.org/jira/browse/IGNITE-11263
Project: Ignite
Issue Type: Bug
Affects Versions: 2.5
Reporter: ARomantsov
Fix For: 2.8
If one of servers in discovery ipFinder is unreachable - server hang on start
repeat locally with commands
sudo iptables -A INPUT DROP
sudo iptables -A OUTPUT DROP
{code:java}
{code}
Server logs end with
{code:java}
[14:39:44,668][INFO][main][GridCacheDatabaseSharedManager] Read checkpoint
status [startMarker=null, endMarker=null]
[14:39:44,669][INFO][main][GridCacheDatabaseSharedManager] Applying lost cache
updates since last checkpoint record [lastMarked=FileWALPointer [idx=0,
fileOff=0, len=0], lastCheckpointId=----]
[14:39:44,700][INFO][main][GridCacheDatabaseSharedManager] Finished applying
WAL changes [updatesApplied=0, time=30 ms]
[14:39:44,700][INFO][main][GridCacheDatabaseSharedManager] Restoring partition
state for local groups.
[14:39:44,705][INFO][main][GridCacheDatabaseSharedManager] Finished restoring
partition state for local groups [groupsProcessed11partitionsProcessed=0,
time=10ms]
[14:39:45,252][INFO][main][TcpDiscoverySpi] Successfully bound to TCP port
[port=47500, localHost=0.0.0.0/0.0.0.0,
locNodeId=6621cfd7-26a8-4bc0-a80a-88c6281aa118]
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11243) Not working control.sh / control.bat in master NPE in output
ARomantsov created IGNITE-11243: --- Summary: Not working control.sh / control.bat in master NPE in output Key: IGNITE-11243 URL: https://issues.apache.org/jira/browse/IGNITE-11243 Project: Ignite Issue Type: Bug Affects Versions: 2.8 Reporter: ARomantsov Fix For: 2.8 ./bin/control.sh --host --port --baseline Cluster state: active Error: java.lang.NullPointerException control.bat --host --port --baseline Cluster state: active Error: java.lang.NullPointerException Press any key to continue . . . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11217) After cluster kill and restart with new jvm option - one of node fail with failure type - Failed to read WAL record at position
ARomantsov created IGNITE-11217:
---
Summary: After cluster kill and restart with new jvm option - one
of node fail with failure type - Failed to read WAL record at position
Key: IGNITE-11217
URL: https://issues.apache.org/jira/browse/IGNITE-11217
Project: Ignite
Issue Type: Bug
Components: data structures
Affects Versions: 2.7
Reporter: ARomantsov
Fix For: 2.8
Test scenario:
- Start two server load
- execute operations (put/put-all/streamer/remove)
- execute client that collect checksum
- kill nodes
- add JVM options to server - DIGNITE_WAL_LOG_TX_RECORDS=true,
DIGNITE_RECOVERY_VERBOSE_LOGGING
- start nodes
- activate them
Found that one node fail
{code:java}
[23:16:06,230][INFO][main][GridCacheProcessor] Finished restoring partition
state for local groups [groupsProcessed=45, partitionsProcessed=764, time=557ms]
[23:16:06,280][INFO][main][FileWriteAheadLogManager] Stopping WAL iteration due
to an exception: Failed to read WAL record at position: 27700852 size:
67108864, ptr=FileWALPointer [idx=0, fileOff=27700852, len=0]
[23:16:06,298][SEVERE][main][IgniteKernal] Exception during start processors,
node will be stopped and close connections
class org.apache.ignite.IgniteCheckedException: Failed to read WAL record at
position: 27700852 size: 67108864
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.handleRecordException(AbstractWalRecordsIterator.java:305)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$RecordsIterator.handleRecordException(FileWriteAheadLogManager.java:2691)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:269)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:158)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:127)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:53)
at
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.tailPointer(GridCacheDatabaseSharedManager.java:1984)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.startMemoryRestore(GridCacheDatabaseSharedManager.java:1958)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1050)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2040)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1732)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
at org.apache.ignite.Ignition.start(Ignition.java:348)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to read WAL
record at position: 27700852 size: 67108864
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readWithCrc(RecordV1Serializer.java:395)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV2Serializer.readRecord(RecordV2Serializer.java:236)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:254)
... 17 more
Caused by: java.io.IOException: class org.apache.ignite.IgniteCheckedException:
Unsupported protocol version: 34
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV1Serializer.readVersion(RecordDataV1Serializer.java:2010)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV2Serializer.readMvccDataEntry(RecordDataV2Serializer.java:328)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV2Serializer.readPlainRecord(RecordDataV2Serializer.java:162)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordDataV1Serializer.readRecord(RecordDataV1Serializer.java:208)
at
[jira] [Created] (IGNITE-11184) add example of ssl rest protocol on ignite
ARomantsov created IGNITE-11184: --- Summary: add example of ssl rest protocol on ignite Key: IGNITE-11184 URL: https://issues.apache.org/jira/browse/IGNITE-11184 Project: Ignite Issue Type: Bug Components: documentation Affects Versions: 2.7 Reporter: ARomantsov Fix For: 2.8 Add information about ssl Jetty configuration to ignite documentation about restApi https://apacheignite.readme.io/docs/rest-api#sample-jetty-xml-configuration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11179) One of two nodes fail by handler with message - threadName=ttl-cleanup-worker, blockedFor=16s
ARomantsov created IGNITE-11179: --- Summary: One of two nodes fail by handler with message - threadName=ttl-cleanup-worker, blockedFor=16s Key: IGNITE-11179 URL: https://issues.apache.org/jira/browse/IGNITE-11179 Project: Ignite Issue Type: Bug Reporter: ARomantsov Start two nodes, one of them drop after Start caches in recovery mode -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11103) "Control utility --cache idle_verify --dump --cache-filter ALL" comand result doesn't contain ignite-sys-cache group
ARomantsov created IGNITE-11103: --- Summary: "Control utility --cache idle_verify --dump --cache-filter ALL" comand result doesn't contain ignite-sys-cache group Key: IGNITE-11103 URL: https://issues.apache.org/jira/browse/IGNITE-11103 Project: Ignite Issue Type: Bug Reporter: ARomantsov Look at functional add in https://issues.apache.org/jira/browse/IGNITE-9980 and find that issue -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10975) when ssl not correct configurate make cu error more undestandable
ARomantsov created IGNITE-10975: --- Summary: when ssl not correct configurate make cu error more undestandable Key: IGNITE-10975 URL: https://issues.apache.org/jira/browse/IGNITE-10975 Project: Ignite Issue Type: Bug Reporter: ARomantsov Now CU return Connection to cluster failed. Error: Latest topology update failed this error also appear when you try to connect on unexist cluster , at that point gain it with bad ssl that add little bit confusion -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10938) After restart cluster with non-blt nodes - they left by handler
ARomantsov created IGNITE-10938: --- Summary: After restart cluster with non-blt nodes - they left by handler Key: IGNITE-10938 URL: https://issues.apache.org/jira/browse/IGNITE-10938 Project: Ignite Issue Type: Bug Components: data structures Affects Versions: 2.8 Reporter: ARomantsov Fix For: 2.8 I have cluster wherein topology contain blt and non-blt nodes, but after restart - nodes left by handler java.lang.IllegalStateException: Unable to find consistentId by UUID -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10929) After huge load on cluster and restart with walCompactionEnabled=True warning on log
ARomantsov created IGNITE-10929:
---
Summary: After huge load on cluster and restart with
walCompactionEnabled=True warning on log
Key: IGNITE-10929
URL: https://issues.apache.org/jira/browse/IGNITE-10929
Project: Ignite
Issue Type: Bug
Affects Versions: 2.5
Reporter: ARomantsov
Fix For: 2.8
{code:java}
[15:08:14,610][WARNING][wal-file-compressor-%null%-3-#70][FileWriteAheadLogManager]
Failed to remove obsolete WAL segment (make sure the process has enough
rights): my_path/work/db/wal/archive/node_1_1/0001.wal, exists:
false
[15:08:15,661][WARNING][wal-file-compressor-%null%-0-#66][FileWriteAheadLogManager]
Failed to remove obsolete WAL segment (make sure the process has enough
rights): my_path/work/db/wal/archive/node_1_1/0005.wal, exists:
false
[15:08:16,540][WARNING][wal-file-compressor-%null%-2-#69][FileWriteAheadLogManager]
Failed to remove obsolete WAL segment (make sure the process has enough
rights): my_path/work/db/wal/archive/node_1_1/0009.wal, exists:
false
[15:08:17,354][WARNING][wal-file-compressor-%null%-1-#68][FileWriteAheadLogManager]
Failed to remove obsolete WAL segment (make sure the process has enough
rights): my_path/work/db/wal/archive/node_1_1/0013.wal, exists:
false
[15:08:18,161][WARNING][wal-file-compressor-%null%-1-#68][FileWriteAheadLogManager]
Failed to remove obsolete WAL segment (make sure the process has enough
rights): my_path/work/db/wal/archive/node_1_1/0017.wal, exists:
false
[15:08:18,161][WARNING][wal-file-compressor-%null%-2-#69][FileWriteAheadLogManager]
Failed to remove obsolete WAL segment (make sure the process has enough
rights): my_path/work/db/wal/archive/node_1_1/0017.wal, exists:
false
[15:08:18,161][WARNING][wal-file-compressor-%null%-2-#69][FileWriteAheadLogManager]
Failed to remove obsolete WAL segment (make sure the process has enough
rights): my_path/work/db/wal/archive/node_1_1/0018.wal, exists:
false
[15:08:18,987][WARNING][wal-file-compressor-%null%-3-#70][FileWriteAheadLogManager]
Failed to remove obsolete WAL segment (make sure the process has enough
rights): my_path/work/db/wal/archive/node_1_1/0020.wal, exists:
false
[15:08:18,987][WARNING][wal-file-compressor-%null%-2-#69][FileWriteAheadLogManager]
Failed to remove obsolete WAL segment (make sure the process has enough
rights): my_path/work/db/wal/archive/node_1_1/0020.wal, exists:
false
[15:08:18,998][WARNING][wal-file-compressor-%null%-2-#69][FileWriteAheadLogManager]
Failed to remove obsolete WAL segment (make sure the process has enough
rights): my_path/work/db/wal/archive/node_1_1/0023.wal, exists:
false
[15:08:23,211][WARNING][wal-file-compressor-%null%-2-#69][FileWriteAheadLogManager]
Failed to remove obsolete WAL segment (make sure the process has enough
rights): my_path/work/db/wal/archive/node_1_1/0028.wal, exists:
false
[15:08:23,211][WARNING][wal-file-compressor-%null%-3-#70][FileWriteAheadLogManager]
Failed to remove obsolete WAL segment (make sure the process has enough
rights): my_path/work/db/wal/archive/node_1_1/0029.wal, exists:
false
[15:08:24,264][WARNING][wal-file-compressor-%null%-0-#66][FileWriteAheadLogManager]
Failed to remove obsolete WAL segment (make sure the process has enough
rights): my_path/work/db/wal/archive/node_1_1/0033.wal, exists:
false
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10928) After huge load on cluster and restart with walCompactionEnabled=True errors on log
ARomantsov created IGNITE-10928:
---
Summary: After huge load on cluster and restart with
walCompactionEnabled=True errors on log
Key: IGNITE-10928
URL: https://issues.apache.org/jira/browse/IGNITE-10928
Project: Ignite
Issue Type: Bug
Reporter: ARomantsov
{code:java}
{code}
{code:java}
[15:30:56,809][INFO][wal-file-compressor-%null%-1-#68][FileWriteAheadLogManager]
Stopping WAL iteration due to an exception: Failed to read WAL record at
position: 28310114 size: -1, ptr=FileWALPointer [idx=35, fileOff=28310114,
len=0]
[15:30:56,811][INFO][wal-file-compressor-%null%-3-#70][FileWriteAheadLogManager]
Stopping WAL iteration due to an exception: Failed to read WAL record at
position: 28303753 size: -1, ptr=FileWALPointer [idx=36, fileOff=28303753,
len=0]
[15:30:56,811][SEVERE][wal-file-compressor-%null%-1-#68][FileWriteAheadLogManager]
Compression of WAL segment [idx=35] was skipped due to unexpected error
class org.apache.ignite.IgniteCheckedException: Failed to read WAL record at
position: 28310114 size: -1
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.handleRecordException(AbstractWalRecordsIterator.java:292)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:258)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:154)
at
org.apache.ignite.internal.processors.cache.persistence.wal.SingleSegmentLogicalRecordsIterator.advance(SingleSegmentLogicalRecordsIterator.java:119)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:123)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:52)
at
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.compressSegmentToFile(FileWriteAheadLogManager.java:2039)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body0(FileWriteAheadLogManager.java:1974)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body(FileWriteAheadLogManager.java:1950)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to read WAL
record at position: 28310114 size: -1
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readWithCrc(RecordV1Serializer.java:394)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV2Serializer.readRecord(RecordV2Serializer.java:235)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:243)
... 10 more
Caused by: java.nio.channels.ClosedByInterruptException
at
java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
at sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:164)
at
org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIO.read(RandomAccessFileIO.java:58)
at
org.apache.ignite.internal.processors.cache.persistence.file.FileIODecorator.read(FileIODecorator.java:51)
at
org.apache.ignite.internal.processors.cache.persistence.wal.io.SimpleFileInput.ensure(SimpleFileInput.java:119)
at
org.apache.ignite.internal.processors.cache.persistence.wal.io.FileInput$Crc32CheckingFileInput.ensure(FileInput.java:89)
at
org.apache.ignite.internal.processors.cache.persistence.wal.io.FileInput$Crc32CheckingFileInput.readFully(FileInput.java:152)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV2Serializer$2.readWithHeaders(RecordV2Serializer.java:149)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readWithCrc(RecordV1Serializer.java:373)
... 12 more
Suppressed: class
org.apache.ignite.internal.processors.cache.persistence.wal.crc.IgniteDataIntegrityViolationException:
val: 1241861030 writtenCrc: 20736
at
org.apache.ignite.internal.processors.cache.persistence.wal.io.FileInput$Crc32CheckingFileInput.close(FileInput.java:106)
[jira] [Created] (IGNITE-10911) Need to enforce truststore key when control utility connect to cluster with SSL enabled
ARomantsov created IGNITE-10911:
---
Summary: Need to enforce truststore key when control utility
connect to cluster with SSL enabled
Key: IGNITE-10911
URL: https://issues.apache.org/jira/browse/IGNITE-10911
Project: Ignite
Issue Type: Bug
Affects Versions: 2.5
Reporter: ARomantsov
Fix For: 2.8
I use the next setting in my app
{code:java}
{code}
And can get the result of command - control.bat --baseline
--keystore..\server.jks --keystore-password * without set up truststore
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10896) Add ability to use more than one key with control.sh --cache idle_verify
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: Ignite Issue Type: Improvement Reporter: ARomantsov Now I can use only one of next options 1) --exclude-caches cache1,...,cacheN or 2) --cache-filter ALL|SYSTEM|PERSISTENT|NOT_PERSISTENT 3) cache1,...,cacheN I suppose that using 1 and 2 or 2 and 3 make this command more flexiable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10825) After node restart and and new node to BLT due load - some partition inconsistent
ARomantsov created IGNITE-10825: --- Summary: After node restart and and new node to BLT due load - some partition inconsistent Key: IGNITE-10825 URL: https://issues.apache.org/jira/browse/IGNITE-10825 Project: Ignite Issue Type: Bug Components: data structures Affects Versions: 2.8 Reporter: ARomantsov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10772) If version look like X.X.X.X rest version return X.X.X-X
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
Issue Type: Bug
Components: rest
Affects Versions: 2.8
Reporter: ARomantsov
Fix For: 2.8
Test URL - http://localhost:8080/ignite?cmd=version
{
"result": {
"error": null,
"response": "X.X.X-X",
"sessionToken": "D372FC2DD4A24603AC39CC92C6B132EC",
"successStatus": 0
},
"status": "OK"
}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10744) class org.apache.ignite.IgniteCheckedException: Failed to read WAL record at position: 5237375 size: -1
ARomantsov created IGNITE-10744:
---
Summary: class org.apache.ignite.IgniteCheckedException: Failed to
read WAL record at position: 5237375 size: -1
Key: IGNITE-10744
URL: https://issues.apache.org/jira/browse/IGNITE-10744
Project: Ignite
Issue Type: Bug
Components: data structures
Affects Versions: 2.8
Reporter: ARomantsov
Fix For: 2.8
Scenario:
-Start 4 nodes with disc storage
-Little load
-Deactivate
-Activate
Got next message in log
{code:java}
[20:54:42,746][INFO][wal-file-compressor-%null%-3-#70][FileWriteAheadLogManager]
Stopping WAL iteration due to an exception: Failed to read WAL record at
position: 5237375 size: -1, ptr=FileWALPointer [idx=4, fileOff=5237375, len=0]
[20:54:42,747][SEVERE][wal-file-compressor-%null%-3-#70][FileWriteAheadLogManager]
Compression of WAL segment [idx=4] was skipped due to unexpected error
class org.apache.ignite.IgniteCheckedException: Failed to read WAL record at
position: 5237375 size: -1
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.handleRecordException(AbstractWalRecordsIterator.java:294)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:258)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:154)
at
org.apache.ignite.internal.processors.cache.persistence.wal.SingleSegmentLogicalRecordsIterator.advance(SingleSegmentLogicalRecordsIterator.java:119)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:123)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:52)
at
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.compressSegmentToFile(FileWriteAheadLogManager.java:2186)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body0(FileWriteAheadLogManager.java:2111)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body(FileWriteAheadLogManager.java:2081)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to read WAL
record at position: 5237375 size: -1
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readWithCrc(RecordV1Serializer.java:394)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV2Serializer.readRecord(RecordV2Serializer.java:235)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:243)
... 10 more
Caused by: java.nio.channels.ClosedByInterruptException
at
java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
at sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:164)
at
org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIO.read(RandomAccessFileIO.java:58)
at
org.apache.ignite.internal.processors.cache.persistence.file.FileIODecorator.read(FileIODecorator.java:51)
at
org.apache.ignite.internal.processors.cache.persistence.wal.io.SimpleFileInput.ensure(SimpleFileInput.java:119)
at
org.apache.ignite.internal.processors.cache.persistence.wal.io.FileInput$Crc32CheckingFileInput.ensure(FileInput.java:89)
at
org.apache.ignite.internal.processors.cache.persistence.wal.io.FileInput$Crc32CheckingFileInput.skipBytes(FileInput.java:130)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV2Serializer$2.readWithHeaders(RecordV2Serializer.java:130)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readWithCrc(RecordV1Serializer.java:373)
... 12 more
Suppressed: class
org.apache.ignite.internal.processors.cache.persistence.wal.crc.IgniteDataIntegrityViolationException:
val: 505117685 writtenCrc: 0
at
org.apache.ignite.internal.processors.cache.persistence.wal.io.FileInput$Crc32CheckingFileInput.close(FileInput.java:106)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readWithCrc(RecordV1Serializer.java:380)
... 12 more
{code}
--
This
[jira] [Created] (IGNITE-10669) NPE in freelist.PagesList.findTailIndex
ARomantsov created IGNITE-10669:
---
Summary: NPE in freelist.PagesList.findTailIndex
Key: IGNITE-10669
URL: https://issues.apache.org/jira/browse/IGNITE-10669
Project: Ignite
Issue Type: Bug
Components: data structures
Affects Versions: 2.7
Environment: Windows
Reporter: ARomantsov
Fix For: 2.8
{code:java}
[22:40:10,916][INFO][main][GridCacheDatabaseSharedManager] Applying lost cache
updates since last checkpoint record [lastMarked=FileWALPointer [idx=2,
fileOff=14706, len=21409],
lastCheckpointId=2f9202e9-c9d7-47ca-9dcc-299a959bb2e0]
[22:40:10,922][SEVERE][main][IgniteKernal] Exception during start processors,
node will be stopped and close connections
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.findTailIndex(PagesList.java:502)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.updateTail(PagesList.java:458)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.mergeNoNext(PagesList.java:1330)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.removeDataPage(PagesList.java:1281)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.AbstractFreeList$RemoveRowHandler.run(AbstractFreeList.java:305)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.AbstractFreeList$RemoveRowHandler.run(AbstractFreeList.java:261)
at
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:279)
at
org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:256)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.AbstractFreeList.removeDataRowByLink(AbstractFreeList.java:571)
at
org.apache.ignite.internal.processors.cache.persistence.metastorage.MetastorageRowStore.removeRow(MetastorageRowStore.java:57)
at
org.apache.ignite.internal.processors.cache.persistence.metastorage.MetaStorage.putData(MetaStorage.java:253)
at
org.apache.ignite.internal.processors.cache.persistence.metastorage.MetaStorage.applyUpdate(MetaStorage.java:492)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLogicalUpdates(GridCacheDatabaseSharedManager.java:2420)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.startMemoryRestore(GridCacheDatabaseSharedManager.java:1909)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1056)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2040)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1732)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
at org.apache.ignite.Ignition.start(Ignition.java:348)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
[22:40:10,922][SEVERE][main][IgniteKernal] Got exception while starting (will
rollback startup routine).
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.findTailIndex(PagesList.java:502)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.updateTail(PagesList.java:458)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.mergeNoNext(PagesList.java:1330)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.removeDataPage(PagesList.java:1281)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.AbstractFreeList$RemoveRowHandler.run(AbstractFreeList.java:305)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.AbstractFreeList$RemoveRowHandler.run(AbstractFreeList.java:261)
at
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:279)
at
org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:256)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.AbstractFreeList.removeDataRowByLink(AbstractFreeList.java:571)
at
[jira] [Created] (IGNITE-10664) need to make identical the behavior of control.sh and control.bat
ARomantsov created IGNITE-10664: --- Summary: need to make identical the behavior of control.sh and control.bat Key: IGNITE-10664 URL: https://issues.apache.org/jira/browse/IGNITE-10664 Project: Ignite Issue Type: Bug Components: clients Affects Versions: 2.7 Environment: windows, nix Reporter: ARomantsov Fix For: 2.8 Now control.bat contain next line: if not "%NO_PAUSE%" == "1" pause and after execution it ready to press button. on the other hand - control.sh not contain any pause -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10504) If client have cache resource with not configurate data region it stop by handler
ARomantsov created IGNITE-10504: --- Summary: If client have cache resource with not configurate data region it stop by handler Key: IGNITE-10504 URL: https://issues.apache.org/jira/browse/IGNITE-10504 Project: Ignite Issue Type: Bug Affects Versions: 2.7 Reporter: ARomantsov Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10477) An empty cluster falls if wal segment size small
ARomantsov created IGNITE-10477:
---
Summary: An empty cluster falls if wal segment size small
Key: IGNITE-10477
URL: https://issues.apache.org/jira/browse/IGNITE-10477
Project: Ignite
Issue Type: Bug
Components: data structures
Affects Versions: 2.7
Reporter: ARomantsov
Fix For: 2.8
I set and try to activate
empty cluster.
Get cluster drop by handler and next error
{code:java}
[15:45:12,723][SEVERE][db-checkpoint-thread-#99][] Critical system error
detected. Will be handled accordingly to configured handler [hnd=class
o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext
[type=SYSTEM_WORKER_TE
RMINATION, err=java.lang.IllegalArgumentException: Record is too long
[capacity=100, size=1802204]]]
java.lang.IllegalArgumentException: Record is too long [capacity=100,
size=1802204]
at
org.apache.ignite.internal.processors.cache.persistence.wal.SegmentedRingByteBuffer.offer0(SegmentedRingByteBuffer.java:214)
at
org.apache.ignite.internal.processors.cache.persistence.wal.SegmentedRingByteBuffer.offer(SegmentedRingByteBuffer.java:193)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.addRecord(FileWriteAheadLogManager.java:2472)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.access$1600(FileWriteAheadLogManager.java:2376)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.log(FileWriteAheadLogManager.java:821)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:3604)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:3091)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:2990)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10446) control.sh --cache idle_verify fail with NPE when node left grid
ARomantsov created IGNITE-10446: --- Summary: control.sh --cache idle_verify fail with NPE when node left grid Key: IGNITE-10446 URL: https://issues.apache.org/jira/browse/IGNITE-10446 Project: Ignite Issue Type: Bug Affects Versions: 2.7 Reporter: ARomantsov Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10404) Handler stop node with reason - IgniteException: Checkpoint read lock acquisition has been timed out
ARomantsov created IGNITE-10404: --- Summary: Handler stop node with reason - IgniteException: Checkpoint read lock acquisition has been timed out Key: IGNITE-10404 URL: https://issues.apache.org/jira/browse/IGNITE-10404 Project: Ignite Issue Type: Bug Reporter: ARomantsov I now about possible WA - set readLockCheckpointTimeout to zero, but it make product unstable, sometimes I forget this option and my cluster totally broken when I try to load -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10402) Restart cluster with BLT led to loss of node due to AE
ARomantsov created IGNITE-10402:
---
Summary: Restart cluster with BLT led to loss of node due to AE
Key: IGNITE-10402
URL: https://issues.apache.org/jira/browse/IGNITE-10402
Project: Ignite
Issue Type: Bug
Components: data structures
Affects Versions: 2.8
Reporter: ARomantsov
Fix For: 2.8
{code:java}
[23:44:47,616][SEVERE][sys-#88][] Critical system error detected. Will be
handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler
[tryStop=false, timeout=0, super=AbstractFailureHandler
[ignoredFailureTypes=Singleton
Set [SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext [type=CRITICAL_ERROR,
err=java.lang.AssertionError]]
java.lang.AssertionError
at
org.gridgain.grid.internal.processors.cache.database.GridSnapshotAwareClusterStateProcessorImpl$3.apply(GridSnapshotAwareClusterStateProcessorImpl.java:291)
at
org.gridgain.grid.internal.processors.cache.database.GridSnapshotAwareClusterStateProcessorImpl$3.apply(GridSnapshotAwareClusterStateProcessorImpl.java:270)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:2183)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3497)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:3208)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2809)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:141)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2614)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2602)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:355)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceiveSingleMessage(GridDhtPartitionsExchangeFuture.java:2602)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1839)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1200(GridCachePartitionExchangeManager.java:146)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:386)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:344)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3334)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:3313)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1061)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:586)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:385)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:311)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:101)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:300)
at
[jira] [Created] (IGNITE-10401) After node join and rebalance - some partition hang in move state
ARomantsov created IGNITE-10401: --- Summary: After node join and rebalance - some partition hang in move state Key: IGNITE-10401 URL: https://issues.apache.org/jira/browse/IGNITE-10401 Project: Ignite Issue Type: Bug Components: data structures Affects Versions: 2.7 Reporter: ARomantsov Fix For: 2.8 I try to kill three nodes and return them back after some load time They begin to rebalance, but one host eventually have many MOVING partition and they not become owning after PME -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10400) Server node stop by handler IgniteException: Failed to resolve node topology
ARomantsov created IGNITE-10400: --- Summary: Server node stop by handler IgniteException: Failed to resolve node topology Key: IGNITE-10400 URL: https://issues.apache.org/jira/browse/IGNITE-10400 Project: Ignite Issue Type: Bug Reporter: ARomantsov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10395) Add to control.sh --cache --tx overall info:
ARomantsov created IGNITE-10395: --- Summary: Add to control.sh --cache --tx overall info: Key: IGNITE-10395 URL: https://issues.apache.org/jira/browse/IGNITE-10395 Project: Ignite Issue Type: Bug Reporter: ARomantsov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10394) Try to activate cluster after deactivate. All node exit by handler
ARomantsov created IGNITE-10394: --- Summary: Try to activate cluster after deactivate. All node exit by handler Key: IGNITE-10394 URL: https://issues.apache.org/jira/browse/IGNITE-10394 Project: Ignite Issue Type: Bug Components: data structures Affects Versions: 2.7 Reporter: ARomantsov AE: ignite-sys-cache ..processors.cache.CacheRegistry.update(CacheRegistry.java:188) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10327) Claster take NPE due cache stop and stop by handler
ARomantsov created IGNITE-10327: --- Summary: Claster take NPE due cache stop and stop by handler Key: IGNITE-10327 URL: https://issues.apache.org/jira/browse/IGNITE-10327 Project: Ignite Issue Type: Bug Components: data structures Affects Versions: 2.8 Reporter: ARomantsov Fix For: 2.7 Stop all caches Take NPE : null on preloadEntry(GridDhtPartitionDemander.java:893) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10323) Contol utility --deactivate on non-activate cluster produse NPE and handler stop nodes
ARomantsov created IGNITE-10323: --- Summary: Contol utility --deactivate on non-activate cluster produse NPE and handler stop nodes Key: IGNITE-10323 URL: https://issues.apache.org/jira/browse/IGNITE-10323 Project: Ignite Issue Type: Bug Components: persistence Affects Versions: 2.7 Reporter: ARomantsov Fix For: 2.8 Scenario: 1) Start cluster 2) Call control.sh --deactivate -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10313) Long exchange on deactivation process
ARomantsov created IGNITE-10313: --- Summary: Long exchange on deactivation process Key: IGNITE-10313 URL: https://issues.apache.org/jira/browse/IGNITE-10313 Project: Ignite Issue Type: Bug Affects Versions: 2.7 Environment: 16 host, 1 server node per host Reporter: ARomantsov Fix For: 2.8 Long exhange after start deactivation process - near to three minutes. Probably in doesn't end, but control.sh return to control to console and I stop cluster -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10205) add to utility command - ./control.sh --cache idle_verify --dump abbility to exclude cache from output file
ARomantsov created IGNITE-10205: --- Summary: add to utility command - ./control.sh --cache idle_verify --dump abbility to exclude cache from output file Key: IGNITE-10205 URL: https://issues.apache.org/jira/browse/IGNITE-10205 Project: Ignite Issue Type: Improvement Reporter: ARomantsov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10134) control.sh --cache list . --config not working on big cache setup
ARomantsov created IGNITE-10134:
---
Summary: control.sh --cache list . --config not working on big
cache setup
Key: IGNITE-10134
URL: https://issues.apache.org/jira/browse/IGNITE-10134
Project: Ignite
Issue Type: Bug
Reporter: ARomantsov
{code:java}
[17:09:31,352][SEVERE][mgmt-#271][GridTaskWorker] Failed to reduce job results
due to undeclared user exception
[task=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask@22c7b357,
err=java.lang.AssertionError]
java.lang.AssertionError
at
org.apache.ignite.internal.visor.VisorOneNodeTask.reduce0(VisorOneNodeTask.java:30)
at
org.apache.ignite.internal.visor.VisorMultiNodeTask.reduce(VisorMultiNodeTask.java:139)
at
org.apache.ignite.internal.processors.task.GridTaskWorker$6.call(GridTaskWorker.java:1133)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6726)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1131)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:958)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1104)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1339)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
[17:09:31,354][SEVERE][mgmt-#271][GridTaskCommandHandler] Failed to execute
task [name=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask,
clientId=606bf232-20e0-4799-bfb1-8d6e44b0d1ad]
class org.apache.ignite.IgniteCheckedException: Failed to reduce job results
due to undeclared user exception
[task=org.apache.ignite.internal.visor.cache.VisorCacheConfigurationCollectorTask@22c7b357,
err=java.lang.AssertionError]
at
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7338)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:171)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
at
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:263)
at
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:257)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(GridTaskWorker.java:1617)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(GridTaskWorker.java:1585)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1175)
at
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:958)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1104)
at
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1339)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
at
[jira] [Created] (IGNITE-10065) possibility to get EVT_CACHE_STARTED before cache proxy initialization
ARomantsov created IGNITE-10065: --- Summary: possibility to get EVT_CACHE_STARTED before cache proxy initialization Key: IGNITE-10065 URL: https://issues.apache.org/jira/browse/IGNITE-10065 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.7 Reporter: ARomantsov Fix For: 2.8 It looks , I can take EVT_CACHE_STARTED before take message - Finish proxy initialization, cacheName=cache -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9994) idle_verify -analyze -partId= -grpId=(minus)number not working
ARomantsov created IGNITE-9994: -- Summary: idle_verify -analyze -partId= -grpId=(minus)number not working Key: IGNITE-9994 URL: https://issues.apache.org/jira/browse/IGNITE-9994 Project: Ignite Issue Type: Bug Affects Versions: 2.6 Reporter: ARomantsov If enter command with plus -grpId - it working -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9992) Add some command to calculate hast sum per primary partition in product
ARomantsov created IGNITE-9992: -- Summary: Add some command to calculate hast sum per primary partition in product Key: IGNITE-9992 URL: https://issues.apache.org/jira/browse/IGNITE-9992 Project: Ignite Issue Type: Improvement Affects Versions: 2.7 Reporter: ARomantsov Some util to quick check cluster data is ok -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9980) Modify ./control.sh --cache idle_verify --dump to print only persistante cache or add flag --persistentOnly
ARomantsov created IGNITE-9980: -- Summary: Modify ./control.sh --cache idle_verify --dump to print only persistante cache or add flag --persistentOnly Key: IGNITE-9980 URL: https://issues.apache.org/jira/browse/IGNITE-9980 Project: Ignite Issue Type: Bug Affects Versions: 2.6 Reporter: ARomantsov It will be cool , if control.sh --cache idle_verify can show persistent/not-persistent/both caches and it will be impliments due utility flag -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9867) Add ability to block out of range IP on discovery request
ARomantsov created IGNITE-9867:
--
Summary: Add ability to block out of range IP on discovery request
Key: IGNITE-9867
URL: https://issues.apache.org/jira/browse/IGNITE-9867
Project: Ignite
Issue Type: Improvement
Components: general
Affects Versions: 2.7
Reporter: ARomantsov
Fix For: 2.8
Now we can set list of cluster collector node, but cannot deny another ips to
connect to our cluster
{code:java}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9827) Assertion error due historical rebalance
ARomantsov created IGNITE-9827: -- Summary: Assertion error due historical rebalance Key: IGNITE-9827 URL: https://issues.apache.org/jira/browse/IGNITE-9827 Project: Ignite Issue Type: Bug Components: persistence Affects Versions: 2.7 Reporter: ARomantsov Fix For: 2.8 I work with next situation 1) Start two nodes with '-DIGNITE_PDS_WAL_REBALANCE_THRESHOLD=0', 2) Preload 3) Stop node 2 4) Load 5) Corrupt all wal archive file in node 1 5) Start node 2 And found assertion in log coordinator - is it ok? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9753) Control.sh validate index work long and with errors
ARomantsov created IGNITE-9753: -- Summary: Control.sh validate index work long and with errors Key: IGNITE-9753 URL: https://issues.apache.org/jira/browse/IGNITE-9753 Project: Ignite Issue Type: Bug Components: general Affects Versions: 2.5 Reporter: ARomantsov Fix For: 2.8 Errors - [12:19:54][:666] IndexValidationIssue [key=null, cacheName=cache_name_1, idxName=_key_PK_hash], class java.lang.NullPointerException: null [12:19:54][:666] IndexValidationIssue [key=null, cacheName=cache_name_2, idxName=_key_PK_hash], class java.lang.NullPointerException: null -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9708) Node didn't detect corrup of file index.bin in FS
ARomantsov created IGNITE-9708: -- Summary: Node didn't detect corrup of file index.bin in FS Key: IGNITE-9708 URL: https://issues.apache.org/jira/browse/IGNITE-9708 Project: Ignite Issue Type: Bug Components: persistence Affects Versions: 2.5 Reporter: ARomantsov Fix For: 2.7 I run two tests In first, i break part.bin file and node correctly find that In second, i break index.bin file and all command (select, idle_verify, etc) not detected problem with it. All corrupts run on correct stop node, and checks after node start -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9430) Add ability to override all caches's "rebalanceThrottle" option via JVM node option
ARomantsov created IGNITE-9430: -- Summary: Add ability to override all caches's "rebalanceThrottle" option via JVM node option Key: IGNITE-9430 URL: https://issues.apache.org/jira/browse/IGNITE-9430 Project: Ignite Issue Type: Improvement Components: general Affects Versions: 2.5 Reporter: ARomantsov Fix For: 2.7 I found ability to set rebalanceThrottle option for any cache , but can we have JVM key for override that parameter for all cache at once -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9325) Add to all command-line utility ability to make sound after complite execution
ARomantsov created IGNITE-9325: -- Summary: Add to all command-line utility ability to make sound after complite execution Key: IGNITE-9325 URL: https://issues.apache.org/jira/browse/IGNITE-9325 Project: Ignite Issue Type: Improvement Components: examples Affects Versions: 2.5 Reporter: ARomantsov Fix For: 2.7 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9255) -DIGNITE_QUIET=false not work in windows, -v work ok
ARomantsov created IGNITE-9255: -- Summary: -DIGNITE_QUIET=false not work in windows, -v work ok Key: IGNITE-9255 URL: https://issues.apache.org/jira/browse/IGNITE-9255 Project: Ignite Issue Type: Bug Components: general Affects Versions: 2.5 Reporter: ARomantsov Fix For: 2.7 I try to run 1) Ignite.bat - Work anticipated 2) Ignite.bat -v - Work anticipated 3) Ignite.bat -J-DIGNITE_QUIET=false - Work like first , but expected like second variant -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9198) REST command active/inactive respone null, other command have correct response value
ARomantsov created IGNITE-9198:
--
Summary: REST command active/inactive respone null, other command
have correct response value
Key: IGNITE-9198
URL: https://issues.apache.org/jira/browse/IGNITE-9198
Project: Ignite
Issue Type: Bug
Components: rest
Affects Versions: 2.5
Reporter: ARomantsov
Fix For: 2.7
Output of active/inactive should have response value like other command
For example version
{
"result": {
"error": null,
*"response": "2.5.1-p9",*
"sessionToken": "CE2C38BF41114B63856A4D1388E7F938",
"successStatus": 0
},
"status": "OK"
}
But active
{
"result": {
"error": null,
*"response": null,* , should be - cluster active
"sessionToken": "CE2C38BF41114B63856A4D1388E7F938",
"successStatus": 0
},
"status": "OK"
}
and inactive
{
"result": {
"error": null,
*"response": null,* , should be - cluster inactive
"sessionToken": "CE2C38BF41114B63856A4D1388E7F938",
"successStatus": 0
},
"status": "OK"
}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9147) When server node left cluster on high load, cluster take hang on PartitionalExchange
ARomantsov created IGNITE-9147: -- Summary: When server node left cluster on high load, cluster take hang on PartitionalExchange Key: IGNITE-9147 URL: https://issues.apache.org/jira/browse/IGNITE-9147 Project: Ignite Issue Type: Bug Components: general Affects Versions: 2.5 Reporter: ARomantsov Fix For: 2.7 I ran a simple test 1) Start 15 servers node 2) Start client with long transaction 3) Additional start 5 client with loading in many caches (near 2 thousand) 4) Stop 1 server node, wait 1 minute and start it back Cluster freenze on more than hour, then license end -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9090) When client node make cache.QueryCursorImpl.getAll they have OOM and continue working
ARomantsov created IGNITE-9090:
--
Summary: When client node make cache.QueryCursorImpl.getAll they
have OOM and continue working
Key: IGNITE-9090
URL: https://issues.apache.org/jira/browse/IGNITE-9090
Project: Ignite
Issue Type: Bug
Affects Versions: 2.4
Environment: 2 server node, 1 client
Reporter: ARomantsov
Fix For: 2.7
{code:java}
[12:21:22,390][SEVERE][query-#69][GridCacheIoManager] Failed to process message
[senderId=30cab4ec-1da7-4e9f-a262-bdfa4d466865, messageType=class
o.a.i.i.processors.cache.query.GridCacheQueryResponse]
java.lang.OutOfMemoryError: GC overhead limit exceeded
at java.lang.Long.valueOf(Long.java:840)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObject0(OptimizedObjectInputStream.java:250)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:198)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:421)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryResponseEntry.readExternal(GridCacheQueryResponseEntry.java:90)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readExternalizable(OptimizedObjectInputStream.java:555)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.read(OptimizedClassDescriptor.java:917)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObject0(OptimizedObjectInputStream.java:346)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:198)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:421)
at
org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.unmarshal0(OptimizedMarshaller.java:227)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:94)
at
org.apache.ignite.internal.binary.BinaryUtils.doReadOptimized(BinaryUtils.java:1777)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1964)
at
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1716)
at
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:310)
at
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:99)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryResponse.unmarshalCollection0(GridCacheQueryResponse.java:189)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryResponse.finishUnmarshal(GridCacheQueryResponse.java:162)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1530)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:576)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1613)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:125)
at
org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2752)
at
org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1516)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:125)
at
org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1485)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[12:21:28,573][INFO][ignite-update-notifier-timer][GridUpdateNotifier] Update
status is not available.
[12:21:23,759][WARNING][jvm-pause-detector-worker][] Possible too long JVM
pause: 22446 milliseconds.
[12:21:23,758][INFO][grid-timeout-worker-#39][IgniteKernal]
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=c1f087b1, uptime=00:01:25.431]
^-- H/N/C [hosts=2, nodes=3, CPUs=32]
^-- CPU [cur=100%, avg=79.09%, GC=8.93%]
^-- PageMemory [pages=0]
^-- Heap [used=216MB, free=8.57%, comm=236MB]
^--
