You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Lisheng Sun (Jira)" <ji...@apache.org> on 2019/10/30 07:35:00 UTC

[jira] [Updated] (HDFS-14942) Change Log Level to warn in JournalNodeSyncer#syncWithJournalAtIndex

     [ https://issues.apache.org/jira/browse/HDFS-14942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lisheng Sun updated HDFS-14942:
-------------------------------
    Environment: 
when hadoop 2.x upgrades to hadoop 3.x,  InterQJournalProtocol is newly added,so  throw Unknown protocol. 

the newly InterQJournalProtocol is used to sychronize past log segments to JNs that missed them.  And that an error occurs does not affect normal service. I think it should not be a ERROR log,and that log a warn log is more reasonable.
{code:java}
 private void syncWithJournalAtIndex(int index) {
  ...
    GetEditLogManifestResponseProto editLogManifest;
    try {
      editLogManifest = jnProxy.getEditLogManifestFromJournal(jid,
          nameServiceId, 0, false);
    } catch (IOException e) {
      LOG.error("Could not sync with Journal at " +
          otherJNProxies.get(journalNodeIndexForSync), e);
      return;
    }
{code}
{code:java}
2019-10-30,15:11:17,388 ERROR org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not sync with Journal at mos1-hadoop-prc-ct17.ksru/10.85.3.59:111002019-10-30,15:11:17,388 ERROR org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not sync with Journal at mos1-hadoop-prc-ct17.ksru/10.85.3.59:11100org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.authorize.AuthorizationException): Unknown protocol: org.apache.hadoop.hdfs.qjournal.protocol.InterQJournalProtocol at org.apache.hadoop.ipc.Client.getRpcResponse(Client.java:1565) at org.apache.hadoop.ipc.Client.call(Client.java:1511) at org.apache.hadoop.ipc.Client.call(Client.java:1421) at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:228) at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:116) at com.sun.proxy.$Proxy16.getEditLogManifestFromJournal(Unknown Source) at org.apache.hadoop.hdfs.qjournal.protocolPB.InterQJournalProtocolTranslatorPB.getEditLogManifestFromJournal(InterQJournalProtocolTranslatorPB.java:75) at org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer.syncWithJournalAtIndex(JournalNodeSyncer.java:250) at org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer.syncJournals(JournalNodeSyncer.java:226) at org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer.lambda$startSyncJournalsDaemon$0(JournalNodeSyncer.java:186) at java.lang.Thread.run(Thread.java:748)
{code}

  was:
when hadoop 2.x upgrades to hadoop 3.x,  InterQJournalProtocol is newly added,so  throw Unknown protocol. 

the newly InterQJournalProtocol is used to sychronize past log segments to JNs that missed them.  And when an error occurs does not affect normal service. I think it should not be a ERROR log,and that log a warn log is more reasonable.
{code:java}
 private void syncWithJournalAtIndex(int index) {
  ...
    GetEditLogManifestResponseProto editLogManifest;
    try {
      editLogManifest = jnProxy.getEditLogManifestFromJournal(jid,
          nameServiceId, 0, false);
    } catch (IOException e) {
      LOG.error("Could not sync with Journal at " +
          otherJNProxies.get(journalNodeIndexForSync), e);
      return;
    }
{code}
{code:java}
2019-10-30,15:11:17,388 ERROR org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not sync with Journal at mos1-hadoop-prc-ct17.ksru/10.85.3.59:111002019-10-30,15:11:17,388 ERROR org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not sync with Journal at mos1-hadoop-prc-ct17.ksru/10.85.3.59:11100org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.authorize.AuthorizationException): Unknown protocol: org.apache.hadoop.hdfs.qjournal.protocol.InterQJournalProtocol at org.apache.hadoop.ipc.Client.getRpcResponse(Client.java:1565) at org.apache.hadoop.ipc.Client.call(Client.java:1511) at org.apache.hadoop.ipc.Client.call(Client.java:1421) at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:228) at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:116) at com.sun.proxy.$Proxy16.getEditLogManifestFromJournal(Unknown Source) at org.apache.hadoop.hdfs.qjournal.protocolPB.InterQJournalProtocolTranslatorPB.getEditLogManifestFromJournal(InterQJournalProtocolTranslatorPB.java:75) at org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer.syncWithJournalAtIndex(JournalNodeSyncer.java:250) at org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer.syncJournals(JournalNodeSyncer.java:226) at org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer.lambda$startSyncJournalsDaemon$0(JournalNodeSyncer.java:186) at java.lang.Thread.run(Thread.java:748)
{code}


> Change Log Level to warn in JournalNodeSyncer#syncWithJournalAtIndex
> --------------------------------------------------------------------
>
>                 Key: HDFS-14942
>                 URL: https://issues.apache.org/jira/browse/HDFS-14942
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>         Environment: when hadoop 2.x upgrades to hadoop 3.x,  InterQJournalProtocol is newly added,so  throw Unknown protocol. 
> the newly InterQJournalProtocol is used to sychronize past log segments to JNs that missed them.  And that an error occurs does not affect normal service. I think it should not be a ERROR log,and that log a warn log is more reasonable.
> {code:java}
>  private void syncWithJournalAtIndex(int index) {
>   ...
>     GetEditLogManifestResponseProto editLogManifest;
>     try {
>       editLogManifest = jnProxy.getEditLogManifestFromJournal(jid,
>           nameServiceId, 0, false);
>     } catch (IOException e) {
>       LOG.error("Could not sync with Journal at " +
>           otherJNProxies.get(journalNodeIndexForSync), e);
>       return;
>     }
> {code}
> {code:java}
> 2019-10-30,15:11:17,388 ERROR org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not sync with Journal at mos1-hadoop-prc-ct17.ksru/10.85.3.59:111002019-10-30,15:11:17,388 ERROR org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer: Could not sync with Journal at mos1-hadoop-prc-ct17.ksru/10.85.3.59:11100org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.authorize.AuthorizationException): Unknown protocol: org.apache.hadoop.hdfs.qjournal.protocol.InterQJournalProtocol at org.apache.hadoop.ipc.Client.getRpcResponse(Client.java:1565) at org.apache.hadoop.ipc.Client.call(Client.java:1511) at org.apache.hadoop.ipc.Client.call(Client.java:1421) at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:228) at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:116) at com.sun.proxy.$Proxy16.getEditLogManifestFromJournal(Unknown Source) at org.apache.hadoop.hdfs.qjournal.protocolPB.InterQJournalProtocolTranslatorPB.getEditLogManifestFromJournal(InterQJournalProtocolTranslatorPB.java:75) at org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer.syncWithJournalAtIndex(JournalNodeSyncer.java:250) at org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer.syncJournals(JournalNodeSyncer.java:226) at org.apache.hadoop.hdfs.qjournal.server.JournalNodeSyncer.lambda$startSyncJournalsDaemon$0(JournalNodeSyncer.java:186) at java.lang.Thread.run(Thread.java:748)
> {code}
>            Reporter: Lisheng Sun
>            Priority: Minor
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org