[
https://issues.apache.org/jira/browse/IGNITE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16234012#comment-16234012
]
Ivan Fedotov commented on IGNITE-5798:
--------------------------------------
Output example:
IgniteConfiguration [igniteInstanceName=testAckIgniteConfigurationNonQuietMode,
pubPoolSize=8, svcPoolSize=8, callbackPoolSize=8, stripedPoolSize=8,
sysPoolSize=8, mgmtPoolSize=4, igfsPoolSize=8, dataStreamerPoolSize=8,
utilityCachePoolSize=8, utilityCacheKeepAliveTime=60000, p2pPoolSize=2,
qryPoolSize=8, igniteHome=D:\workspace\ignite,
igniteWorkDir=D:\workspace\ignite\work,
mbeanSrv=com.sun.jmx.mbeanserver.JmxMBeanServer@5a42bbf4,
nodeId=6efc8e60-1435-4527-8250-be8ed41aa5f7,
marsh=org.apache.ignite.internal.binary.BinaryMarshaller@46bbde21,
marshLocJobs=false, daemon=false, p2pEnabled=true, netTimeout=10000,
sndRetryDelay=1000, sndRetryCnt=3, metricsHistSize=10000,
metricsUpdateFreq=1000, metricsExpTime=9223372036854775807,
discoSpi=TcpDiscoverySpi [addrRslvr=null, sockTimeout=0, ackTimeout=0,
marsh=JdkMarshaller [], reconCnt=10, maxAckTimeout=600000, forceSrvMode=false,
clientReconnectDisabled=false], segPlc=STOP, segResolveAttempts=2,
waitForSegOnStart=true, allResolversPassReq=true, segChkFreq=10000,
commSpi=TcpCommunicationSpi [connectGate=null, connPlc=null,
enableForcibleNodeKill=false, enableTroubleshootingLog=false,
srvLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$2@7cd0c0ee,
locAddr=null, locHost=null, locPort=45010, locPortRange=100, shmemPort=-1,
directBuf=true, directSndBuf=false, idleConnTimeout=600000, connTimeout=5000,
maxConnTimeout=600000, reconCnt=10, sockSndBuf=32768, sockRcvBuf=32768,
msgQueueLimit=0, slowClientQueueLimit=0, nioSrvr=null, shmemSrv=null,
usePairedConnections=false, connectionsPerNode=1, tcpNoDelay=true,
filterReachableAddresses=false, ackSndThreshold=32, unackedMsgsBufSize=0,
sockWriteTimeout=2000, lsnr=null, boundTcpPort=-1, boundTcpShmemPort=-1,
selectorsCnt=4, selectorSpins=0, addrRslvr=null, rcvdMsgsCnt=0, sentMsgsCnt=0,
rcvdBytesCnt=0, sentBytesCnt=0,
ctxInitLatch=java.util.concurrent.CountDownLatch@75657089[Count = 1],
stopping=false,
metricsLsnr=org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$3@70fbe0fd],
evtSpi=MemoryEventStorageSpi [expireAgeMs=9223372036854775807,
expireCnt=10000, filter=null], colSpi=NoopCollisionSpi [],
deploySpi=LocalDeploymentSpi [lsnr=null],
indexingSpi=org.apache.ignite.spi.indexing.noop.NoopIndexingSpi@8a3f938,
addrRslvr=null, clientMode=false, rebalanceThreadPoolSize=1,
txCfg=org.apache.ignite.configuration.TransactionConfiguration@1e933e45,
cacheSanityCheckEnabled=true, discoStartupDelay=60000, deployMode=SHARED,
p2pMissedCacheSize=100, locHost=127.0.0.1, timeSrvPortBase=31100,
timeSrvPortRange=100, failureDetectionTimeout=10000,
clientFailureDetectionTimeout=10000, metricsLogFreq=0, hadoopCfg=null,
connectorCfg=null, odbcCfg=null, warmupClos=null, atomicCfg=AtomicConfiguration
[seqReserveSize=1000, cacheMode=PARTITIONED, backups=0, aff=null,
grpName=null], classLdr=null, sslCtxFactory=null, platformCfg=null,
binaryCfg=null,
memCfg=org.apache.ignite.configuration.MemoryConfiguration@3e3823ad,
pstCfg=null, activeOnStart=true, longQryWarnTimeout=3000,
sqlConnCfg=SqlConnectorConfiguration [host=null, port=10800, portRange=100,
sockSndBufSize=0, sockRcvBufSize=0, tcpNoDelay=true, maxOpenCursorsPerConn=128,
threadPoolSize=8]]
> Logging Ignite configuration at startup
> ---------------------------------------
>
> Key: IGNITE-5798
> URL: https://issues.apache.org/jira/browse/IGNITE-5798
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexandr Kuramshin
> Assignee: Ivan Fedotov
> Priority: Major
> Labels: easyfix, newbie
>
> I've found that IgniteConfiguration is not logged even when
> -DIGNITE_QUIET=false
> When we starting Ignite with path to the xml, or InputStream, we have to
> ensure, that all configuration options were properly read. And also we would
> like to know actual values of uninitialized configuration properties (default
> values), which will be set only after Ignite get started.
> Monitoring tools, like Visor or WebConsole, do not show all configuration
> options. And even though they will be updated to show all properties, when
> new configuration options appear, then tools update will be needed.
> Logging IgniteConfiguration at startup gives a possibility to ensure that the
> right grid configuration has been applied and leads to better user support
> based on log analyzing.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
